Versions Compared

Old Version 2

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 3

changes.mady.by.user Pascal-Nicolas Becker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: DS-1349 (hide submitter in version table) is solved for JSPUI (but not for XMLUI)

...

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 For JSPUI you can also configure if the submitter's name and email address of the editor are exposed as well. This might actually be useful if the editor account should be part of the version history or if they should be hidden (see below). For XMLUI you currently do not have this choice and the submitter's name and email address will be publicly exposed to everyone able to see the version history. 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.

Therefore, discussion has illustrated that there is a usecase for an intermediate exposure of version history that hides the Editor column.

You can join the discussion or contribute a new code here:
If you want to step in and enhance the XMLUI to respect the configuration option, please join the discussion here: JIRA DS-1349 - Item Level Versioning exposes personal data Image Removed.

Image Added

Hide Submitter details in JSPUI's version table

 In the file [dspace]/config/modules/versioning.cfg you can edit the configuration option versioning.item.history.include.submitter. By default this is set to false, which means that information about the submitter is only viewable by administrators. If you want to expose the submitters information to everyone (which be useful if all submitters uses generic institutional email addresses, but may conflict with local privacy laws if personla details are included) you can set this configuration property to true.

Code Block
# The property item.history.include.submitter controls whether the name of
# the submitter of a version should be included in the version history of
# an item. This property is currently used in JSPUI only.
versioning.item.history.include.submitter=false

Credits

The initial contribution of Item Level Versioning to DSpace 3.0 was implemented by @mire with kind support from:

...