Difference between revisions of "Content template and instructions"

(Type of Relationship)
(EAD ID Number)
Line 127: Line 127:
 
Enter the title of the archival resource associated with the organization, as it appears in the top-level of the library catalog record or finding aid.
 
Enter the title of the archival resource associated with the organization, as it appears in the top-level of the library catalog record or finding aid.
  
====EAD ID Number====
+
====Materials Call Number====
Enter the identifier of the EAD record for the resource associated with the organization, as it appears in the <eadid> element of the EAD record.
+
Enter the call number for the resource associated with the organization, as it appears in the catalog record or finding aid.
  
 
====Type of Relationship====
 
====Type of Relationship====

Revision as of 13:46, 17 September 2009

Insert administrative history here.

Variant names

Insert variant names here.

Description

Established: ?
The date "?" was not understood.
Abolished: ?
The date "?" was not understood.
Location: Provo, Utah (?
The date "?" was not understood.
-?
The date "?" was not understood.
)

Functions

Insert description of functions here.

Assets and Administrative Structure

Insert description of administrative structure here.

Associated Units

Superior unit: Brigham Young University (?
The date "?" was not understood.
-?
The date "?" was not understood.
) Subordinate unit: ? (?
The date "?" was not understood.
-?
The date "?" was not understood.
)

Associated Archival Materials

Insert references to all associated materials here.

Sources

Insert sources for all information given in the record here.

Maintenance Information

Record ID:

Creator: UPB


Content guidelines

Record ID and Creation

This section of the record is not repeatable, and should appear only once per record.

Record ID Number (RDA 11.12.0.1)

Enter an identification number for the record. Numbers should include the prefix "EAC", a hyphen, the year, another hyphen, and then a five digit number (e.g., "EAC-2008-00001").

Creator

Enter the MARC organization code of the institution responsible for the creation of the record. For this project, this should be "UPB".

Identity and Description

This section of the record is not repeatable, and should appear only once per record.

Authorized Form of Name

Enter the name exactly as it appears in the Library of Congress Name Authority File (LCNAF), available at http://authorities.loc.gov/.

Library of Congress Control Number

Enter the Library of Congress Control Number (LCCN) for the authority record used in the previous field. LCCN appears in the LCNAF record as field 010.

Establishment Date (DACS 10.27, RDA 11.5.2)

Enter the year of the founding of the organization in an ISO-8601-compatible format (i.e., YYYY).

Abolition Date (DACS 10.27, RDA 11.5.3)

Enter the year of the dissolution of the organization in an ISO-8601-compatible format (i.e., YYYY).

Location* (DACS 10.28, RDA 11.4)

Enter the location of the head office, or the geographical region in which the organization carries out its activities. Record the name as it appears in the LCNAF, substituting a comma for the parentheses (e.g., "Provo, Utah").

Location fields (marked with an asterisk) may be repeated as necessary within the Identity and Description section, if multiple locations are associated with an organization.

Dates of Association* (DACS 10.27)

Enter the date of the creation of the record in an ISO-8601-compatible format (i.e., YYYY/YYYY). Open date spans should be entered with a terminal date of "9999".

Functions (DACS 10.30, RDA 11.10)

Enter information on the functions and activities performed by the organization. Description should be narrative in form, but include function terms should be taken from the Getty's Art and Architecture Thesaurus (available at http://www.getty.edu/vow/AATHierarchy?find=&logic=AND&note=&subjectid=300054593) functions facets where possible.

Assets and Administrative Structure (DACS 10.31)

Enter information on both the internal and external structure of the organization, as well as the dates of any changes to that structure. Name any immediately superior entities, and describe the nature of the relationship. These relationships should also be entered in the Entity Relationships section.

Administrative History (DACS 10.26-36, RDA 11.1)

Enter historical information relevant to understanding the organization's functions, activities, and relations with other entities. Administrative history should begin with a brief summary, including the organization's name, dates of existence, main functions or activities, and geographic locations. History should be narrative in form, and include the following elements where applicable:

  • Dates of founding and/or dissolution;
  • Geographical areas;
  • Predecessor and successor bodies;
  • Names of the corporate bodies;
  • Names of chief officers;
  • Any other important information.
  • History should not include detailed descriptions of elements previously described, including:
  • Functions;
  • Assets and administrative structure.

For additional guidance and examples, please consult Describing Archives: A Content Standard.

Entity Relationships

Entities relationships may be repeated as needed, with one entry for each relationship.

Entity Name (RDA 32.1.0.3b)

Enter the name exactly as it appears in the Library of Congress Name Authority File (LCNAF), available at http://authorities.loc.gov/, or otherwise recorded in the wiki.

Type of Relationship (RDA 29.5, 32.1.0.3.2)

Enter the type of relationship existing between the organization and the entity listed above. These relationships may indicate immediate administrative relationships, predecessor and successor bodies, and other relationships. Valid relationship types include:

  • Superior to;
  • Subordinate to;
  • Earlier unit;
  • Later unit;
  • Associated with.

Dates of Relationship

Enter the date of the creation of the record in an ISO-8601-compatible format (i.e., YYYY/YYYY). Open date spans should be entered with a terminal date of "9999".

For dates of changes in name or merger, only enter the date of the change. Date should also be recorded in an ISO-8601-compatible format.

Resource Relationships

Resource relationships may be repeated as needed, with one entry for each relationship.

Archival Resource Name

Enter the title of the archival resource associated with the organization, as it appears in the top-level of the library catalog record or finding aid.

Materials Call Number

Enter the call number for the resource associated with the organization, as it appears in the catalog record or finding aid.

Type of Relationship

Optionally, enter the type of relationship existing between the archival resource and the organization. These relationships may whether the organization is the creator of the materials, their subject, or another relationship. Valid relationship types include:

  • Creator of (the described entity is the creator of the resource or record);
  • Destroyer of (the described entity destroyed the resource or record based on an appraisal decision);
  • Controller of (referenced resource is controlled in some way by the described entity);
  • Causa of (related resource is or describes the mandate or charge for the described entity);
  • Subject of (related resource describes or is about the related entity);
  • Other (other relation).

Sources

References to source materials for all information in the record should be included in this section. Entries typically take the form:

{Title of source}, {date of source}: p. {page number of source information} ({information gathered})

Additional information on the formulation of source entries can be obtained from the Name Authority Cooperative Program (NACO) Participants Manual, pages 36-60.