Page History
...
General user actions that would generate a new Version of a new Dryad Item and their overal impact on creation of a new DSpace item.
...
Scenarios
...
Description
...
New Item Version
...
Add Data File to Existing Data Package
...
Add a Data File Item to Dryad and add to existing Data Package
...
yes
...
Delete Data File from Package
...
Remove a Data File from an existing Data Package
...
yes
...
Replace Bitstream in Item
...
Remove an existing Data File (2) and add a new one (1)
...
yes
- Release of a new scientific dataset with additional data
- Release of a corrected scientific dataset with altered data
- Release of a revised or corrected journal article, technical report, ...
Services that are effected by user scenarios
- Local User Submissions and Curator Reviews.
- SWORD and LNI Deposit interfaces
- Local ItemImport and Export Command-line services.
- External Harvesters (OAI and DSpace)
- Academic Search Engines and Catalogs.
...
Edit Metadata in Item
...
Metadata edits do not produce new Items
...
Metadata Mapping
Initial Requirements for Dryad anticipated exposure of versioning information as metadata fields, shortly after the initial draft of an implementation proposal. It was determined that it was critial that Referential Integrity be maintained when versioning DSpace Items. Utilizing metadata fields was abandoned as an approach and a version history database table and Domain Model was introduced to support version histories.
...
Overview
Content Tools