Versions Compared

Old Version 3

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 4

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updating documentation according to DS-1120 fix

...

Metadata Field

Value

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ec3368d9feeabae1-50b1bd18-43c24f25-89959d2f-441f5a4fd7071994cde91c4b"><ac:plain-text-body><![CDATA[

dc.identifier.uri

Handle of Site (format: [handle_prefix]/0)

]]></ac:plain-text-body></ac:structured-macro>

dc.title

Name of Site (from dspace.cfg 'dspace.name' config)

...

Metadata Field

Value

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9b642b6e5dd4f675-7a11f37f-47d843a8-9dad9ba3-26807d0e1b00adbefa80335c"><ac:plain-text-body><![CDATA[

dc.identifier.uri

Site Handle (format: [handle_prefix]/0)

]]></ac:plain-text-body></ac:structured-macro>

...

Info
titleWhy are there Group Names with Handles?

You may have noticed several odd looking group names in the above example, where a Handle is embedded in the name (e.g. "COLLECTION_hdl:123456789/57_SUBMIT"). This is a translation of a Group name which included a Community or Collection Internal ID (e.g. "COLLECTION_45_SUBMIT"). Since you are exporting these Groups outside of DSpace, the Internal ID may no longer be valid or be understandable. Therefore, before export, these Group names are all translated to include an externally understandable identifier, in the form of a Handle. If you use this AIP to restore your groups later, they will be translated back to the normal DSpace format (i.e. the handle will be translated back to the new Internal ID).

If a Group name includes a Community or Collection _Internal ID_ (e.g. "COLLECTION_45_SUBMIT"), and that Community or Collection no longer exists, then the Group will be renamed to a more generic, random name of theGroup is considered "Orphaned".

Warning
titleOther Orphaned Groups May Be Renamed On Export

Wiki Markup
Wiki Markup
In 1.8.2 and above, the Group is renamed using the following format: "
GROUP
  • ORPHANED\_\[object-type\]\_GROUP\_\[obj-id\]\_\[group-type\]" (e.g. "ORPHANED_COLLECTION_GROUP_10_ADMIN").
  • Wiki Markup
    Prior to 1.8.2, the Group was renamed with a random key: "GROUP\_\[random-hex-key\]\_\[object-type\]\_\[group-type\]" (e.g. "GROUP_123eb3a_COLLECTION_ADMIN").  _This old format was discontinued as giving the groups a randomly generated name caused the SITE AIP to have a different checksum every time it was regenerated._

The reasoning is that we were unable to translate an Internal ID into an External ID type\]" (e.g. "GROUP_123eb3a_COLLECTION_ADMIN"). The reasoning is that we were unable to translate an _Internal ID_ into an _External ID_ (i.e. Handle). If we are unable to do that translation, re-importing or restoring a group with an _old_ internal ID could cause conflicts or instability in your DSpace system. In order to avoid such conflicts, these groups are renamed using a random, unique key.

Example of DSPACE-ROLES Schema for a Community or Collection

...