Page History

...

Initial Requirements

The Item Level Versioning implementation in DSpace 3.0 builds on following requirements identified by the stakeholders who supported this contribution. Initial Requirements Analysis

Initial Requirements

The Item Level Versioning implementation in DSpace 3.0 builds on following requirements identified by the stakeholders who supported this contribution. Initial Requirements Analysis

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

User Interface

Create a new version of an item

To create a new version of an existing item the following steps have to be performed:

1. Search for an Item
2. Go to Item view page
3. click on "create a new version"
4. fill out the form and confirm the operation 

. Image Removed

After the operation is confirmed a new submission process will be generated and the user could modify the metadata and the bitstream(s).
The new version of the item won't be visible until the workflow will be completed.

Access history of an item

To access the history of an item the following steps have to be performed:

...

1. 1. be maintained in SWORD, LNI and AIP packaging and be maintained in updates and restorations.

User Interface

Creating a new version of an item

Administrators en collection/community administrators can create new versions of an item from the Item View page.

1. Click "Create a new version" from the Context Menu in the navigation bar.
2. Provide the reason for creating a new version that will lateron be stored and displayed in the version summary.
   
   Image Added
   
   
3. Your new version is now creates as a new Item in your Workspace. It requires you to go through the submission and workflow steps like you would do for a normal, new submission to the collection. The rationale behind this is that if you are adding new files or metadata, you will also need to accept the license for them. In addition to this, the versioning functionality does not bypass any quality control embedded in the workflow steps.
   
   Image Added 

After the submission steps and the execution of subsequent workflow steps, the new version becomes available in the repository.

View the history and older versions of an item

An overview of the version history, including links to older versions of an item, is available at the bottom of an Item View page. The repository administrator can decide whether the version history should be available to all users or restricted to administrators.

Image Added

Versioning model

For every new Version a separate DSpace Item will be created that replicates the metadata, bundle and bitstream records. The bitstream records will point to the same file on the disk.

...