§ 2.5 Authority Document Schema

When we say that we are “complying”, we are saying that we are complying with authoritative rules that are not of our own creation. These authoritative rules can come in the form of regulations, principles, standards, guidelines, best practices, policies, and procedures. Collectively, these are called Authority Documents within this schema. For the purposes of this standard, we will refrain from a full discussion, especially since there is a wealth of information about what Authority Documents are that can be found online HERE.

To "catalog" a book or other form of library material involves several interrelated processes which all contribute to the achievement of Charles Ammi Cutter’s “objects” for a catalog[1]:

  • To enable a person to find a book of which the author, title, or subject is known;

  • To show what the library has by a given author, on a given subject, or in a given kind of literature; and

  • To assist in the choice of a book.

Thus, catalogers prepare a description of the Authority Document, assign subject headings, determine a classification system, provide a link to the electronic item, and code that information with both metadata so that it may be displayed in online catalogs.

When analyzing current schemas, the only catalog, per se, is that provided by the UCF’s Common Controls Hub, and STIGViewer.com. However, the UCF’s current catalog structure doesn’t account for all the various Authority Document types and reference structures necessary. Therefore, the catalog structure has been expanded with the help from the folks at Zotero to include various forms of documents:

  • Authority Documents

  • eBook from a Bookseller (Kindle, iBooks)

  • eBook from a database

  • eBook from a Website

  • Journal Article from a database

  • Journal Article from Website

  • Secure Technical Implementation Guides

  • OSCAL

§ 2.5 AuthorityDocument

A document duly adopted implementing the powers, functions, and activities of an Authority.

§ 2.5.1 ADMapping

Information related to which team mapped the Authority Document, when it became available, and how to find it in that system.

§ 2.5.1.1 Team

Information specifically about the team involved in the AD Mapping.

§ 2.5.1.1.1 Member

Information about each team member that participated in the mapping project.

§ 2.5.2 ADStructure

This defines Authority Document specific structures.

§ 2.5.2 Authors

A collection of Authors.

§ 2.5.3 CommonNames

A collection of common names, or simplified names that an Authority Document might be searched by.

§ 2.5.4 Editors

A collection of Editors.

§ 2.5.5 Identifiers

These are unique points of reference for finding the original document.

§ 2.5.6 SubjetMatterStub

Stub response for Subject Matters.

  1. (Cutter 1876)

Last updated