Page tree
Skip to end of metadata
Go to start of metadata
Title (Goal)Structure - Automated Retention of All changes to Items
Primary ActorSystem
Scope 
Level 
Story (A paragraph or two describing what happens)

A record of all changes to item should be retained in DSpace. Any time an update/commit happens to an ITem, a clear record of all the changes and a previous state of the item should be retained for repository managers to review. Repository Managers should be able to restore from any previous version replacing the contents of the current version with the previous state.

Persistence of all changes to DSpace Items in a manner that past versions may be viewed and existing Item may be restored if necessary. Records changes to Bitstreams, Resource Polices, Formats, Metadata Fields. Changes to the Item and Bitstreams to are recorded when any change to an “Archived” Item happens. new revision is persisted when new changes are committed on item.

Identifiers should stay consistent for the resource, for example, handles and/or DOI may contain version history information, but a canonical handle or DOI should persist that represents all versions of the Item.

 

 

 

3 Comments

  1. This one is very important in the environment where repository manager wants to delegate refinement of the items to the users, but stay in control.

  2. Couldn't we also make the changes visible to all users, for transparency? So, for example, if the item contains files which are the supplementary data for a paper, and if a change has been made to them since the paper was first published, users will be able to see this clearly (or more importantly they'll be able to reassure themselves that no changes have been made since they last downloaded the files).

  3. Just commenting to reiterate how important this is.