[MAGNOLIA-3313] Add multivalue property support to metadata Created: 06/Oct/10 Updated: 20/Feb/15 Resolved: 19/Oct/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 4.4 |
| Type: | Task | Priority: | Major |
| Reporter: | Federico Grilli | Assignee: | Federico Grilli |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Description |
|
The need for adding multivalue properties to metadata arose as we want to store a list of users concurrently editing a certain content. This involves changing the node type defintion for MetaData and allow for multiple properties. |
| Comments |
| Comment by Federico Grilli [ 19/Oct/10 ] |
|
no longer needed as soft locking status is stored in a servlet context hashmap |