Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: change to group rename warning message to better describe recent code fixes on trunk

...

Metadata Field

Value

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="2898554da8752421-7eb1978a-46be46c6-bad3bb0b-47559723d0ee2099993381b3"><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="ffc35c868fee1282-0b880e59-4f874048-af9b94c5-56ec7838635d743eec920fda"><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).

Warning
titleUnused Groups may not be exportedOther Groups May Be Renamed On Export

Wiki Markup
If a Group name includes a Community or Collection _Internal ID_ 
Groups which are no longer utilized by the system may not be exported in the AIP. 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
not be exported in any AIP. The reasoning is that we were unable to translate an Internal ID into an External ID
 be renamed to a more generic, random name of the format: "GROUP_\[random-hex-key\]_\[object-type\]_\[group-type\] (e.g. "GROUP_123ef3_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 will never be included within AIPs
 groups are renamed using a random, unique key.

Example of DSPACE-ROLES Schema for a Community or Collection

...