Versioning in DSpace:
"DSpace provides a way to manage your research materials and publications in a professionally maintained repository to give them greater visibility and accessibility over time." (http://www.dspace.org/index.php?option=com_content&task=blogcategory&id=44&Itemid=156) (accessed 3/3/08)
Follow this link to see a PDF of how DSpace currently organises material within its system. DSpace is slated to support versioning from release 1.6 (source - external link) This is the proposed system:
"Versions can be used to support not only migrations, but also corrections and technical modifications of essentially equivalent semantic content. In some systems, versions are also used for semantically different content, such as pre-refereed and published versions of a paper. While the system we recommend would not technically prevent such versions from being created, we recommend against using versions for this type of content management, but instead to create a new item for this type of version and provide relationship links between the items." (see http://wiki.dspace.org/static_files/0/0e/DSpace-recs.pdf , page 9)(accessed 3/3/08)
This versioning solution will be using a FRBR-like structure, tying metadata to individual items and manifestations (see http://wiki.dspace.org/static_files/0/0e/DSpace-recs.pdf , page 7).
Of particular interest are the specifications listed in the DSpace wiki page for versioning in this new version: http://wiki.dspace.org/index.php/Google_Summer_of_Code_Versioning.
Features expected include:
- Revision's metadata: Every revision must have its own metadata. Changes to metadata may or may not result in the creation of a new version of an Item. It is left to the user's discretion.
- Point to Latest: The default behaviour of the system in looking for a versioned object (Item, bitstream, etc.) without a specified revision number is to supply the latest such revision.
Next Section:
Please go to the page about EPrints.