Page History
...
By default, Item Level Versioning is disabled in DSpace 34.0. This feature is currently only supported in the XMLUI.
Steps for XML UI
If you wish to enable this feature, you just have to uncomment the "Versioning" aspect in your [dspace]/config/xmlui.xconf file (and restart your servlet container):
| Code Block |
|---|
<!-- =====================
Item Level Versioning
===================== -->
<!-- To enable Item Level Versioning features, uncomment this aspect. -->
<aspect name="Versioning Aspect" path="resource://aspects/Versioning/" />/" /> |
Steps for JSP UI
If you wish to enable this feature, you just have to edit the enabled settings in your [dspace]/config/modules/versioning.cfg file (and restart your servlet container):
| Code Block |
|---|
#---------------------------------------------------#
#------------ VERSIONING CONFIGURATIONS ------------#
#---------------------------------------------------#
# These configs are used by the versioning system #
#---------------------------------------------------#
#Parameter 'enabled' is used only by JSPUI
enabled=false |
| Warning | ||
|---|---|---|
| ||
If you are using the AIP Backup and Restore functionality to backup / restore / migrate DSpace Content, you must be aware that the "Item Level Versioning" feature is not yet compatible with AIP Backup & Restore. Using them together may result in accidental data loss. Currently the AIPs that DSpace generates only store the latest version of an Item. Therefore, past versions of Items will always be lost when you perform a restore / replace using AIP tools. See DS-1382. |
...
| Code Block |
|---|
item.history.view.admin=false |
Identified Challenges & Known Issues in DSpace
...
4.0
Item Level Versioning has a substantial conceptual impact on many DSpace features. Therefore it has been accepted into DSpace 3.0 as an optional feature and it is still an option feature in DSpace 4.0. Following challenges have been identified in the current implementation. As an early adopter of the Item Level Versioning feature, your input is greatly appreciated on any of these.
...
One possible solution would be to present an end user with aggregated statistics across all viewers, and give administrators the possibility to view statistics per version.
No support for JSP User Interface
Item Versioning in DSpace 3.0 was contributed without specific user interface support for JSP User Interface.
Exposing version history
The version history is added on the bottom of a versioned item page. A repository administrator can either decide to show this to all users, or restrict it to admins only. If it is shown to admins only, an end user will have no way to find the way to an older version. On the other hand, if a repository administrator does decide to expose version history to all users, the name and email address of the editor are exposed as well. This might actually be useful if the editor account is a generic institutional email address, but may conflict with local privacy laws if any personal details are included in this account.
...
- MBLWHOI Library
- Woods Hole Oceanographic Institution
- Marine Biology Laboratory, Center for Library and Informatics, History and Philosophy of Science program
- Arizona State University, Center for Biology and Society
- Dryad
The JSP UI compatibility has been added in DSpace 4.0 by CINECA
Overview
Content Tools