Page History
...
Higher Priority Requirements
- What is Versionable
- Versioning is at the level of
- Previous Versions of Items should continue to be visible, citable and accessible
- an Individual Item
- 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 (possibly configurable)
- Previous Versions of Items should continue to be visible, citable and accessible
- The Previous Versions Bitstreams
- are retained. If something was once retrievable, it is always retrievable.
- Identifiers A base "versionhistory" Identifier points to the most recent version
- Each version of an Item is represented by a separate "versioned" identifier (Handle or DOI)
- The relationships between versions should be visible in various Metadata Exports (OAI, Packagers, ItemExport)
- Expose Versioning detail in DSpace API and Services (I.E. OAI, Bagit, Etc.)
- The relationships between versions should not be brittle and breakable by manipulating Item metadata records.
- 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.
- When a new version of an Item is deposited the "versionhistory" identifier will resolve to the new version.
- Each version of the item includes metadata about who created the version and the date/time. (it is essentially a full copy of the item, with modifications)
- Presentation
- On the item page, there is a link to view previous/subsequent versions.
- Each version of the item should include additional provenance details about who created the version, when and why.
- 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, sword or LNI deposit.
- Submitters: Creation of a new version is initiated by the
- original submitter. On the "submissions" page,
- submitter should see all of their archived submissions.
- Collection Manager, Administrators: should have a button to submit a new version of a
- Item accessible in the Edit Item administrative interface.
- 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.
Lower Priority Requirements
...
Overview
Content Tools