<function> Function

<function> is used to encode terms for spheres of activities and processes that generated the described materials. The terms may provide useful access points, such as “entertaining” or “collecting taxes.” This should not be confused with the <occupation> element, which designates a type of work of business.

The element may be used to tag any function during a paragraph, with the NORMAL attribute supplying the proper form of the term. Functions which contributed greatly to the formation of the materials should be listed within <controlaccess> even if they are indicated elsewhere. <function> may be used within <controlaccess>, <entry>, <event>, <extref>, <extrefloc>, <indexentry>, <item>, <label>, <namegrp>, <p>, <physdesc>, <physfacet>, <ref> (reference), <refloc> (reference location), and <unittitle>.

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.
  • AUTHFILENUMBER – not required. A number that identifies the authority file record for an access term drawn from that authority file (the source for this number/the access term should be in SOURCE).
  • ENCODINGANALOG – not required. May contain information to map this tag to MARC field 657.
  • NORMAL – not required. Can be used to provide the authority form if the word is being used informally within narrative text, etc.
  • RULES – not required. May be used to specify the descriptive rules followed when forming the term.
  • SOURCE – not required. The source of the controlled vocabulary, e.g. “lcsh” for Library of Congress Subject Headings.

Subelements

<function> may contain PCDATA, <emph>, <extptr>, <lb />, and <ptr>.

Examples

The following example comes from the LoC tag libary:

<controlaccess>
	<head>Index Terms</head>
	<p>These records are indexed under the following headings in the catalog of
	the Minnesota Historical Society.  Researchers wishing to find related materials
	should search the catalog under these index terms.</p>
	<controlaccess>
		<head>Government Functions:</head>
		<function encodinganalog="657" source="aat">Law enforcing.</function>
		<function encodinganalog="657" source="aat">Convicting.</function>
	</controlaccess>
</controlaccess>

EAD tag library entry for <function>.
https://eadiva.com/2/function/
eadiva.com
crawl=CC-MAIN-2020-16
25076
application/http; msgtype=response
sha1:JV6CLLPVIEKS4NDACB434FCSPJVKYNX6
<urn:uuid:b7933c90-faa4-49ea-b179-73b77fb07bed>
2020-03-28T14:30:55Z
192.241.132.143
application/xhtml+xml
sha1:SQZI7UMWBL5T2TGBLR5PRSCWENCVX5CW
<urn:uuid:1953ed46-6776-46a6-8176-c07ca3dff3fc>
https://eadiva.com/2/function/
response
<urn:uuid:f64a8f18-46f8-49d6-8ca2-de14f632a669>
isPartOf: CC-MAIN-2020-16
publisher: Common Crawl
description: Wide crawl of the web for March/April 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-20.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/