Versions Compared

Old Version 1

changes.mady.by.user Melissa Anez

Saved on

compared with

New Version 2

changes.mady.by.user Melissa Anez

Saved on

Key

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

...

  1. Collection Name - This is the name that will show up at the top of the collection's page (see 'Top-level Collection' in the first image above for an example).
  2. Collection PID - This is the Persistent Identifier for this new collection; check APPENDIX E - Glossary (Copy) for more information on Persistent Identifiers

  3. Inherit collection policy?- Check this box to copy the parent collection's collection policy into the new collection. This will include any content models the parent collection was using. In this example, the only content model in the top-level collection's collection policy was the 'Collection' content model. so no other unique content models will be pulled.

    If the inherit collection policy box is not selected you will need to enter a Children Namespace - This is the namespace objects in the new collection will use (again, check the Glossary for more information). You may select any content models which will apply to this new collection (this will display all content models that are available in your repository).

  4. Inherit XACML policy from: Select from the dropdown menu if you would like to copy the XACML policy.
  5. Create collection - Once the form is filled out, click this button to create the collection.

...

Note

In this example, the new child collection contains no content models that would allow for ingesting objects. A new content model would need to be assigned to the collection before the user can begin ingesting new objects. Check the tutorial on How to Manage Collection Policies (Copy) to see how to turn this blank collection into a usable one.