Page History
...
Metadata Field | Value | ||
---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="dc33aaf4e545de0d-f96dd1bd-46a64813-8ee5a44e-795bbe3c113f1b78060bfb4c"><ac:plain-text-body><![CDATA[ | dc.identifier.uri | Handle of Site (format: | ]]></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="f95e89e4ae980b29-cca52cc3-46a146e0-bdc0a5a8-c10e5c0d8d2b83412515373a"><ac:plain-text-body><![CDATA[ | dc.identifier.uri | Site Handle (format: | ]]></ac:plain-text-body></ac:structured-macro> |
...
Code Block |
---|
aip.disseminate.techMD = PREMIS, DSPACE-ROLES |
Example of DSPACE-ROLES Schema for a SITE AIP
Below is a general example of the structure of a DSPACE-ROLES XML file, as it would appear in a SITE AIP.
Code Block |
---|
<DSpaceRoles> <Groups> <Group ID="1" Name="Administrator"> <Members> <Member ID="1" Name="bsmith@myu.edu" /> </Members> </Group> <Group ID="0" Name="Anonymous" /> <Group ID="70" Name="COLLECTION_hdl:123456789/57_ADMIN"> <Members> <Member ID="1" Name="bsmith@myu.edu" /> </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="bsmith@myu.edu" /> </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="8" Name="COLLECTION_hdl:123456789/6703_DEFAULT_READ" /> <Group ID="9" Name="COLLECTION_hdl:123456789/2_ADMIN"> <Members> <Member ID="1" Name="bsmith@myu.edu" /> </Members> </Group> </Groups> <People> <Person ID="1"> <Email>bsmith@myu.edu</Email> <Netid /> <FirstName>Bob</FirstName> <LastName>Smith</LastName> <Language>en</Language> <CanLogin /> </Person> <Person ID="2"> <Email>jjones@myu.edu</Email> </People> </DSpaceRoles> <Netid /> <FirstName>Jane</FirstName> <LastName>Jones</LastName> <Language>en</Language> <CanLogin /> </Person> </People> </DSpaceRoles> |
Info | ||
---|---|---|
| ||
Info | ||
| ||
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) |
Example of DSPACE-ROLES Schema for a Community or Collection
Below is a general example of the structure of a DSPACE-ROLES XML file, as it would appear in a Community or Collection AIP.
This specific example is for a Collection, which has associated Administrator, Submitter, and Workflow approver groups. In this very simple example, each group only has one Person as a member of it. Please notice that the Person's information (Name, NetID, etc) is NOT contained in this content (however they are available in the DSPACE-ROLES example for a SITE, as shown above)
Code Block |
---|
<DSpaceRoles>
<Groups>
<Group ID="9" Name="COLLECTION_hdl:123456789/2_ADMIN" Type="ADMIN">
<Members>
<Member ID="1" Name="bsmith@myu.edu" />
</Members>
</Group>
<Group ID="13" Name="COLLECTION_hdl:123456789/2_SUBMIT" Type="SUBMIT">
<Members>
<Member ID="2" Name="jjones@myu.edu" />
</Members>
</Group>
<Group ID="10" Name="COLLECTION_hdl:123456789/2_WORKFLOW_STEP_1" Type="WORKFLOW_STEP_1">
<Members>
<Member ID="1" Name="bsmith@myu.edu" />
</Members>
</Group>
<Group ID="11" Name="COLLECTION_hdl:123456789/2_WORKFLOW_STEP_2" Type="WORKFLOW_STEP_2">
<Members>
<Member ID="2" Name="jjones@myu.edu" />
</Members>
</Group>
<Group ID="12" Name="COLLECTION_hdl:123456789/2_WORKFLOW_STEP_3" Type="WORKFLOW_STEP_3">
<Members>
<Member ID="1" Name="bsmith@myu.edu" />
</Members>
</Group>
</Groups>
</DSpaceRoles>
|
METSRights Schema
All DSpace Policies (permissions on objects) are translated into the METSRights schema. This is different than the above DSPACE-ROLES schema, which only represents Groups and People objects. Instead, the METSRights schema is used to translate the permission statements (e.g. a group named "Library Admins" has Administrative permissions on a Community named "University Library"). But the METSRights schema doesn't represent who is a member of a particular group (that is defined in the DSPACE-ROLES schema, as described above).
...