Versions Compared

Old Version 30

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 31

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Metadata Field

Value

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e076faa427cf046b-fdd5723b-45f04e57-a179ada9-58c93e4baeae2dbc60553a55"><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="3dffe117a5a7f657-239aa356-49ec429a-8ad8b537-ba8e7b0160bd4d4e5af3ab82"><ac:plain-text-body><![CDATA[

dc.identifier.uri

Site Handle (format: [handle_prefix]/0)

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

...

Metadata Field

Value

<premis:objectIdentifier>

Contains Bitstream direct URL

<premis:objectCategory>

Always set to "File"

<premis:fixity>

Contains MD5 Checksum of Bitstream

<premis:format>

Contains File Format information of Bistream

<premis:originalName>

Contains original name of file

DSPACE-ROLES Schema

All DSpace Groups and EPeople objects are translated into a custom DSPACE-ROLES XML Schema. This XML Schema is a very simple representation of the underlying DSpace database model for Groups and EPeople. The DSPACE-ROLES Schemas is generated by DSpace's RoleCrosswalk.

Only the following DSpace Objects utilize the DSPACE-ROLES Schema in their AIPs:

  • Site AIP – all Groups and EPeople are represented in DSPACE-ROLES Schema
  • Community AIP – only Community-based groups (e.g. COMMUNITY_1_ADMIN) are represented in DSPACE-ROLES Schema
  • Collection AIP – only Collection-based groups (e.g. COLLECTION_2_ADMIN, COLLECTION_2_SUBMIT, etc.) are represented in DSPACE-ROLES Schema

In the METS structure, DSPACE-ROLES metadata always appears within a techMD inside an <mdWrap MDTYPE="OTHER" OTHERMDTYPE="DSPACE-ROLES"> element. For example:

Code Block

  <amdSec ID="amd_2068"> 
      ...
      <techMD ID="techMD_2070">
         <mdWrap MDTYPE="OTHER" OTHERMDTYPE="DSPACE-ROLES">
              ...
         </mdWrap>
      </techMD>
      ...
  </amdSec>

By default, DSPACE-ROLES metadata is always included in AIPs. It is controlled by the following configuration in your dspace.cfg:

Code Block

aip.disseminate.techMD = PREMIS, DSPACE-ROLES

Example of DSPACE-ROLES Schema

Below is a general example of the structure of a DSPACE-ROLES XML file.

Code Block

<DSpaceRoles>
  <Groups>
    <Group ID="1" Name="Administrator">
      <Members>
        <Member ID="1" Name="tdonohue@duraspace.org" />
      </Members>
    </Group>
    <Group ID="0" Name="Anonymous" />
    <Group ID="70" Name="COLLECTION_hdl:123456789/57_ADMIN">
      <Members>
        <Member ID="1" Name="tdonohue@duraspace.org" />
      </Members>
    </Group>
    <Group ID="75" Name="COLLECTION_hdl:123456789/57_DEFAULT_READ">
      <MemberGroups>
        <MemberGroup ID="0" Name="Anonymous" />
      </MemberGroups>
    </Group>
    <Group ID="71" Name="COLLECTION_hdl:123456789/57_SUBMIT">
      <Members>
        <Member ID="1" Name="tdonohue@duraspace.org" />
      </Members>
    </Group>
    <Group ID="72" Name="COLLECTION_hdl:123456789/57_WORKFLOW_STEP_1">
      <MemberGroups>
        <MemberGroup ID="1" Name="Administrator" />
      </MemberGroups>
    </Group>
    <Group ID="73" Name="COLLECTION_hdl:123456789/57_WORKFLOW_STEP_2">
      <MemberGroups>
        <MemberGroup ID="1" Name="Administrator" />
      </MemberGroups>
    </Group>
    <Group ID="74" Name="COLLECTION_hdl:123456789/57_WORKFLOW_STEP_3">
      <MemberGroups>
        <MemberGroup ID="0" Name="Anonymous" />
      </MemberGroups>
    </Group>
    <Group ID="8" Name="COLLECTION_hdl:123456789/6703_DEFAULT_READ" />
    <Group ID="9" Name="COLLECTION_hdl:123456789/2_ADMIN">
      <Members>
        <Member ID="1" Name="tdonohue@duraspace.org" />
      </Members>
    </Group>
    <Group ID="14" Name="COLLECTION_hdl:123456789/2_DEFAULT_READ" />
    <Group ID="13" Name="COLLECTION_hdl:123456789/2_SUBMIT" />
    <Group ID="10" Name="COLLECTION_hdl:123456789/2_WORKFLOW_STEP_1" />
    <Group ID="11" Name="COLLECTION_hdl:123456789/2_WORKFLOW_STEP_2" />
    <Group ID="12" Name="COLLECTION_hdl:123456789/2_WORKFLOW_STEP_3" />
  </Groups>
  <People>
    <Person ID="1">
      <Email>tdonohue@duraspace.org</Email>
      <Netid />
      <FirstName>Tim</FirstName>
      <LastName>Donohue</LastName>
      <Language>en</Language>
      <CanLogin />
    </Person>
  </People>
</DSpaceRoles>
Info
titleGroup 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/2_SUBMIT"). This is a translation of a Group name which included a Community or Collection Internal ID (e.g. "COLLECTION_5_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.

METSRights Schema