Guidelines to EAD Best Practices (Version 3.1) May 2011

Arizona Archive Online Guidelines to EAD Best Practices (version 3.1) May 2011

Best Practices Working Group Todd Welch, Northern Arizona University (chair) Lauren Amundson, Lowell Observatory David Botts, Flagstaff Public Library Jonathan Pringle, Museum of Northern Arizona Arizona Archive Online 2011

Arizona Archives Online (AAO) Best Practices

Table of Contents Page

Purpose of Best Practices 3 Encoding schemes 3 Minimum Required Elements for Core AAO Finding Aid 5 Hidden Collections 6 Encoding Hierarchical vs. Flat Arrangement within the element 7 Describing Archives: a Content Standard (DACS) 9 Order of elements 9 Nesting and Repeating elements 10 Filing Titles 10 Entering dates 11 Heading elements (i.e. Labels) 12 Special character encoding 12 Punctuation and Empty elements 13 Special formatting of text: and elements and the use of the RENDER attribute 13 Special formatting of text: <list> and <item> elements 14 Linking to digital objects and external content 15 Long guides 17 Validating and Creating well-formed guides 18 Naming, Saving, and Updating a finding aid file 17 Editing and Updating an existing finding aid file 19 Note on Using EAD Guideline Tables 19 Page 1 of 67 Arizona Archive Online 2011 EAD Guideline Tables Table 1: <eadheader> and <frontmatter> 21 Table 2: <archdesc> 26 Table 3: <dsc> 42 Table 4: Digital objects and external links 48 Appendix: Sample of finding aid based on AAO Best Practices 52 Bibliography 67 Page 2 of 67 Arizona Archive Online 2011 Purpose of Best Practices  Ensure basic uniformity when encoding and submitting AAO finding aids  Promote efficient uploading procedures to AAO web site  Revise and realign best practices with other EAD consortium efforts  Enhance access to archival descriptions for end users Encoding schemes Arizona Archives Online (AAO) contains descriptions for much of the archival materials held by member repositories within the state of Arizona—from single items and small collections to complex, multilevel collections. Given this fact and that repositories work with different collecting focuses and operating constraints, it is impractical and inefficient to describe the entire range of archival materials to the same degree. Some similar types of materials that comprise the entirety of a collection, such as the minutes of a single committee or diaries of an individual, can be described at the collection level (i.e. a container list <dsc> section may not be necessary). Other collections comprised of multiple homogeneous series, such as the outgoing correspondence of an administrator or minutes of a committee, can be described at the series or subseries level. Consequently, not all archival description needs to contain in-depth information to the folder or item level. Encoding Levels Basic The basic scheme is used for guides that reflect a single level or nonhierarchical descriptive output. It can be used for homogenous archival materials described at any level, including collections, record groups, fonds, record series, or subseries. The basic scheme can also be used for small or single-item collections or “hidden collections” not yet fully processed or not expected to be processed for some time. (See discussion on “Hidden Collections” below). Page 3 of 67 Arizona Archive Online 2011 Examples of collection where a Basic encoding level may be implemented:  Small collections, including single-item collections  Large homogeneous collections (e.g., the minutes of a committee, diaries of an individual)  Collections not yet fully processed or not expected to be processed for some time. Although repositories are generally encouraged to describe materials as completely as possible, these collections may not warrant component descriptions or a detailed listing of files or items <dsc> (i.e. container listings). In the case of “Hidden Collections”, detailed descriptions to the file and item level may not be available. Full The full encoding level should be used for multilevel or hierarchical descriptive output. The <archdesc> description of archival materials can begin at any level, but most often multilevel description begins at the “collection” or general level to “series” “subseries” “file” (more specific) level. Most fully-processed collections will use the <dsc> section to provide a detailed listing of archival materials at the “series” level and, subsequently, the “file” level. Some archival descriptions may provide description to the “item” level, but often the “file” level will suffice. This encoding scheme does not require that each subdivision in the collection be described to the file or item level, but all repositories are strongly encouraged to describe archival materials as completely as possible. Examples of collections where a Full encoding level may be implemented:  Records of a business, association, or organization  Papers of a politician, civic leader, or family  Record series of a political office or governmental agency Page 4 of 67 Arizona Archive Online 2011 Minimum Required Elements for Core AAO Finding Aid Below is an example of the elements that have the status Req in the AAO Best Practice Guidelines. This Core AAO Finding Aid provides for a basic level of description. This example is appropriate for in cases involving small collections or single items, larger homogenous collections, and hidden or unprocessed collections that will not be fully processed for some time. Other elements may be added where appropriate to provide additional information regarding the described materials. For more on submitting Hidden or unprocessed collections to the AAO web site (see Hidden Collections section). <ead> <eadheader> <eadid> <filedesc> <titlestmt> <titleproper> <date> <titleproper> [Filing Title] <publicationstmt> <publisher> <address> <addressline> <date> <profiledesc> <langusage> <language> <frontmatter> <titlepage> <titleproper> Page 5 of 67 Arizona Archive Online 2011 <date> <num> <publisher> <archdesc> <did> <unitid> <unittitle> <unitdate> <physdesc> <extent> <abstract> <langmaterial> <language> <repository> <corpname> </did> <scopecontent> <accessrestrict> Hidden Collections In an effort to provide and alert end users of all primary resources held by Arizona repositories, member institutions are developing standards for encoding unprocessed collections. Finding aids for unprocessed collections convey basic descriptive and administrative information to users to promote resource discovery, explain terms of access, and contact information for users to request access to these archival materials. The Description of Subordinate Components or container list <dsc> element is not required when describing an unprocessed collection. If creating a <dsc> with the finding aid, encoding the LEVEL attribute to "analyticover" and supply summaries of subdivisions of an unprocessed collection. Page 6 of 67 Arizona Archive Online 2011 Basic <archdesc> elements to be used when creating finding aids for a Hidden Collection include: <unitid>, <unittitle>, <unitdate>, <physdesc>, <abstract>, <repository>, <langmaterial>, <scopecontent>, and <accessrestrict>. In addition, nested elements for these elements should be used. Encoding Hierarchical vs. Flat Arrangement within the <dsc> element Within the Description of Subordinate Components or container list <dsc> element, EAD uses a system of numbered <c0x> component tags to capture the organization and description of a collection. There is no fixed correspondence between a component tag and the intellectual level -- a component tag is merely a wrapper used to encode nested, hierarchical arranged descriptions. There can be variance between a <c02> element within the same guide (i.e. it may serve to encode a file in one section of a container list and an item in another section). When providing a hierarchical description, use the <c01> down to the necessary <c0x> component to describe each unit. Always used numbered component elements. The LEVEL attribute with an allowable value is required to distinguish each unit. The LEVEL value must be one of the following: class, collection, file, fonds, item, otherlevel, recordgrp, series, subfonds, subgrp, subseries. The use of these encoding guidelines will facilitate indexing, style sheet rendering, and display of the finding aid data. If a collection has a "flat" arrangement, use <c01> tags to describe each unit. The LEVEL attribute with an allowable value is required to distinguish each unit. The LEVEL value must be one of the following: class, collection, file, fonds, item, otherlevel, recordgrp, series, subfonds, subgrp, subseries. Hierarchical arrangement <c01 level="series"> <did> <unitid>Series I</unitid> <unittitle>Re-election Records</unittitle> <unitdate>2008</unitdate> </did> <c02 level="subseries"> <did> <unittitle>Donor Correspondence</unittitle> <unitdate>October 2008</unitdate> Page 7 of 67 Arizona Archive Online 2011 </did> <c03 level="file"> <did> <container type="Box">1</container><container type="folder>1</container> <unittitle>Ohio donors</unittitle> </did> </c03> <c03 level="file"> <did> <container type="Box">1</container><container type="folder>2</container> <unittitle>Oklahoma donors</unittitle> </did> </c03> <c03 level="file"> <did> <container type="Box">1</container><container type="folder>3</container> <unittitle>Oregon donors</unittitle> </did> </c03> </c02 </c01> Flat arrangement <c01 level=”file”> <did> <container type="folder">1</container> <unitid>NAU.ARC.1996.5.1</unitid> <unittitle>Spring Football Camp</unittitle> <unitdate>1996</unitdate> </did> </c01> <c01 level=”file”> <did> Page 8 of 67 Arizona Archive Online 2011 <container type="folder">2</container> <unitid>NAU.ARC.1997.5.1</unitid> <unittitle>Spring Football Camp</unittitle> <unitdate>1997</unitdate> </did> </c01> <c01 level=”file”> <did> <container type="folder">3</container> <unitid>NAU.ARC.1999.5.1</unitid> <unittitle>Spring Football Camp</unittitle> <unitdate>1999</unitdate> </did> </c01> Describing Archives: a Content Standard (DACS) In order to promote interpretability within the AAO database of finding aids and beyond, AAO institutions are highly encouraged to observe the guidelines for describing archival materials regardless of format as provided for in Describing Archives: a Content Standard, particularly when supplying archival description above the <dsc> section The standard provides guidance on describing the content and context of archival materials, as well as instruction on describing creators and forming names (controlled vocabulary). Order of elements The AAO Best Practice Guidelines present EAD elements in a preferred sequence. It is not required that repositories follow this sequence, it is encouraged that they follow the order in which the elements are listed in the tables to enhance the review and formatting of finding aids. The grouping, rendering and public display of the elements within a finding aid will be controlled by the AAO style sheet. Page 9 of 67 Arizona Archive Online 2011 Nesting and Repeating elements EAD elements may be nested as allowed by the EAD Tag Library (see the “May contain” section of each element description). The repeatability of each element (i.e., more than one occurrence of an element may be used) is also stated in the Status column of the detailed element tables. When the (paragraph) element is allowed within another element, it may be repeated as often as necessary (e.g. <bioghist>, <scopecontent>, <accessrestrict>, <userrestrict>, <prefercite>, <relatedmaterial>, <arrangement>, etc.). Filing Titles In order to insures that collection titles can be sorted and displayed alphabetically from the AAO web site, repositories are required to adopt the encoding practice of utilizing a second occurrence of the <titleproper> element in the EAD header to hold the filing title. See the <eadheader> Table (table 1) under <titleproper> for details and examples of using the second <titleproper> [filing title] element. The <titleproper> used for filing title has been inserted into each repository’s template. Examples of filing title <titleproper> element:  Personal name (invert last name and enclose first name in parenthesis):  <titleproper type="filing" altrender="nodisplay">Udall (Morris K. and Stewart) Papers</titleproper>  Family name (direct heading):  <titleproper type="filing" altrender="nodisplay">Day Family Diaries</titleproper>  Business, organization, or association name (direct heading): Page 10 of 67 Arizona Archive Online 2011  <titleproper type="filing" altrender="nodisplay">Blue Moon Publishing Company Records</titleproper> Entering dates All <unitdate> Date elements above the <dsc> Description of Subordinate Components element must contain a NORMAL attribute for encoding normalized dates. For those <unitdate> elements above the <dsc> Description of Subordinate Components element, but within the <archdesc> element, use the four-digit year format ("YYYY") only. The <date> element found within the <eadheader> element (i.e. <filedesc>, <publicationstmt>, <profiledesc>, <revisiondesc>, and <frontmatter>) can be normalized according to the International Standard Organization (ISO) 8601 standard to the year, month and day. Designating the time of day is not necessary and should not be included. Example of encoded date(s): Inclusive and Bulk dates – use TYPE attribute to distinguish between "inclusive" and "bulk" dates <unitdate type="inclusive" normal="1992">1992</unitdate> <unitdate type="inclusive" normal="1980/1983">1980-1983</unitdate> <unitdate type="bulk" normal="1970/1985">(bulk 1970-1985)</unitdate> Broken dates (e.g., "1900, 1905-1918") – use separate </unitdate> elements <unitdate type="inclusive" normal="1900">1900,</unitdate><unitdate type="inclusive" normal="1905/1918">1905-1918</unitdate> Open date spans – set NORMAL attribute to 9999 for [ongoing] <unitdate normal="1962/9999">1962-[ongoing]</unitdate> Page 11 of 67 Arizona Archive Online 2011 Approximate dates – use appropriate date span in the NORMAL attribute <unitdate normal="1915/1925">ca. 1920</unitdate> <unitdate normal="1920/1929">1920s</unitdate> <unitdate normal="1901/2000">20th century</unitdate> Undated material – use approximate dates based on the earliest and latest dates the material were created <unitdate normal="1888/1931">undated</unitdate> Heading <head> elements (i.e. labels) Except within the <bioghist> element, the <head> element should not be utilized by AAO repositories. The finding aid’s headers or section titles will be controlled by the AAO style sheet and NOT by the information encoded within the <head> element. AAO repositories should select the appropriate <head> element within the <bioghist> based on whether the creator of the collection is an individual/family, business/association or governmental agency:  <head>Biographical note</head>  <head>Historical note</head>  <head>Administrative history</head> Special character encoding Page 12 of 67 Arizona Archive Online 2011 For all special characters encoded in XML, encode directly in UTF-8 Unicode, or use Unicode decimal or hexadecimal character references. Note that all decimal character references should begin with an ampersand (&) and/or pound sign (#), and end with a semicolon (;). More commonly used characters found in EAD finding aids including the following: & & (Ampersand) < < (Left angle bracket) > > (Right angle bracket) © © (Copy right symbol) Punctuation and Empty elements EAD markup should not generally include punctuation between the <unittitle> and <unitdate> elements. The style sheet will add punctuation in those cases. Punctuation is acceptable within any other given element. After completing the EAD markup process, but before loading finding aids to the AAO web site -- empty elements (i.e. tags containing no data) should be removed. Special formatting of text: <emph> and <title> elements and the use of the RENDER attribute Bold, underline, italic, and other similar kinds of formatting should be represented using the EAD <emph> tag or the <title> tag with RENDER attribute set accordingly.  <emph> for formatting a segment of text within a larger body of text. EAD Markup: <emph render="bold">Northern Arizona University</emph> defeated the <a href="/tags/University_of_Arizona/" rel="tag">University of Arizona</a> in football. Public Display: Page 13 of 67 Arizona Archive Online 2011 Northern Arizona University defeated the University of Arizona in football.  <title> for formatting the title of a book, journal, newspaper EAD Markup: The photographs were published in the Fall 2011 edition of <title render="italic">Arizona Highways. Public Display: The photographs were published in the Fall 2011 edition of Arizona Highways.

Special formatting of text: and elements

Lists should be represented using the EAD tag with nested tags for each entry in the list. Lists can be inserted into elements contained within the (content, context, and extent of the entire body of the archival material) and (detailed listing of files). Set the TYPE attribute to select the type of list desired (i.e. "simple", "deflist", "marked", "ordered").

EAD Markup:

Collection consists of four series: I. Correspondence II. Minutes III. Reports IV. Bank statements

Public Display (style sheet rendered): Arrangement and organization

Page 14 of 67

Arizona Archive Online 2011

Collection consists of four series: I. Correspondence II. Minutes III. Reports IV. Bank statements

Linking to digital objects and external content

Table Four provides guidelines for external linking to digital resources or associated digital objects that are and are not part of the materials being described by the finding aid.

Linking to Digital Objects from the finding aid

Use the Digital Archival Object Group element, with its child elements Resource, Digital Archival Object Location, and ARC, for references/links to digital representations of collection items described in the finding aid. The element allows for only one digital object, while allows for one or more digital objects to be nested. In order to maintain consistency, AAO recommends that institutions use the element approach to linking to one or more digital objects within a finding aid. The element should be nested with the following subelements: , , , and .

The elements may be included in the following EAD elements: , , , , any component group, , and .

Example of linking digital object to finding aid:

Photographs of Bruce Babbitt and family members 1967-2004

Page 15 of 67

Arizona Archive Online 2011

Sample digitized image from this file: Bruce Babbitt portrait, 28 May 1988.

External linking (pointers and reference tags)

All external linking should be encoded using the Extended Pointer or the Extended Reference tags with the HREF attribute. While the and elements found in the EAD.DTD do allow external linking, it is recommended the members use the Extended Pointer or the Extended Reference tags with the HREF attributes instead.

The element is an empty external linking tag, but the element can include text and subelements as part of its reference to an electronic object external to the finding aid. AAO repositories are strongly encouraged to use the HREF attribute. The use of the ENTITYREF attribute with an associated entity declaration at the top of the finding aid markup for establishing a destination for the link, such as a URL is not recommended.

For external linking elements, the AAO stylesheet default behavior will be to render links as SHOW="replace" (i.e., the linked resource will be displayed in the same browser window). The stylesheet will support SHOW="embed" for images only (i.e., the image will be displayed inline in the finding aid) and SHOW="new" (i.e., the linked resource will be displayed in a new browser window). Use of any other SHOW attribute will be rendered as the default SHOW="replace".

Example of element as an empty external linking tag to a digital object:

Page 16 of 67

Arizona Archive Online 2011

Grand Canyon River Guides Collection, 1955-2005 Processed by: Richard Quartaroli Cline Library. Special Collections and Archives Department.

Example of element providing hypertext with an external link to external content (i.e. link to another AAO finding aid):

Grand Canyon Trust Collection

Long guides

Each XML finding aid file must be a complete finding aid. Do not divide the finding aid into smaller subparts. Longer guides will be pre-processed and indexed for searchability on the AAO web site and viewable pdf documents will be delivered to end users.

Page 17 of 67

Arizona Archive Online 2011

Validating and creating well-formed guides

To ensure compliance with the EAD.DTD, contributing repositories should validate and check that their new and updated finding aid files are well-formed prior to uploading to the AAO web site. While most invalid guides will load and index, poorly formed finding aid files will not. To maintain the integrity and effectiveness of the best practices, contributing repositories are strongly urged to validate their guides with software designed as an XML editor, such as XML Editor or Adobe Dreamweaver.

Naming, Saving, and Updating a finding aid file

After opening a new finding aid template file, it's a good idea to use the “save as” command and name the file immediately – to ensure that your institutional template is not altered. As a safeguard, a copy of each institution’s template will be available from the Arizona Archives Online (AAO) web site.

The AAO best practices strongly encourages that institutions use a consistent naming convention for saving and submitting their finding aid files, such as incorporating an institutional abbreviation (i.e. “UA“) or implementing the MARC code as a prefix with an underscore to uniquely identify their files.

If your institution does not have an existing MARC code, instructions for requesting a code for your institution can be found on the Library of Congress MARC Code List for Organizations web page. Existing MARC codes can be found at http://www.loc.gov/marc/organizations/orgshome.html#searches.

Existing AAO Members MARC codes: Arizona Historical Society/Northern Arizona Division AzFHi Arizona Historical Society/Southern Arizona Division AzTP Arizona State Library, Archives, and Public Records Az Arizona State Museum AzTuSM Arizona State University AzTeS Center for Creative Photography AzU-CCP Heard Museum AzPhBJB Museum of Northern Arizona AzFM Northern Arizona University AzFU

Page 18 of 67

Arizona Archive Online 2011

Postal History Foundation AzTuPHF Sharlot Hall Museum AzPrSH University of Arizona AzU

File Naming Reminders: Filenames must end with an .xml extension Filenames may include upper and lowercase letters, numbers, and underscores Filenames should contain no spaces or dashes. Spaces and dashes will affect the AAO indexing functionality!

Filename examples: AzFM_MS608.xml AzFM is the MARC code for the Museum of Northern Arizona, MS608 is the collection number assigned to the collection by the Museum of Northern Arizona.

Editing and Updating Existing Finding Aids

If a finding aid file is edited or updated and resubmitted to the AAO web site, do not assign a new filename to the updated file (use the original or identical file name). If the updated finding aid file is intended to replace the previous version of the file -- it must have exactly the same filename. When uploading an edited guide with an ftp program, a dialog box should warn you that the existing file on the AAO web site will be overwritten. Click the ‘yes’ button to replace the original file residing on the AAO web site. The AAO index is updated automatically at night.

Note on Using EAD Guideline Tables

Elements/Attributes – Encoded Archival Description tag and underlying attributes allowed for each tag. Status -- The guidelines indicate whether an element is required or not by using one of the following four codes:

Req = Required. This EAD tag is required as described in the Notes column.

MA = Mandatory when applicable. This EAD tag is mandatory when the information is available or discernable as described in the Notes column.

Page 19 of 67

Arizona Archive Online 2011

Rec = Recommended. This EAD tag is strongly recommended in order to facilitate access to a collection as described in the Notes column.

Opt = Optional. The EAD tag may be used if desired.

Repeatable? – Column indicates whether element can (Y) or cannot (N) be repeated within the archival finding aid.

Comments/Application Notes – Explanation and examples of tag element and attribute use. In addition, it contains any special instructions or comments relevant to the element or attribute in question. Encoding Analogs – Serves as ‘crosswalks between EAD elements and the Describing Archives: A Content Standard (DACS).

Page 20 of 67

Arizona Archive Online 2011

Table 1: and

Elements and Attributes Status Repeatable? Comments/Application Notes DACS

Elements are surrounded by angle Req=Required brackets and rendered in MA=Mandatory, if applicable boldface. Rec=Recommended by best practices guidelines Opt=Optional stylesheet declaration A style sheet declaration will not be part of the standard AAO template. If you would like to render or view the finding aid in a web browser (Microsoft IE), it is possible to add a style sheet declaration to the template. Please delete declaration after viewing and before uploading to the AAO web site.

Example:

Place the guide and the stylesheeet (template.xsl) in the same directory to render in Microsoft Internet Explorer. DOCTYPE declaration Req The DOCTYPE declaration points to the name, version, and location of the XML.DTD (document type definition) or rules used to create and valid the xml document. This declaration is presence in all AAO templates. Here is the declaration used in AAO templates:

Req N Parent or top “wrapper” element for an EAD finding aid. Req N Wrapper element containing information about the finding aid document. langencoding="iso639b" Req Set to “iso639-2b“. Conveys the standard used for language codes. scriptencoding="iso15924" Req Set to “iso15924“. Conveys the standard used for script codes. relatedencoding="dc" Req Set to “dc”. dc stands for “Dublin Core” Indications the metadata schema used

Page 21 of 67

Arizona Archive Online 2011

to map elements for indexing and discovery. repositoryencoding="iso15511" Req Set to "iso15511". Conveys the standard used for establishing repository codes. countryencoding="iso3166-1" Req Set to “iso31661.” Conveys the standard used for country codes. dateencoding="iso8601" Req Set to “iso8601.” Conveys the standard used for date formats. Req N EAD identifier. This element and its attributes are used to provide unique information about the specific EAD finding aid. countrycode="us" Req States the country code using the iso3166-1 format. 2.1.5 mainagencycode= Req Use the repository code supplied by the Library of Congress for your institution. 2.1.4 The code should follow the iso15511 format. Repository codes and instructions for requesting a code for your institution can be found on the Library of Congress MARC Code List for Organizations web page. publicid Enter the full name of the repository/institution where archival materials reside. encodinganalog="identifier" Req Maps element to Dublin Core identifier field. Req N Wrapper element for bibliographic information of finding aid. Req N Wrapper element for finding aid title information. Req N Use for the official title of the finding aid (i.e. Inventory of the Morris Udall Papers). encodinganalog="title" Req Maps element to Dublin Core title field. Req N The element is used to convey the span of dates of described materials. The use element should be within the element. (i.e. Inventory of the Morris Udall Papers 1933- 1980.). era="ce" Rec Default value presence in AAO templates. calendar="gregorian" Rec Default value presence in AAO templates. normal= Req Enter normalized date span of described materials. Use the iso8601 format (e.g. normal="1933/1980"). encodinganalog="date" Req Maps element to Dublin Core date field. [filing title] Req This instance of is a modified form of the title used to alphabetically sort by collection titles. The filing title should start with a person’s last name, followed by the first name and, if used, middle initial of the creator, collector, or associated individual in enclosed with parenthesis. Filing rules for corporate bodies (businesses, associations, or organizations) should be listed as they appear in the initial element.

Here are some examples of filing title for (without EAD elements):

Page 22 of 67

Arizona Archive Online 2011

Udall (Morris K.) Papers Udall (Morris K. and Stewart) Papers Day Family Diaries Blue Moon Publishing Company Records United Indian Traders Association Photographs type="filing" Req States that this element is intended for filing purposes. altrender="nodisplay" Req States that this element is not intended to be used for Web or print display. MA N Name of person(s) or institution responsible for creating the intellectual content 8.1.5 of the finding aid. encodinganalog="creator" MA Maps element to the Dublin Core creator field. Req N Wrapper element for information about publication of finding aid. Req Y Name of publisher of finding aid. Usually the name of the repository housing the archival collection. Req Maps element to the Dublin Core publisher field. encodinganalog="publisher" Req N Date of publication of finding aid. era="ce" Rec Default value presence in AAO templates. calendar="gregorian" Rec Default value presence in AAO templates. normal= Req Enter normalized date, publication date, or copyright date for finding aid. Use the iso8601 format (e.g. normal="2011"). encodinganalog="date" Maps element to the Dublin Core date field.

Req Y Wrapper element for the address of the repository housing the described archival materials. Req Y The element is repeatable as needed to list the repository name, street address, city, state, zip code, phone number, fax number, email address, and repository URL. Req N Wrapper element to record information about encoding version and the language(s) of the finding aid. MA N Statement describing the creation or encoding of the finding aid. Lists name of 8.1.5 encoder(s) and/or institution, if available. Rec Date of original encoding in EAD. 8.1.5 era="ce" Rec Default value presence in AAO templates. calendar="gregorian" Rec Default value presence in AAO templates. normal= Rec Enter normalized original date of encoding. Use the iso8601 format (e.g. If the original creation date for encoding of March 2011 should be entered like this:

Page 23 of 67

Arizona Archive Online 2011

normal="2011-03").

March 23, 2011 should be entered like this: normal="20110323” Req N Statement about the language(s) that are used in the encoded finding aid. Req Y Repeat the element as needed to encode each language represented in the text of the finding aid.

Do not confuse with the element used in the section of the EAD guide used to specify the language(s) represented in the materials that comprise the collection being described. encodinganalog="language" Req Maps element to the Dublin Core language field. langcode="eng" Req Refer to iso639-2b for the correct language code. AAO templates are set to default value: langcode="eng" scriptcode="latn" Req Refer to iso15924 for correct script code. AAO templates are set to default value: scriptcode="latn" Rec N Record information about significant changes that were made to the original encoded finding aid. Use the element to record each major revision. Each major revision should contain a description of the change using the element and the date of the change using the element. Rec Y Wrapper element containing descriptive information about the change, as well as the date of the revision. Rec Y Describes specific significant revision made to the original encoded finding aid. 8.1.5 Rec Y Date of revision (e.g. April 2011). 8.1.5 era="ce" Rec Default value presence in AAO templates. calendar="gregorian" Rec Default value presence in AAO templates. normal= Rec Enter normalized date of significant revision to encoding. Use the iso8601 format (e.g. If the revision date for encoding of March 2011 should be entered like this: normal="2011-03").

March 23, 2011 should be entered like this: normal="20110323”

Req N AAO templates will contain this wrapper element. The AAO style sheet will render and display the text encoded within the wrapper elements prominently at the beginning of each finding aid. Req N The use of the wrapper element accommodates the display of the collection title, collection dates, local call number, and repository name. Req N Duplicate the title of the finding aid from the section. (i.e.

Page 24 of 67

Arizona Archive Online 2011

Inventory of the Morris Udall Papers). – not used for alphabetizing (do not invert). encodinganalog="245$a" Req Maps element to MARC title field. Req N The element is used to convey the inclusive span of dates of described materials. The use element should be within the element. (i.e. Inventory of the Morris Udall Papers 1933- 1980.). Req N The element is used to convey the local call number(s) described in the finding aid. Use the element to provide line breaks between multiple local call numbers. (i.e. NAU.MS.280NAU.PH.99.10). Req N The element is used to name of the repository housing the archival collection.

Req Y Add a

Page 25 of 67

Arizona Archive Online 2011

Table 2:

Elements and Attributes Status Repeatable? Comments/Application Notes DACS

Elements are surrounded by angle Req=Required brackets and rendered in boldface. MA=Mandatory, if applicable Rec=Recommended by best practices guidelines Opt=Optional Req N Wrapper element for archival description of materials being described in the finding aid. level="collection" Req Attribute used to define portion of the materials being described in the Chap. 1 finding aid.

AAO encourages the use of the following level attribute values: "collection" "recordgrp" "series" “subseries" "otherlevel"

AAO templates will have the default value of "collection". relatedencoding="marc21” Req Defines the encoding system (i.e. MARC for the 21st Century) used to map elements.

AAO templates will have the marc21 default values entered at the top level of the level. Req; N Wrapper element for core information about the described collection/record group. should be used at the top-level or at any component level .

Req Y This element is considered an essential element for data exchange by 2.1.3 ISAD(G)v2. Enter local “call number” or “control number” used to identify archival materials being described. encodinganalog="099" Rec AAO templates will have the default value of "099". countrycode="us" Req AAO templates will have the default value of "us". 2.1.5 repositorycode= Req AAO templates will have the value of the repository. The code should 2.1.4 follow the iso15511 format. Repository codes and instructions for requesting a code for your institution can be found on the Library of Congress MARC Code List for Organizations web page.

Page 26 of 67

Arizona Archive Online 2011

MA N Wrapper element containing information about the individual or 2.6 organization responsible for the creation, accumulation, or assembly of the described materials before their incorporation into an archival repository. This tag may be used to indicate records creators, collectors, and dealers. creation, accumulation, or assembly of the described materials before 14 their incorporation into an archival repository. This tag may be used to indicate records creators, collectors, and dealers.

- use when an individual is the creator/collector of the materials. - use when a family is the creator/collector of the materials. - use when a business or association is the creator/collector of the materials. encodinganalog="100|110|111” Rec Enter "100" for personal name; "100" for family name; "110" for corporate name; "111" for meeting or conference name. Note that both the name of an organization (MARC 110) and the name of a meeting or conference (MARC 111) are mapped to the EAD element. role="creator|collector|photographer" Rec What is the defined role of the entity contained in the element. source="lcnaf" Rec If the name was found in the LC Name Authority File, enter “lcnaf” in the SOURCE attribute and do not use the RULES attribute (below). rules="aacr2|dacs" Rec If the name was not found in the LC authority file but was formulated using DACS or AACR2 rules, enter “dacs” or “aacr2” in the RULES attribute and do not use the SOURCE attribute (above).

Req Y The title [transcribed or supplied] of the described materials. 2.3

If the collection title includes within it the name of a publication, such as the title of a magazine, periodical, or newspaper, enclose the publication name in a element, and set the <title> element’s RENDER attribute to "italic". encodinganalog="245$a" Rec Default value presence in AAO templates, maps to the MARC title field. <unitdate> Req Y US repository following APPM practice normally include <unitdate> as part 2.4 of <unittitle>, whereas British and Canadian practice, following ISAD(G)v2 use <unitdate> at the same level as <unittitle>. Given the trend for further Page 27 of 67 Arizona Archive Online 2011 international standardization, separate title and date is preferred but both practices are permitted. DACS separates <unittitle> from <unitdate> and should be considered the descriptive standard for encoding. Repeat <unitdate> if both inclusive and bulk dates are given. This element is considered an essential element for data exchange by ISAD(G)v2. Use for the creation year, month, or day of the described materials. type="inclusive|bulk" Req Use "inclusive" for the entire date range; use "bulk" only as a repeat <unitdate> instance where predominant dates are present and might give the user a better indication of the bulk or majority of the collection’s dates. AAO templates will have the default value of "inclusive" – but repositories should use a repeated instance of <unitdate> for "bulk" when they feel its’ warranted. normal= Req Enter normalized date span of described materials. Use the iso8601 format (e.g. normal="1933/1980"). encodinganalog="245$f|245$g" Rec "245$f" for inclusive dates; “245$g” for bulk dates. AAO templates will have the default value of "245$f". <physdesc> Req Y A wrapper element for physical details about the described materials. Use 2.5 subelements <extent>, <physfacet>, <dimensions>, and if desired, <genreform> to record the information. <extent> Req Y State extent of space occupied (in linear or cubic feet) and/or number of 2.5 containers and/or items. If desired, include additional details concerning types and formats of material, as in the first example below. Use separate <extent> tags inside a single <physdesc> to state the same information in different ways (e.g., one <extent> element for cubic feet and another <extent> element for number of containers, both nested inside the same <physdesc> element). For example: <physdesc> <extent>2.5 cubic feet, including textual materials, photographs, and videocassettes</extent> <extent>5 boxes</extent> </physdesc> <physdesc> <extent>738 photographic prints</extent> Page 28 of 67 Arizona Archive Online 2011 <extent>37 glass negatives</extent> encodinganalog="300$a" Rec AAO templates will have the default value of "300$a". <physfacet> Opt N Use to record physical facet of material being described. For the proper 2.5 (Purpose terms and syntax for describing the physical aspects of specific types of and Scope); non-textual materials, consult the appropriate list in DACS. Appendix B See EAD tag library for information on use of this element. <dimensions> Opt N Use to record the specific measurement for certain types of materials, 2.5 (Purpose such as the height and width of photographs or the size of audio and video and Scope); tapes). Appendix B See EAD tag library for information on use of this element. <materialspec> Opt N Use to record other descriptive information about the material being 2.5 (Purpose described, such as the recording speed of reel-to-reel tapes or the and Scope); projection used to create a map. Appendix B See EAD tag library for information on use of this element. <abstract> Req N User for brief descriptive information of collection contents at highest 3.1 level, in addition to <scopecontent> for fuller discussion. At compontent level, use <scopecontent> rather than <abstract>. encodinganalog="520" Rec AAO templates will have the default value of "520". <langmaterial> Req N Wrapper element naming the language(s) found in the described materials. One or more language name(s) are enclosed in a nested <language> element. If the collection, such as a photograph collection, contains no associated text, state that fact in <langmaterial> using wording similar to the following: <langmaterial>No textual or other language materials are included in the collection.</langmaterial> <language> MA Y Nested within the <langmaterial> element, use to encode the language of the materials being described: <langmaterial>Diary entries written in <language langcode=”fre”>French</language> and <language langcode=”ger”>German.</language>. Page 29 of 67 Arizona Archive Online 2011 langcode="eng" MA Use ISO 6392b to determine correct language code. AAO templates will have the default value of "eng". – if another language, change to correct language code. encodinganalog="546" Rec AAO templates will have the default value of "546". <repository> Req N Wrapper element for institution or repository that houses and provides access to the described materials. <corpname> Req N Name of the repository (e.g. Center for Creative Photography or Museum 2.2.2 of Northern Arizona). encodinganalog="852$a" Rec AAO templates will have the default value of "852$a". <subarea> MA Y If there is a secondary administrative level within a repository, use the 2.2.2 <subarea> to note the name of the secondary level. (e.g. Arizona Collection). encodinganalog="852$b" Rec AAO templates will have the default value of "852$b" – for repositories’ templates where a secondary level exists. <address> MA Y Wrapper element used to encode the address information for the 2.2.3 repository. <addressline> MA Y Use one <addressline> element for each line of postal or other address information; repeat as many times as necessary to include all lines of address, if desired. May contain email address, contact phone number(s), etc. For example: <addressline>P.O. Box 6022 </addressline> <addressline>Flagstaff, AZ 86011-6022</addressline> <addressline>928-523-5551</addressline> <addressline>special.collections@nau.edu</addressline> <addressline> http://www.nau.edu/library/speccoll/ </addressline> <accessrestrict> Req N Use to record Information about conditions that affect the availability of 4.1; 4.2 the described materials being described. May indicate the need for an appointment or the natural of the restrictions imposed by the donor, legal statue, repository, or other agencies. Should also include lack of restrictions (i.e. “No restrictions on access”). Do not confuse with conditions governing use. Text should be enclosed in paragraph tags . If needed, the paragraph tags are repeatable within the <accessrestrict> Page 30 of 67 Arizona Archive Online 2011 element. encodinganalog="506" Rec AAO templates will have the default value of "506". <userestrict> MA N Use to record information about conditions that affect use of the 4.4 described materials after access has been granted. Examples include limitations, regulations, or special procedures imposed by a repository, donor, legal statue, or other agency regarding reproduction, publication, or quotation of the described materials. May also indicate the absence of restrictions. Text should be enclosed in paragraph tags . If needed, the paragraph tags are repeatable within the <userrestrict> element. encodinganalog="540" Rec AAO templates will have the default value of "540". <prefercite> Rec N Use to record information about how users should identify the described 7.1.5 materials when referring to them in published credits. Text should be enclosed in paragraph tags . If needed, the paragraph tags are repeatable within the <prefercite> element. encodinganalog="524" Rec AAO templates will have the default value of "524". <acqinfo> MA N Use to record immediate source of the materials being described and 5.2 the circumstances under which they were received., includes donations, transfers, purchases, and deposits. Text should be enclosed in paragraph tags . If needed, the paragraph tags are repeatable within the <acqinfo> element. encodinganalog="541" Rec AAO templates will have the default value of "541". <accruals> Opt N Use to record information about anticipated or regular additions to 5.4 described materials. Text should be enclosed in paragraph tags . If needed, the paragraph tags are repeatable within the <accruals> element. encodinganalog="584" Rec AAO templates will have the default value of "584". <custodhist> Rec N Use to record Information about the chain of ownership of the materials 5.1 being described before they reach the immediate source of acquisition. Text should be enclosed in paragraph tags . If needed, the paragraph tags are repeatable within the <custodhist> element. encodinganalog="561" Rec AAO templates will have the default value of "561". Page 31 of 67 Arizona Archive Online 2011 <appraisal> Opt N Use to record information about the process determining the archival value and thus the disposition of records based upon their current administrative, legal, and fiscal use; evidential, intrinsic, and informational value; arrangement and condition; and relationship to other records. See EAD tag library for information on use of this element. <processinfo> Rec N Use to record information about processing activities, such as 8.1 accessioning, organizing, describing, preserving, and storing the described materials. Text should be enclosed in paragraph tags . If needed, the paragraph tags are repeatable within the <processinfo> element. encodinganalog="583" Rec AAO templates will have the default value of "583". <separatedmaterial> Rec N Use to record information about materials that are associated by 6.3 provenance to the described materials, but that have been physically separated or removed. Text should be enclosed in paragraph tags . If needed, the paragraph tags are repeatable within the <separatedmaterial> element. encodinganalog="5440" Rec AAO templates will have the default value of "5440". <relatedmaterial> Rec N Element should be used to record relevant collections that are not 6.3 physically or logically included within the materials described in the collection inventory (finding aid), but that may be of use to a researcher because of an association to the described materials. Materials designated by this element are not related to the described material by provenance, accumulation, or use. Text should be enclosed in paragraph tags . If needed, the paragraph tags are repeatable within the <relatedmaterial> element. encodinganalog="5441" Rec AAO templates will have the default value of "5441". <altformavail> Rec N Use to record information about copies of materials being described, 6.2 including the type of alternative form, significant control numbers, location, and source for ordering if applicable. The additional formats are typically microforms, photocopies, or digital reproductions. encodinganalog="530" Rec AAO templates will have the default value of "530". Page 32 of 67 Arizona Archive Online 2011 <otherfindaid> Rec N Use to record information about additional or alternative guides to the 4.6 described materials, such as card files, dealers’ inventories generated by the creator or compiler of the materials. It is used to indicate the existence of additional collection inventories; it is not designed to encode the contents of those guides. Text should be enclosed in paragraph tags . If needed, the paragraph tags are repeatable within the <otherfindaid> element. encodinganalog="555" Rec AAO templates will have the default value of "555". <bioghist> MA Y Concise essay or chronology that places the archival material in context by providing information about their creator. Includes significant information about the life of an individual or family, or the administrative history of a corporate body. Text should be enclosed in paragraph tags . >. If needed, the paragraph tags are repeatable within the <bioghist> element. encodinganalog="545" Rec AAO templates will have the default value of "545". 2.7 <head> Rec Y In order to distinguish a biographical note (biographical information about the person or family who created a collection of papers), from a historical note (background information about the organization or agency that created a collection of records), the <head> element may be used inside <bioghist> to record the appropriate heading. Either use one of the following: “Biographical Note” (person or family history); “Historical Note” (historical information about a business or organization; or “Administrative History” (government agency). This is the only <head> element in the <archdesc> portion of the finding aid. All other headings are defined by the style sheet. AAO templates will leave the <head> element blank. <scopecontent> Req N Use to provide a general description of the topical range and content, 3.1 including notes on the document types and formats of the described materials. If the organization/arrangement information cannot readily be separated from the scope note, give as part of <scopecontent>. If separable, use <arrangement> and do not nest within <scopecontent>. Page 33 of 67 Arizona Archive Online 2011 Text should be enclosed in paragraph tags . >. If needed, the paragraph tags are repeatable within the <scopecontent> element. encodinganalog="520" Rec AAO templates will have the default value of "520". <arrangement> MA N Use to record the filing sequence of the described material (e.g., 3.2 alphabetical or chronological) and/or the manner in which the collection has been ordered (e.g., organized into series). Text should be enclosed in paragraph tags . If needed, the paragraph tags are repeatable within the <arrangement> element. encodinganalog="351" Rec AAO templates will have the default value of "351". <bibliography> Opt N Use to record citations to works that are based on, about, or of special 6.4 value when using the materials being described, or works in which a citation to or brief description of the materials is available. The works could be books, articles, television programs, unpublished reports, web sites, or other forms of information. Text should be enclosed in paragraph tags . If needed, the paragraph tags are repeatable within the <bibliography> element. See EAD tag library for information on use of this element. encodinganalog="581" Rec AAO templates will have the default value of "581". <controlaccess> MA Y Wrapper element that designates key access points for the described materials and enables authority-controlled searching and browsing across finding aids on a computer network. Hundreds of names and subjects can appear in a finding aid. Prominence can be given to the major ones by bundling them together in a single place within the <archdesc>. Each sub-element requires either a SOURCE -or- RULES attribute, as appropriate. Use a SOURCE attribute to encode the source (i.e., thesaurus, authority file) of an established list of indexing terms. If the term is not found in an established list, then do not use a SOURCE attribute. Use instead a RULES attribute to indicate the content standard by which the term is constructed, e.g., "lcsh", "aacr", "dacs". If the term is not Page 34 of 67 Arizona Archive Online 2011 constructed according to an established content standard, encode the RULES attribute value as "local". The <list> and <item>(s) elements, although not necessary, can nest the controlled access terms: <persname>, <famname>, <corpname>, <subject>, <geogname>, <genreform>, <occupation>, <function>, and <title>. AAO style sheet will format the controlled access terms together by type when guide is rendered in a web browser. Nested with <list> and <item> tags: <controlaccess> <list type="simple"> <item><persname encodinganalog="600" source="lcnaf">Udall, Morris K., 1922-</persname></item> <item><persname encodinganalog="600" source="lcnaf">Abbey, Edward, 1927-1989-</persname></item> <item><subject encodinganalog="650" source="lcsh">Legislators-- Arizona</subject></item> <item><subject encodinganalog="650" source="lcsh">Authors-- Arizona</subject></item> <item><subject encodinganalog="650" source="lcsh">Environmental laws—United States</subject></item> </list> </controlaccess> WIthout <list> and <item> tags: <controlaccess> <persname encodinganalog="600" source="lcnaf">Udall, Morris K., 1922- </persname> <persname encodinganalog="600" source="lcnaf">Abbey, Edward, 1927-1989- </persname> <subject encodinganalog="650" source="lcsh">Legislators--Arizona</subject> <subject encodinganalog="650" source="lcsh">Authors--Arizona</subject> <subject encodinganalog="650" source="lcsh">Environmental laws—United States</subject> </controlaccess> <persname> MA Y Access terms related to personal names of significant subjects and/or 2.6; 9; 12 contributors of described materials. Page 35 of 67 Arizona Archive Online 2011 Use the form of the name located in a standard naming authority file, such as the Library of Congress Name Authority File. If a name does not appear in an authority file, establish the name according to a content standard such as DACS, or AACR2. Controlled subheadings for personal names should be separated by a double hyphen – (with no spaces between heading terms and hyphens). Except for a period needed for a middle initial in a personal name, do not end a personal name heading with a period (.) – the AAO style sheet will supply the ending period when required by AACR2. <persname encodinganalog="600" source="lcnaf">Babbitt, Bruce E.</persname> <persname encodinganalog="600" rules="aacr2">Smith, Wilma, 1967- </persname> encodinganalog="600|700" Rec AAO templates will have the default value of "600". Change to encodinganalog="700", if <persname> in controlled access plays the role of contributor. source= MA AAO templates will leave the default value blank. If heading is found in the Library of Congress Name Authority File, assign source="lcnaf". If heading is found in an existing or legacy local catalog system, assign source="local". If heading is not found in the Library of Congress Name Authority File, delete the source attribute and use the RULES attribute to indicate how the name is established. rules= MA AAO templates will leave the default value blank. If there is no name authority record available for a particular name, establish the name heading and use "aacr2" to indicate that the name has been formulated according to AACR2 rules. If the form of the name is not based on a content standard such as AACR2, use “local” instead. Page 36 of 67 Arizona Archive Online 2011 If the name is taken from a standard name authority file, delete the RULES attribute and identify the name authority source in the SOURCE attribute. <famname> MA Y Access terms related to family names of significant subjects and/or 2.6; 9; 12.29 contributors of described materials. Since family names are not maintained by the Library of Congress Name Authority File, establish the name according to the DACS standard: State the family surname followed by the word “family.” Base the decision on published works about the family or reference sources, where available. Controlled subheadings for family names should be separated by a double hyphen – (with no spaces between heading terms and hyphens). Do not end the heading with a period. <famname encodinganalog="600" rules="dacs">Goldwater family-- Archives</famname> encodinganalog="600|700" Rec AAO templates will have the default value of "600". Change to encodinganalog="700", if <famname> in controlled access plays the role of contributor. rules="dacs" MA AAO templates will have the default value of "dacs". <corpname> MA Y Access terms related to corporate names of significant subjects and/or 2.6; 9; 14 contributors of described materials. Use the form of the name located in a standard naming authority file, such as the Library of Congress Name Authority File. If a name does not appear in an authority file, establish the name according to a content standard such as AACR2. Controlled subheadings for corporate names should be separated by a double hyphen – (with no spaces between heading terms and hyphens). <corpname encodinganalog="610" source="lcnaf">Babbitt Brothers Trading Company</corpname> <corpname encodinganalog="610" rules="aacr2">Black Bean Burrito Company</corpname> Rec AAO templates will have the default value of "610". If heading is a encodinganalog="610|611|710|711" conference name, change to encodinganalog="611". Page 37 of 67 Arizona Archive Online 2011 Change to encodinganalog="710", if <corpname> in controlled access plays the role of contributor. Change to encodinganalog="711", if <corpname> in controlled access is a conference name and plays the role of contributor. source= MA AAO templates will leave the default value blank. If heading is found in the Library of Congress Name Authority File, assign source="lcnaf". If heading is found in an existing or legacy local catalog system, assign source="local". If heading is not found in the Library of Congress Name Authority File, delete the source attribute and use the RULES attribute to indicate how the name is established. rules= MA AAO templates will leave the default value blank. If there is no name authority record available for a particular name, establish the name heading and use “aacr2” to indicate that the name has been formulated according to AACR2 rules. If the form of the name is not based on a content standard such as AACR2, use “local” instead. If the name is taken from a standard name authority file, delete the RULES attribute and identify the name authority source in the SOURCE attribute. <subject> MA Y The form of the heading should be taken from a standard thesaurus, such as the Library of Congress Subject Headings (LCSH). <subject encodinganalog="650" source="lcsh">Authors--Arizona</subject> <subject encodinganalog="650" source="lcsh">Environmental laws—United States</subject> encodinganalog="650" Rec AAO templates will have the default value of "650". source= MA AAO templates will leave the default value blank. If heading is found in the Library of Congress Subject Headings, assign source="lcsh". If heading is found in an existing or legacy local catalog system, assign Page 38 of 67 Arizona Archive Online 2011 source="local". <geogname> MA Y Access terms related to places, natural features, or political jurisdictions. Chap. 13 Take the geographic term from a standard geographic authority file, such as Library of Congress Subject Headings or the Getty Thesaurus for Geographic Names. If a term does not appear in an authority file, establish the term according to a content standard such as DACS. Controlled subheadings may be added as needed, separated by a double hyphen -- (with no spaces between heading terms and hyphens). Controlled subheadings for geography names should be separated by a double hyphen – (with no spaces between heading terms and hyphens). Do not end the heading with a period. <geogname encodinganalog="651" source="lcsh">Grand Canyon (Ariz.)</geogname> encodinganalog="651" Rec AAO templates will have the default value of "651". source= MA Use “lcsh” if name is established in LCSH. Use abbreviation or code for any other authority from which heading is taken, e.g., "tgn". If name is unestablished, delete SOURCE attribute and use RULES attribute. rules= MA If there is no authority record available for a particular place, feature, or jurisdiction name, use rules="scm" to indicate that the name has been formulated according to the LC Subject Cataloging Manual. Delete SOURCE attribute. <title> MA Y Access terms related to titles of published works to which a collection is related, such as monographs, serials, or paintings represented prominently in the collection. Do not end in a period unless the title ends in an initial. Set the RENDER attribute to "italic" to emphasize that the access term is a title of a published work. <title render=”italic” encodinganalog=”630” source=”lctah”>Arizona republic encodinganalog="630|730|740" Rec AAO templates will have the default value of "630". source= MA Use “lctah” when title is established in LC Title or LC Name/Title Authority Headings file. Use abbreviation or code for any other authority from which heading is taken. If title is unestablished, delete the SOURCE attribute and use the RULES attribute instead.

Page 39 of 67

Arizona Archive Online 2011 rules= MA Use “aacr2” if the title is not taken from an authorized source as described above, but is formulated according to AACR2. If title is established in the LC Name/Title Authority Headings, delete the RULES attribute and use the SOURCE attribute instead. Rec Y Access terms related to genre or form terms. Use one or more tags to list major genres and/or forms of material represented in the materials described. To enhance retrieval by form/genre, add entries for photographs, moving images, sound recordings, scrapbooks, diaries, artifacts, and oral histories.

Controlled subheadings may be added as needed, separated by a double hyphen -- (with no spaces between heading terms and hyphens). Controlled subheadings for geography names should be separated by a double hyphen – (with no spaces between heading terms and hyphens). Do not end the heading with a period.

Color slides encodinganalog="655" Rec AAO templates will have the default value of "655". source= MA If the source of the genre term is from the Art & Architecture Thesaurus (AAT), set the SOURCE attribute to source="aat".

If the source of the genre term is from the Library of Congress Thesaurus for Graphic Materials -- form/genre terms, set the SOURCE attribute to source="lctgm". Opt Y Access terms related to types of work or professions. Use one or more tags. Occuption terms may be placed in the element rather than the element.

See EAD tag library for information on use of this element. encodinganalog="656" Rec AAO templates will not contain an element. source= MA If the source of the genre term is from the Art & Architecture Thesaurus

Page 40 of 67

Arizona Archive Online 2011

(AAT), set the SOURCE attribute to source="aat".

If the source of the genre term is from the Library of Congress Subject Headings (LCSH), set the SOURCE attribute to source="lcsh". Opt Y Access terms related to activities and/or processes that generated the described materials. Function terms may be placed in the element rather than the element.

See EAD tag library for information on use of this element. encodinganalog="657" Rec AAO templates will not contain a element. source= MA If the source of the genre term is from the Art & Architecture Thesaurus (AAT), set the SOURCE attribute to source="aat".

If the source of the genre term is from the Library of Congress Subject Headings (LCSH), set the SOURCE attribute to source="lcsh".

Page 41 of 67

Arizona Archive Online 2011

Table 3:

Elements and Attributes Status Repeatable? Comments/Application Notes DACS Elements are surrounded by angle Req=Required brackets and rendered in boldface. MA=Mandatory, if applicable Rec=Recommended by best practices guidelines Opt=Optional MA N Use one element to encode the component hierarchy. The element is not required for finding aids. The tag is a wrapper element that groups information that reflects the hierarchical arrangement of the described materials. The Description of Sub- components section nests the components of a collection (i.e. recordgrp, subgrp, series, subseries, file, item, and other level). This should be a reflection of the intellectual arrangement of the described materials. type="combined|analyticover|in-depth" MA AAO templates will have the default value of "combined".

Use the default attribute value of "combined" when each major subdivision (ie. recordgrp, subgrp, series, or subseries) is described and followed by a container list of narrower levels (ie. file or item).

Use the attribute value of "analyticover" when only providing users with a description of the major subdivisions (ie. recordgrp, subgrp, series, or subseries) without describing narrower levels (ie. file or item) in a container list. This value may be used when describing summaries of subdivisions of an unprocessed collection.

Use the attribute value of "in-depth" when only providing users with a container list of narrower levels (ie. file or item). MA Y Encoders must use numbered (-) component elements; it provides a clearer view of the hierarchical structure.

Nested s should be used as needed to reflect the intellectual structure of the archival materials.

The full suite of subelements and attributes described are available at each component level (e.g., all elements described in the

Page 42 of 67

Arizona Archive Online 2011

table, may also be used as needed in each component described in ), although this table and the AAO template will only contain the most commonly used elements for subcomponent descriptions (ie. , , , , , , and elements. level="recordgrp|collection|subgrp|seri MA N Component levels should generally be subordinate to the level set in the Chap. 1 es|subseries|file|item" level attribute found in the element.

(if "otherlevel" is used) – use otherlevel The assignment of sub-component levels should be a reflection of the attribute in addition. collection’s arrangement. If the arrangement is hierarchical, then subsequent components will be smaller units of the preceding otherlevel="accession|sub-subseries" component – (ie. "series" then "subseries" then "file").

If the arrangement is flat, then the use of a single component is all that is required.

MA N Wrapper element for core information about the described collection/record group. should be used at the top-level or at any component level . MA Y Enter the component’s identification number and/or name that is used to 2.1.3 specify the group or section of archival materials being described. encodinganalog="099" Opt AAO templates will not contain this attribute. Add to element, if desirable. MA Y Use to record the type of physical container and specific or assigned container numbers where the described materials reside. This is almost exclusively done for the component levels with a "file" and/or "item" designate.

For finding aids that contain only higher-level component descriptions,

Page 43 of 67

Arizona Archive Online 2011

such as series or subseries-level data, container information may be provided at the appropriate broader level.

As needed, one or two elements may be used in a given entry. An entry that contains more than two elements will not display correctly with the AAO style sheet. type= MA Use this attribute to record the type(s) of physical containers where the described material is being housed. Use the most appropriate terms to reflect the container type, such as "box" "folder" "box-folder" "album" "scrapbook" "reel" “verticalfile". There is no controlled vocabulary, but repositories should be consistent locally with their use of container terms.

Multiple containers with the same title materials may also be grouped together:

11- 8

1.1 - 1.8 MA Y The title [transcribed or supplied] of the described materials. 2.3

If the collection title includes within it the name of a publication, such as the title of a magazine, periodical, or newspaper, enclose the publication name in a element, and set the <title> element’s RENDER attribute to "italic". encodinganalog="245$a" Opt AAO templates will not contain this attribute. Add to element, if desirable. <unitdate> MA Y US repository following APPM practice normally include <unitdate> as 2.4 part of <unittitle>, whereas British and Canadian practice, following ISAD(G)v2 use <unitdate> at the same level as <unittitle>. Given the trend for further international standardization, separate title and date is preferred but both practices are permitted. DACS separates <unittitle> from <unitdate> and should be considered the descriptive standard for encoding. Repeat <unitdate> if both inclusive and bulk dates are given. This element is considered an essential element for data exchange by Page 44 of 67 Arizona Archive Online 2011 ISAD(G)v2. Use for the creation year, month, or day of the described materials. type="inclusive|bulk" Opt Use "inclusive" for the entire date range; use "bulk" only as a repeat <unitdate> instance where predominant dates are presence and might give the user a better indication of the bulk or majority of the collection’s dates. AAO templates will not contain this attribute. Add to element, if desirable. normal= Opt Enter normalized date span of described materials. Use the iso8601 format (e.g. normal="1933/1980"). AAO templates will not contain this attribute. Add to element, if desirable. encodinganalog="245$f|245$g" Opt "245$f" for inclusive dates; “245$g” for bulk dates. AAO templates will not contain this attribute. Add to element, if desirable. <physdesc> Opt Y A wrapper element for physical details about the described materials. Use 2.5 subelements <extent>, <physfacet>, <dimensions>, and if desired, <genreform> to record the information. AAO templates will not contain the elements <physfacet> and <dimensions>. Add these elements as necessary. <extent> MA Y State extent of space occupied (in linear or cubic feet) and/or number of 2.5 containers and/or items. If desired, include additional details concerning types and formats of material, as in the first example below. Use separate <extent> tags inside a single <physdesc> to state the same information in different ways (e.g., one <extent> element for cubic feet and another <extent> element for number of containers, both nested inside the same <physdesc> element). For example: <physdesc> <extent>6 color prints</extent> </physdesc> encodinganalog="300$a" Opt AAO templates will not contain this attribute. Add to element, if Page 45 of 67 Arizona Archive Online 2011 desirable. <langmaterial> Rec N Wrapper element naming the language(s) found in the described materials. One or more language name(s) are enclosed in a nested <language> element. If the collection, such as a photograph collection, contains no associated text, state that fact in <langmaterial> using wording similar to the following: <langmaterial>No textual or other language materials are included in the collection.</langmaterial> AAO templates will not contain the element in the <dsc>. Add the element, if desirable. <language> Rec Y Nested within the <langmaterial> element, use to encode the language of 4.5 the materials being described: <langmaterial>Diary entries written in <language langcode=”fre”>French</language></langmaterial> AAO templates will not contain the element in the <dsc>. Add the element, if desirable. langcode="eng" Opt Use ISO 6392b to determine correct language code. AAO templates will not contain this attribute. Add to element, if desirable. Close </did> Page 46 of 67 Arizona Archive Online 2011 <scopecontent> Rec N Particularly at the higher component levels, such as the recordgrp or 3.1 series level, the scope and content note should provide a general description of the topical range and content, including notes on the document types and formats of the described materials at the higher component level. Biographical or administrative historical information may also be included in this element. Text should be enclosed in paragraph tags . >. If needed, the paragraph tags are repeatable within the <scopecontent> element. encodinganalog="520" Opt AAO templates will not contain this attribute. Add to element, if desirable. <accessrestrict> MA N Use to record Information about conditions that affect the availability of 4.1; 4.2 the described materials being described. May indicate the need for an appointment or restrictions imposed by the donor, legal statue, repository, or other agency. Do not confuse with conditions governing use. AAO templates will not contain the element in the <dsc>. Add the element, if necessary. encodinganalog="506" Opt AAO templates will not contain this attribute. Add to element, if desirable. <userestrict> Rec N Use to record information about conditions that affect use of the 4.4 described materials after access has been granted. Examples include limitations, regulations, or special procedures imposed by a repository, donor, legal statue, or other agency regarding reproduction, publication, or quotation of the described materials. May also indicate the absence of restrictions. AAO templates will not contain the element in the <dsc>. Add the element, if necessary. encodinganalog="540" Opt AAO templates will not contain this attribute. Add to element, if desirable. Page 47 of 67 Arizona Archive Online 2011 Table 4: Digital objects and external links Elements and Attributes Status Repeatable? Comments/Application Notes DACS Elements are surrounded by angle Req=Required brackets and rendered in boldface. MA=Mandatory, if applicable Rec=Recommended by best practices guidelines Opt=Optional Linking to external pointers or resources from a finding aid <extptr> Req Y If desired, link to external digital objects, such as your institutional logo using this element. The attribute values below dictate how the link is made. The pointers can link to an institution’s web page. Element will not be part of AAO template and should be added to guide by repository where appropriate. <extptr linktype="simple" href="http://library.nau.edu/speccoll" title="NAU logo" actuate="onload" show="embed"> linktype="simple" Set attribute to "simple". href= Provide the complete URL path in this attribute. title= Provide title of external digital object element. actuate="onload" Set attribute to "onload". show="embed" Set attribute to "embed". <extref> Req Y Use to link to external resources (i.e. other finding aids, web sites, online resources). Use the TITLE attribute to enter text to be used as a hyperlink to external resource. Element will not be part of AAO template and should be added to guide by repository where appropriate. <extref linktype="simple" href="http://www.harveyhouses.net/" title="Fred Harvey houses" role="text/html" actuate="onrequest" show="replace"> linktype="simple" Set attribute to "simple". href= Provide the complete URL path in this attribute. actuate="onrequest" Set attribute to "onrequest". role="text/html" Set attribute to "text/html". Page 48 of 67 Arizona Archive Online 2011 show="replace|new" show="replace" (i.e., the linked resource will be displayed in the same browser window). show="new" (i.e., the linked resource will be displayed in a new browser window). Linking to digital object(s) from a finding aid <daogrp> Req Y Wrapper element for linking to digital objects from finding aid. linktype="extended" Set attribute to "extended". <daodesc> Rec Use to supply information about the contents or source of the digital objects. Text should be enclosed in paragraph tags . >. If needed, the paragraph tags are repeatable within the <scopecontent> element. <resource> Req N Mark up creates textual hyperlink: <resource label="start">image of Barry M. Goldwater</resource> Empty element mark up creates a link from an icon/thumbnail/image: <resource label="start"/> or <resource label="start"></resource> Not repeatable within the same <daogrp> element. linktype="resource" Set attribute to "resource". label="start" Set attribute to "start". <daoloc> Req Y Element provides the location, type, title, and role of the digital object(s) in an extended link. If a repository wishes to embed an image in a finding aid document and then provide a link to a larger version of the same image – use two <daoloc> elements and two <arc> elements with their attributes, such as in the following example: <daoloc label=“thumbnail” href="http://archive.library.nau.edu/leesferry_thumb.jpg" title=”thumbnail image of Lees Ferry, 1967” role="image/jpeg"/> <daoloc label=“reference” href="http:// archive.library.nau.edu/leesferry_full.jpg " title=”reference image of Lees Ferry, 1967” role="image/jpeg"/> <arc from="start" to="thumbnail” show="embed" actuate="onload"/> <arc from="thumbnail" to="expanded” show="new" actuate="onrequest"/> Page 49 of 67 Arizona Archive Online 2011 href= Use to provide the URL of each digital object. <daoloc label="reference" href=" http://archive.library.nau.edu/u?/cpa,16123" title=”image of dog at Grand Canyon, ca. 1950” role="image/jpeg"/> label="thumbnail|reference|hi-res" Use to identify if digital object is a thumbnail, reference, or high resolution file. <daoloc label="reference" href=" http://archive.library.nau.edu/u?/cpa,16123" title=”image of dog at Grand Canyon, ca. 1950” role="image/jpeg"/> title= Use to provide the title of each digital object. <daoloc label="reference" href=" http://archive.library.nau.edu/u?/cpa,16123" title="image of dog at Grand Canyon, ca. 1950" role="image/jpeg"/> Use to identify the mimetype of the digital object being used in the role="image/gif|image/jpeg|image/tif" <daoloc> element. <daoloc label="reference" href=" http://archive.library.nau.edu/u?/cpa,16123" title="image of dog at Grand Canyon, ca. 1950" role="image/jpeg"/> <arc> Req Y Specifies the rules for traversal among the participating resources in an extended link. Arc uses the attributes to and from to define the traversal between named pairs of resources. from= Set the attribute FROM to the identical value as the <resource> attribute LABEL (i.e. <resource label="start">). If the <arc> will be referring to a thumbnail as the beginning of an extended link, assign the FROM attribute to thumbnail (i.e. <resource label="thumbnail"). Here are two examples of uses of the FROM attribute (also see discussion within <daoloc> element: <arc from="start" to="thumbnail” show="embed" actuate="onload"/> <arc from="thumbnail" to="expanded” show="new" actuate="onrequest"/> to= Use the attribute TO to define the destination of the extended link. Assigning the attribute TO to the value "expanded" will point to a different resource. Here are two examples of the use of the TO attribute: <arc from="start" to="thumbnail” show="embed" actuate="onload"/> <arc from="thumbnail" to="expanded” show="new" actuate="onrequest"/> show= Use the attribute SHOW to define when the digital object will be embedded in the guide upon loading or replace/open a new resource upon request. Page 50 of 67 Arizona Archive Online 2011 Embed digital object in guide: <arc from="start" to="thumbnail” show="embed" actuate="onload"/> Request (replace existing browser page) <arc from="thumbnail" to="expanded” show="replace" actuate="onrequest"/> Request (open new browser page) <arc from="thumbnail" to="expanded” show="new" actuate="onrequest"/> actuate= Use the attribute ACTUATE to define behavior of when to activate extended link. Activate when loading guide: <arc from="start" to="thumbnail” show="embed" actuate="onload"/> Activate when extended link is clicked: <arc from="thumbnail" to="expanded” show="new" actuate="onrequest"/> Page 51 of 67 Arizona Archive Online 2011 Appendix: Sample of finding aid based on AAO Best Practices <?xml version="1.0"?> <!DOCTYPE ead PUBLIC "+//ISBN 1-931666-00-8//DTD ead.dtd (Encoded Archival Description (EAD) Version 2002)//EN" "http://www.asu.edu/asuns/dtd/ead.dtd"> <ead> <eadheader countryencoding="iso3166-1" dateencoding="iso8601" langencoding="iso639-2b" relatedencoding="dc" repositoryencoding="iso15511" scriptencoding="iso15924"> <eadid countrycode="US" encodinganalog="identifier" mainagencycode="AzTuSM" publicid="-//Arizona State Museum//text(us::AzTuSM::Muriel Thayer Painter Collection, 1939-1975)//EN" >MS18.xml</eadid> <filedesc> <titlestmt> <titleproper encodinganalog="title">Muriel Thayer Painter Collection<date calendar="gregorian" encodinganalog="date" era="ce" certainty="approximate" normal="1939/1975">1939-1975</date></titleproper> <titleproper encodinganalog="title" altrender="nodisplay" type="filing">Painter (Muriel Thayer) Collection</titleproper> <author encodinganalog="creator">Processed by Jeanne Armstrong; machine-readable finding guide created by Jeanny Armstrong</author> </titlestmt> <publicationstmt> <publisher encodinganalog="publisher">Arizona State Museum</publisher> <address> <addressline>PO Box 210026</addressline> <addressline>Tucson, AZ 85721-0026</addressline> <addressline>Phone: 520-621-2970</addressline> <addressline>Fax: 520-621-2976</addressline> <addressline>URL: http://www.statemuseum.arizona.edu/archives/index.shtml</addressline> </address> <date calendar="gregorian" encodinganalog="date" era="ce" certainty="approximate" normal="2008">© 2008 Arizona Board of Regents. All Rights Reserved.</date> </publicationstmt> </filedesc> <profiledesc> <creation>Machine-readable finding guide encoded by Lisa Duncan <date encodinganalog="date" normal="2008-12" era="ce" certainty="approximate" calendar="gregorian">December 2008.</date> </creation> <langusage>Finding guide is in<language encodinganalog="language" langcode="eng" scriptcode="Latn"> Page 52 of 67 Arizona Archive Online 2011 English.</language> </langusage> </profiledesc> </eadheader> <archdesc level="collection" type="inventory" relatedencoding="marc21"> <did> <unitid encodinganalog="099">MS 18</unitid> <origination><persname encodinganalog="100" role="creator" rules="aacr2" source="lcnaf">Painter, Muriel Thayer</persname></origination> <unittitle encodinganalog="245$a">Muriel Thayer Painter Collection<unitdate calendar="gregorian" encodinganalog="245$f" era="ce" certainty="approximate" normal="1939/1975" type="inclusive">1939-1975.</unitdate> </unittitle> <physdesc><extent encodinganalog="300$a">15.5 Linear Feet</extent></physdesc> <abstract encodinganalog="520">Collection consists of the papers of Muriel Thayer Painter relating to Mrs. Painter's work in the Pascua Yaqui community. Included are field notes on Pascua and San Xavier and materials relating to her community activities with the Tucson Festival Society and Pascua Yaqui Association. Also included are materials from Refugio Savala, a Yaqui poet, including his manuscript <emph render="italic">Autobiography of a Yaqui Poet</emph></abstract> <langmaterial> <language encodinganalog="546" langcode="eng" scriptcode="Latn">English.</language> </langmaterial> <repository> <corpname encodinganalog="852$a">Arizona State Museum</corpname> <address> <addressline>PO Box 210026</addressline> <addressline>Tucson, AZ 85721-0026</addressline> <addressline>Phone: 520-621-2970</addressline> <addressline>Fax: 520-621-2976</addressline> <addressline>URL: http://www.statemuseum.arizona.edu/archives/index.shtml</addressline> </address> </repository> </did> <accessrestrict encodinganalog="506"> None. </accessrestrict> <userestrict encodinganalog="540"> Page 53 of 67 Arizona Archive Online 2011 The Arizona State Museum may not own copyright to all parts of this collection. It is the responsibility of the user to obtain permission to publish from the owner of the copyright (the institution, the creator of the record, the author or his/her transferees, heirs, legates, or literary executors). The user agrees to indemnify and hold harmless the Arizona Board of Regents for the University of Arizona, Arizona State Museum, its officers, employees, and agents from and against all claims made by any person asserting that he or she is an owner of copyright. </userestrict> <custodhist encodinganalog="561"> The Painter Collection came to the Arizona State Museum at Muriel Thayer Painter's death in 1975 except for several drafts of her Yaqui manuscript, which were at the University of Arizona Press or in the Spicer residence. These drafts were given to the Archives by Mrs. Spicer in 1987. </custodhist> <prefercite encodinganalog="524"> Muriel Thayer Painter Collection. Arizona State Museum Archives. Ms18. </prefercite> <bioghist encodinganalog="545"> <head>Biographical Note</head> Muriel Thayer was born in Minneapolis in 1892. She attended University of Minnesota and graduated from Wellesley in 1916 with a degree in social work. During 1938-39, Bronislaw Malinowski was a guest lecturer at the University of Arizona, Department of Anthropology. Muriel Thayer Painter joined Malinowski in observing the Yaqui Easter ceremony in Spring, 1939. From the beginning, Muriel Painter's commitment to study the Easter ceremony, and eventually the entire ceremonial cycle, grew. Each year from 1939 through 1954 she attended most of the Holy Week observances and the processions during Lent. Her extensive notes documenting these observations were supplemented by interviews with Yaquis over a period of years from 1948 to 1975. Mrs. Painter was appointed chairperson of the Tucson Chamber of Commerce "Yaqui Committee" in 1942. In 1950, the Tucson Chamber of Commerce published her pamphlet on the Yaqui Easter Ceremony at Pascua, which was later updated and reprinted by the University of Arizona Press. Since 1944, Muriel Painter was a research associate at the Arizona State Museum. She was program chairperson for the Tucson Festival Society which began organizing the annual San Xavier Fiesta in 1952. During the 1960s, she was chairperson of the Pascua Yaqui Association which sought to improve housing in Pascua Pueblo. The work Page 54 of 67 Arizona Archive Online 2011 of this Association eventually gained recognition of the Yaquis as a tribe and funds for establishing New Pascua Pueblo. When she died in 1975, Muriel Painter left her papers, including her unpublished manuscript, to the Arizona State Museum. Dr. Edward Spicer of the Department of Anthropology and Wilma Kaemlein, emeritus staff member of ASM, revised the manuscript and in 1986 it was published as <emph render="italic">With Good Heart</emph> by the University of Arizona Press. </bioghist> <arrangement encodinganalog="351"> This collection is organized into four subgroups and 15 series <list> <item>Subgroup 1: Field Notes, <unitdate>1939-1971</unitdate></item> <item>Series 1: Pascua Field Notes by Date, <unitdate>1939-71</unitdate></item> <item>Series 2: Pascua Field Notes by Subject and Miscellaneous Reading Notes </item> <item>Series 3: Papago (O'odham) Field Notes </item> <item>Series 4: Notes on Mexico and Miscellaneous </item> <item>Subgroup 2: Publications </item> <item>Series 1: Various Small Publications </item> <item>Series 2: Yaqui Manuscript Research </item> <item>Series 3: <emph render="italic">With Good Heart</emph>, First Draft </item> <item>Series 4: <emph render="italic">With Good Heart</emph>, Second Draft </item> <item>Series 5: <emph render="italic">With Good Heart</emph>, Final Draft </item> <item>Subgroup 3: Refugio Savala Papers </item> <item>Series 1: Original Savala Manuscripts </item> <item>Series 2: Savala Manusciprt Edited by Kay Sands </item> <item>Subgroup 4: Community and Professional Activities </item> <item>Series 1: Correspondence </item> <item>Series 2: Tucson Festival Society </item> <item>Series 3: Pascua Yaqui Development Project </item> <item>Series 4: Other Activities </item> </list> </arrangement> <scopecontent encodinganalog="520"> This collection relates to the years from 1939 to 1975 when Muriel Painter was active in the Pascua Yaqui community. Her papers include field notes on Pascua and San Xavier and materials relating to her community activities with the Tucson Festival Society and Pascua Yaqui Association. Page 55 of 67 Arizona Archive Online 2011 Subgroup 1 is field notes, 1939-71; subgroup 2 is publication; subgroup 3 is the Refugio Savala papers; and subgroup 4 is community and professional activities. Refugio Savala's manuscripts for <emph render="italic">Autobiography of a Yaqui Poet</emph> and other Savala papers are included in the Painter Collection because he was an important Yaqui contributor to her work. Mrs. Painter encouraged Refugio to start his autobiographical journal describing Yaqui customs as they were in his lifetime. </scopecontent> <controlaccess> <controlaccess> <persname encodinganalog="600" source="lcnaf">Painter, Muriel Thayer</persname> <persname encodinganalog="600" source="lcnaf">Savala, Refugio</persname> </controlaccess> <controlaccess> <subject encodinganalog="650" source="lcsh">Yaqui Indians--Arizona--Rites and ceremonies</subject> <subject encodinganalog="650" source="lcsh">Yaqui Indians--Religion</subject> <subject encodinganalog="650" source="lcsh">Yaqui Indians</subject> <subject encodinganalog="650" source="lcsh">Indians of <a href="/tags/North_America/" rel="tag">North America</a>--Arizona--Rites and ceremonies</subject> <subject encodinganalog="650" source="lcsh">Tohono O'odham Indians</subject> <subject encodinganalog="650" source="lcsh">Tohono O'odham Indians--Arizona--Rites and ceremonies</subject> </controlaccess> <controlaccess> <geogname encodinganalog="651" source="lcsh">Pascua Village (Ariz.)--Social life and customs</geogname> <geogname encodinganalog="651" source="lcsh">Pascua Yaqui Tribe of Arizona</geogname> </controlaccess> </controlaccess> <dsc type="combined"> <c01 level="series"> <did> Page 56 of 67 Arizona Archive Online 2011 <unitid>Subgroup 1</unitid> <unittitle>Field Notes, <unitdate>1939-1971</unitdate></unittitle> </did> <scopecontent> Subgroup 1: Series 1 consists of Pascua field notes arranged by date; Series 2 is Pascua field notes by subject and miscellaneous reading notes. These notes are on half sheets and are stored in card boxes. Series 3 consists of Papago (O'odham) field notes; Series 3-5 are three drafts of the manuscript of <emph render="italic">With Good Heart</emph>. </scopecontent> <c02 level="subseries"> <did> <unitid>Series 1</unitid> <unittitle>Pascua Field Notes by Date, <unitdate>1939-71</unitdate></unittitle> </did> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">1</container> <unittitle>Pascua-Malinowski, <unitdate>1939</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">2</container> <unittitle>Pascua, <unitdate>1939</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">3</container> <unittitle>Pascua, <unitdate>1945-46</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> Page 57 of 67 Arizona Archive Online 2011 <container type="box">1</container> <container type="folder">4</container> <unittitle>Pascua, <unitdate>1947</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">5</container> <unittitle>Pascua, January-February, <unitdate>1948</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">6</container> <unittitle>Pascua, February, <unitdate>1948</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">7</container> <unittitle>Pascua, March,<unitdate>1948</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">8-9</container> <unittitle>Pascua, April, <unitdate>1948</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">10</container> <unittitle>Pascua, May, <unitdate>1948</unitdate></unittitle> </did> Page 58 of 67 Arizona Archive Online 2011 </c03> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">11</container> <unittitle>Pascua, August<unitdate>1948</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">12</container> <unittitle>Pascua, October,<unitdate>1948</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">13</container> <unittitle>Pascua, November-December, <unitdate>1948</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">14</container> <unittitle>Pascua, January-February, <unitdate>1949</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">1</container> <container type="folder">15</container> <unittitle>Pascua, March, <unitdate>1949</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> Page 59 of 67 Arizona Archive Online 2011 <container type="box">1</container> <container type="folder">16-17</container> <unittitle>Pascua, April, <unitdate>1949</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">18</container> <unittitle>Pascua, May, <unitdate>1949</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">19</container> <unittitle>Pascua, June, <unitdate>1949</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">20</container> <unittitle>Pascua, July-September, <unitdate>1949</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">21</container> <unittitle>Pascua, October-December, <unitdate>1949</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">22</container> <unittitle>Pascua, January-March, <unitdate>1950</unitdate></unittitle> </did> Page 60 of 67 Arizona Archive Online 2011 </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">23-24</container> <unittitle>Pascua, April, <unitdate>1950</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">25</container> <unittitle>Pascua, May, <unitdate>1950</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">26</container> <unittitle>Pascua, June-August, <unitdate>1950</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">27</container> <unittitle>Pascua, October-November, <unitdate>1950</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">28</container> <unittitle>Pascua, January-February, <unitdate>1951</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> Page 61 of 67 Arizona Archive Online 2011 <container type="box">2</container> <container type="folder">29</container> <unittitle>Pascua, March, <unitdate>1951</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">30</container> <unittitle>Pascua, March-May, <unitdate>1951</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">31</container> <unittitle>Pascua, June-August, <unitdate>1951</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">32</container> <unittitle>Pascua, September-December, <unitdate>1951</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">33</container> <unittitle>Pascua, January-April, <unitdate>1952</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">2</container> <container type="folder">34</container> <unittitle>Pascua, May-December, <unitdate>1952</unitdate></unittitle> </did> Page 62 of 67 Arizona Archive Online 2011 </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">35</container> <unittitle>Pascua, January-November, <unitdate>1953</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">36</container> <unittitle>Pascua, February-March, <unitdate>1954</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">37</container> <unittitle>Pascua, April-November, <unitdate>1955</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">38</container> <unittitle>Pascua, <unitdate>1956</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">39</container> <unittitle>Pascua, February-October, <unitdate>1957</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> Page 63 of 67 Arizona Archive Online 2011 <container type="box">3</container> <container type="folder">40</container> <unittitle>Pascua, November-December, <unitdate>1957</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">41</container> <unittitle>Pascua, <unitdate>1958</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">42</container> <unittitle>Pascua, <unitdate>1959</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">43</container> <unittitle>Pascua, <unitdate>1961-62</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">44</container> <unittitle>Pascua, <unitdate>1963</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">45</container> <unittitle>Pascua, <unitdate>1964</unitdate></unittitle> </did> Page 64 of 67 Arizona Archive Online 2011 </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">46</container> <unittitle>Pascua, <unitdate>1965</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">47</container> <unittitle>Pascua, <unitdate>1966-67</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">48</container> <unittitle>Pascua, <unitdate>1968-69</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">49</container> <unittitle>Pascua, <unitdate>1970-71</unitdate></unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">50</container> <unittitle>Barrio Libre</unittitle> </did> </c03> <c03 level="file"> <did> <container type="box">3</container> <container type="folder">51</container> Page 65 of 67 Arizona Archive Online 2011 <unittitle>Notes on Refugio Savala</unittitle> </did> </c03> </c02> ...... [rest of container list] </c01> </dsc> </archdesc> </ead> Page 66 of 67 Arizona Archive Online 2011 Bibliography The best practices committee found the Encoded Archival Description (EAD) Version 2002 Official site maintained by the Library of Congress extremely useful when determining the application of specific EAD elements. Library of Congress. Encoded Archival Description Version 2002 Official Site The revised Arizona Archives Online best practices (version 3.1) were guided and vastly improved by consulting the following consortia EAD best practices documentation: Northwest Digital Archives. Best Practice Guidelines for Encoded Archival Description (version 3.3) Online Archive of California. Best Practice Guidelines for EAD (version 2.0) Utah Manuscript Association. Encoded Archival Description Best Practices Guidelines (version 1.2) When entering archival descriptive information above the <dsc> section of a finding aid, Archive Archives Online contributors should refer to the rules and conventions illustrated in Describing Archives: a Content Standard. Page 67 of 67 </div> </article> </div> </div> </div> <script type="text/javascript" async crossorigin="anonymous" src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-8519364510543070"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js" crossorigin="anonymous" referrerpolicy="no-referrer"></script> <script> var docId = '215c0ba3c8a5cdd82f9bddf08c676831'; var endPage = 1; var totalPage = 68; var pfLoading = false; window.addEventListener('scroll', function () { if (pfLoading) return; var $now = $('.article-imgview .pf').eq(endPage - 1); if (document.documentElement.scrollTop + $(window).height() > $now.offset().top) { pfLoading = true; endPage++; if (endPage > totalPage) return; var imgEle = new Image(); var imgsrc = "//data.docslib.org/img/215c0ba3c8a5cdd82f9bddf08c676831-" + endPage + (endPage > 3 ? ".jpg" : ".webp"); imgEle.src = imgsrc; var $imgLoad = $('<div class="pf" id="pf' + endPage + '"><img src="/loading.gif"></div>'); $('.article-imgview').append($imgLoad); imgEle.addEventListener('load', function () { $imgLoad.find('img').attr('src', imgsrc); pfLoading = false }); if (endPage < 7) { adcall('pf' + endPage); } } }, { passive: true }); </script> <script> var sc_project = 11552861; var sc_invisible = 1; var sc_security = "b956b151"; </script> <script src="https://www.statcounter.com/counter/counter.js" async></script> </html>