Page History

...

• Mark Diggory - @mire
• Holly Miller - MBL
• Diane Rielinger - MBL
• Lisa Raymond - WHOI 
• Ryan Scherle - NESCent / Dryad

Administration

1. Current Code Locations
   1. https://dryad.googlecode.com/svn/trunk/dryad/dspace/modules/

Business Requirements / Goals

The history of an item should be available, and it should be possible to cite a particular version of the item.

Higher Priority Requirements

1. Versioning is at the level of individual Items, User should be able to generate a new version of the item via submission, sword or LNI deposit.
2. Previous Versions of Items should continue to be visible, citable and accessible 
3. Previous versions of bitstreams are retained. If something was once retrievable, it is always retrievable.
4. Each version of an Item is represented by a separate "versioned" identifier (Handle or DOI)
5. The relationships between versions should be visible in various Metadata Exports (OAI, Packagers, ItemExport)
6. Expose Versioning detail in DSpace API and Services (I.E. OAI, Bagit, Etc.)
7. The relationships between versions should not be brittle and breakable by manipulating Item metadata records.
8. A base "versionhistory" Identifier points to the most recent version of the Item. 
9. A revision identifier also exists that is unique to the specific version.
10. When a new version of an Item is deposited, a new revision identifier will be created.
11. When a new version of an Item is deposited the "versionhistory" identifier will resolve to the new version.
12. 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)
13. On the item page, there is a link to view previous/subsequent versions.
14. By examining the metadata, it is possible to determine whether an item is the most recent version, the original version, or an intermediate version.
15. Creation of a new version is initiated by the author. On the "submissions" page, users should see all of their archived submissions. 
16. Each archived submission should have a button to submit a new version of a Item accessible by the Submitter or the Collection Manager, Administrators
17. Only the most recent version of an item is available via the search interface (possibly configurable)

 Lower Priority Requirements

1. All metadata and content changes within a "Version" should be logged in an audit trail

Administration

1. Current Code Locations
   1. https://dryad.googlecode.com/svn/trunk/dryad/dspace/modules/

...

Technical Requirements and Existing Implementation

Work Areas for Implementation of Version History

...