Use Restriction Note
|Mandatory||Repeatable||Data Type||Authority||Level Available||A/V Only||Public Element|
|No||No||Variable Character Length (2000)||None||Series
|Definition:||Significant information pertaining to the use or reproduction of the archival materials.|
|Purpose:||Clarifies use restrictions and provides any significant information pertaining to the use restrictions of archival materials.|
|Relationship:||This element is dependent on Use Restriction Status. To have Use Restriction Note, Use Restriction Status must be created. In addition, the selection of some terms from the Use Restriction Status Authority List and the Specific Use Restriction Authority List require the use of Use Restriction Note as described in the Guidance for those elements.|
|Guidance:||Enter any significant information pertaining to the use restrictions for the archival materials.
Although the name of the person or organization holding a copyright may be indicated in this note, do not include contact information (names and phone numbers) as that information frequently changes.
Do not use this element to describe access restrictions to the archival materials, instead use the Access Restriction elements.
Do not use this element to describe physical reasons for access restrictions, instead use Physical Restriction Note. Physical reasons are often preservation requirements, such as the need to acclimate materials stored in a cold vault.
Do not use this element to describe the hardware or equipment needed to access the archival materials, instead use Technical Access Requirements Note.
Write in complete sentences. Be precise and brief. Do not use acronyms or organizational designations that are not defined in either Title or Scope and Content Note. If Use Restriction Note uses an acronym that is not defined in either Title or Scope and Content Note, define the acronym the first time that it is used in Use Restriction Note. Consult the Abbreviations section for further guidance on other abbreviation topics.
Table of Contents
Lifecycle Data Requirements Guide