Page History
...
- What should be Versionable
- Versioning happens at the level of an Individual Item
- Versioning should preserve the current state of metadata, bitstreams and resource policies attached to the item.
- Access, Search and Discovery
- Only the most recent version of an item is available via the search interface
- Previous versions of Items should continue to be visible, citable and accessible
- The Bitstreams for previous versions are retained. If something was once retrievable, it should always be retrievable.
- Identifiers
- Each version of an Item is represented by a separate "versioned" identifier
- A base "versionhistory" Identifier points to the most recent version of the Item.
- A revision identifier also exists that is unique to the specific version.
- When a new version of an Item is deposited, a new revision identifier will be created.
- Presentation
- On the item page, there is a link to view previous/subsequent versions.
- By examining the metadata or identifiers, it is possible to determine whether an item is the most recent version, the original version, or an intermediate version.
- Access Control and Rights
- Certain roles should be able to generate a new version of the item via submission.
- To submitters, collection manager, administrators will be given to option to create new version of an item.
- Rights to access a specific Item should transmute as well to previous versions
- Rights to access a specific Bitstream should also transmute to previous versions.
- Data Integrity
- The relationships between versions should not be brittle and breakable by manipulating Item metadata records.
- The relationships between versions should be preserved and predictable in various Metadata Exports (OAI, Packagers, ItemExport)
- The relationships between versions should be maintained in SWORD , LNI and AIP packaging and be maintained in updates and restorations.
...
Overview
Content Tools