Task #3703
Story #3698: support for mutable content
determine mutability use cases
Start date:
2013-04-01
Due date:
% Done:
100%
Milestone:
None
Product Version:
*
Story Points:
Sprint:
Description
decide and agree on the use cases in scope and out of scope for implementation (and deferred scope)
History
#1 Updated by Rob Nahf about 11 years ago
- Subject changed from determine use cases to determine mutability use cases
#2 Updated by Rob Nahf about 11 years ago
- % Done changed from 0 to 70
#3 Updated by Rob Nahf about 11 years ago
- Category set to Documentation
- Status changed from In Progress to Closed
- % Done changed from 70 to 100
- translation missing: en.field_remaining_hours set to 0.0
listed in Content Mutability document, to be reviewed:
http://mule1.dataone.org/ArchitectureDocs-current/design/ContentMutability.html
#4 Updated by Rob Nahf almost 11 years ago
- Target version changed from 2013.12-Block.2.2 to 2013.20-Block.3.2
#5 Updated by Rob Nahf almost 11 years ago
- Target version changed from 2013.20-Block.3.2 to 2013.22-Block.3.3
#6 Updated by Dave Vieglais over 10 years ago
- Target version changed from 2013.22-Block.3.3 to 2013.35-Block.5.1
#7 Updated by Dave Vieglais over 10 years ago
- Target version changed from 2013.35-Block.5.1 to 2014.6-Block.1.3
#8 Updated by Chris Jones about 10 years ago
- Target version changed from 2014.6-Block.1.3 to 2014.18-Block.3.1
#9 Updated by Robert Waltz over 9 years ago
- Target version changed from 2014.18-Block.3.1 to CCI-2.0.0
