<processinfo> Processing Info

<processinfo> encodes information about accessioning, arranging, describing, preserving, storing, or otherwise preparing the described materials for research use. This should be used for basic information. More-detailed information can be encoded within specific elements for each facet. The element is comparable to ISAD(G) data element 3.7.1 and MARC field 583. <date>s within the element (within child elements) are comparable to ISAD(G) data element 3.7.3.

<processinfo> is one of the elements which may be used within <archdesc>, <c>, <c01> … <c12>, and itself.

Attributes

  • @altrender – not required. Use if the content of the element should be displayed or printed differently than the rendering established in a style sheet for other occurrences of the element.
  • @audience – not required. Use to set whether the element’s contents will be visible to external users or to internal ones. Possible values are: “internal” and “external.”
  • @encodinganalog – not required. May contain information to map this tag to a particular element in another schema.
  • @id – not required. Creates an ID for element. Can be used for linking.
  • @lang – not required. Three-letter code that indicates the language in which the element’s contents were written. It should come from ISO 639-2b.
  • @localtype – not required. This attribute may be used within a number of elements. Its use and values are not defined by the schema and may be defined locally.
  • @script – not required. Four-letter code that indicates the script in which the element’s contents were written. It should come from ISO 15924.

Child Elements

<processinfo> may contain an optional <head> element. It must contain one or more of the following: <blockquote>, <chronlist>, <list>, <p>, <table>, and further <processinfo> elements.

DACS

See DACS Section 7, Notes especially 7.1.8 for processing notes and DACS Section 8, Description control, and specifically section 8.1.5 for information about archivist and date. Added value. (DACS 2013, pp.78-81, 83-84)

Examples

<processinfo>
  <head>Processing Information</head>
  <p>The original collection was accessioned and processed by University Archivist Wilhelmena Ransom between 1989 and 1990. Accruals are processed annually by student workers with guidance by the University Archivist on occasions when material warranted the creation of a new series.</p>
  <p>In 2006, upon <persname identifier="http://id.loc.gov/authorities/names/no2019174587" normal="Russel, Martha A. (Martha Anita), 1941-2010"><part>Dr. Martha Russel's</part></persname>, transition to emerita status, Digital Archivist Monica Brown accessioned and processed the two hard drives on which Dr. Russel had stored digital meeting notes, colloquia and symposium reccordings, and other miscellaneous departmental materials. These were used to fill gaps in existing series.</p>
  <p>From 2016 to 2020, Electronic Records Archivist María Ramirez has annually accessioned and processed the meeting notes, policies, and annual reports via a Box folder shared with the department's administrative assistant. Copies of these born-digital materials are stored on the University Archives' fileserver and linked in the finding aid.</p>
</processinfo>

Changes from EAD 2002

<processinfo> gained @lang and @script elements. @type changed to @localtype. It lost <address> and <note>.

EAD3 Tag Library Entry

View the official tag library entry for <processinfo>