...
LTS recommends that NRS users avoid defining multi-level Naming Authorities loaded with organizational meaning. In practice, this means defining a Naming Authority only at the tub level ("FHCL" rather than "FHCL.Widener"). Collections do move and organization-specific Naming Authorities become confusing if the collections they refer to are moved from one library to another. LTS also recommends that Naming Authorities have no more than three levels: top-level, child, grandchild.
Connect to NRS Admin
Click on "Naming Authority" from top menu
Click on 'Create' from Naming Authority search page
Select the Parent Authority from the drop down list
You should only see the Naming Authorities for which you have permissions
This is the procedure for creating an authority path under the top-level. The operator performing this procedure must have the "authority" role relative to the authority path under which the child authority will be defined.
...
Production: http://nrs.harvard.edu/urn-3:HUL:nrs-admin
QA/test: http://nrs.harvard.edu/urn-3:HUL:nrs-admin-qa
- From the main menu, select Naming Authorities and then Delegate.
- Select the urn-3 namespace.
- From the drop-down list, select the authority path under which you will define a child- or sub-authority and click the Select button.
- Enter information for the child authority path and click the Delegate button.
...