<c> Component

<c> is a wrapper element found within <dsc>, and which may be nested within another <c> element. Each <c> element identified an intellectually logical section of described materials, which may not coincide with the physical sections. Not every <c> corresponds to directly to a folder, etc. It may simply be a hierarchical stage.

<c> may have levels assigned through the LEVEL attribute, as seen in the attributes section below. Nesting <c> may also be done as <c01> to <c12>, to help a manual encoder track levels more easily and preserve the code’s structure.

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.”
  • ID – not required. Creates an ID for element. Can be used for linking.
  • ENCODINGANALOG – not required. May contain information to map this tag to a particular element in another schema.
  • LEVEL – not required. The values of this attribute may be class, collection, file, fonds, item, otherlevel, recordgrp, series, subfonds, subgrp, and subseries. For any other value of LEVEL (such as from a locally-assigned vocabulary) choose “otherlevel” as the value, and specify name in OTHERLEVEL attribute. Assigning an attribute to the highest-level <c> is highly-recommended.
  • OTHERLEVEL – not required. If the designated value options for LEVEL do not fit the repository needs, “othervalue” should be used as the value for LEVEL and the alternate term should be specified here.
  • TPATTERN – not required. Reference to one of a set of standard patterns that define the specifications of particular HTML output tables.

Subelements

<c> may contain further <c> elements, as well as <accessrestrict>, <accruals>, <acqinfo>, <altformavail>, <appraisal>, <arrangement>, <bibliography>, <bioghist>, <controlaccess>, <custodhist>, <dao>, <daogrp>, <descgrp>, <did>, <dsc>, <fileplan>, <head>, <index>, <note>, <odd>, <originalsloc>, <otherfindaid>, <phystech>, <prefercite>, <processinfo>, <relatedmaterial>, <scopecontent>, <separatedmaterial>, <thead>, and <userestrict>. Note, since PCDATA is not used within this element, it serves as a wrapper of all the information about the components.

DACS

Use DACS Section 1. Level of description for the LEVEL attribute. (DACS 2013, pp.7-11)

Examples

An example of how <c> may be used:

<c level="series">
	<did>
	<unitid>SJB1</unitid>
	<unittitle>Correspondence</unittitle>
	</did>
	<arrangement><p>This series is arranged alphabetically by correspondent. Letters written <emph>by</emph> Sarah J. Bell are arranged alphabetically by recipient's last name.</p></arrangement>
	<c level="subseries">
	<did>
	<unitid>SJB2</unitid>
	<unittitle>Incoming Correspondence</unittitle>
	</did>
		<c level="file">
		<did>
		<unitid>SJBFolder1</unitid>
		<unittitle>A-H</unittitle>
		</did>
		</c>
		<c level="file">
		<did>
		<unitid>SJBFolder2</unitid>
		<unittitle>I-Z</unittitle>
		</did>
		</c>
	</c>
	<c level="subseries">
	<did>
	<unitid>SJB3</unitid>
	<unittitle>Outgoing Correspondence</unittitle>
	</did>
		<c level="file">
		<did>
		<unitid>SJBFolder3</unitid>
		<unittitle>A-C</unittitle>
		</did>
		</c>
		<c level="file">
		<did>
		<unitid>SJBFolder4</unitid>
		<unittitle>D-H</unittitle>
		</did>
		</c>
		<c level="file">
		<did>
		<unitid>SJBFolder5</unitid>
		<unittitle>I-Q</unittitle>
		</did>
		</c>
		<c level="file">
		<did>
		<unitid>SJBFolder6</unitid>
		<unittitle>R-Z</unittitle>
		</did>
		</c>
	</c>
</c>

EAD tag library entry for <c>.