LTS has pre-created top-level authority pathsNaming Authorities, corresponding to main administrative units of the Harvard University. Using NRS Web Admin, it is possible to define child- or sub-authorities under these top-level authority paths. The responsibility for defining sub-authorities is vested in the local NRS administrator for each authority path.
Using NRS Web Admin, the local administrator can perform these actions on authority paths for which they are authorized:
- Delegate (create) child- or sub-authorities under a top-level authority path.
- Update an existing authority path (change its status or maximum depth/breadth settings).
- Purge (delete) an authority path (only possible for paths that have no names or sub-authorities defined).
Best practice for defining sub-authorities. OIS recommends that tubs avoid defining multi-level authority paths Naming Authorities. NRS users who have the 'Lead' role for a Naming Authority are able to create child authorities for that Naming Authority. For instance, if a staff member has the Lead role for HUL.ARCH, the staff member would be authorized to create HUL.ARCH.2020 or HUL.ARCH.ANNUAL.1900
LTS recommends that NRS users avoid defining multi-level Naming Authorities loaded with organizational meaning. In practice, this means defining an authority path a Naming Authority only at the tub level ("FHCL" rather than "FHCL.Widener"). Collections do move and organization-specific authority paths Naming Authorities become confusing if the collections they refer to are moved from one library to another.
...
If a tub must define a multi-level authority path, OIS LTS recommends that the no more than three levels of naming authority delegation be performed: top-level, child, grandchild. NRS will only permit a maximum of five levels of delegation. Also, individual components of the authority path should be no longer than seven characters.
...
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
- Administrator: the 8 digit HUID of the operator given the authority role for this new sub-authority. This operator would be identified as the local NRS administrator for this authority path on the NRS Status Page. Leave this field blank and administrative responsibility is implicitly passed to the administrator of the parent authority.