EAD Tag Library for Version 1.0

EAD Elements: <famname> Family Name

Description:

The proper noun designation for a group of persons closely related by blood or persons who form a household. Includes single families and family groups, e.g., Patience Parker Family and Parker Family.

All names in a finding aid do not have to be tagged. One option is to tag those names for which access other than basic, undifferentiated keyword retrieval is desired. Use of authorized forms is recommended to facilitate access to the names within and across finding aid systems. The <famname> element may be used in many text elements. To indicate a family name with major representation in the materials being described, nest <famname> within the <archdesc> <controlaccess> element.

The ROLE attribute can be used to specify the relationship(s) of the name to the materials being described, for example, "compiler," "creator," "collector," or "subject." The NORMAL attribute can be used to provide a consistent form of a name that has been abbreviated in some parts of a finding aid. The AUTHFILENUMBER attribute can be used to identify a link to an authority file record that has more information about the name or cross references for alternative forms of the name and related names. Use the SOURCE attribute to specify the vocabulary from which the name has been taken.

See also the related elements <controlaccess>, <corpname>, <persname>, and <name>.

The <famname> element is comparable to MARC fields 100, 600, 700.

May contain:

#PCDATA, emph, extptr, lb, ptr

May occur within:

bibref, controlaccess, entry, event, extref, extrefloc, indexentry, item, label, namegrp, origination, p, physdesc, physfacet, ref, refloc, unittitle

Attributes:

ALTRENDER	#IMPLIED, CDATA
AUDIENCE	#IMPLIED, external, internal
AUTHFILENUMBER	#IMPLIED, CDATA
ENCODINGANALOG	#IMPLIED, CDATA
ID	#IMPLIED, ID
NORMAL	#IMPLIED, CDATA
OTHERSOURCE	#IMPLIED, CDATA
ROLE	#IMPLIED, CDATA
SOURCE	#IMPLIED, aat, aacr2, cdwa, dot, gmgpc, lcnaf, lcsh, lctgm, local, mesh, mim, ncarules, nmc, rad, rbgenr, tgn, ulan, othersource

Examples:

<c01 level="series">
<did>[...]</did>
[other possible elements and text... ]
<c02>
<did><physloc audience="internal">B:14:D</physloc>
<container type="box">1</container>
<container type="folder">1</container>
<unittitle>
<famname normal="Smith">Smyth family </famname>genealogical information,
<unitdate type="inclusive">1889-1925</unitdate></unittitle>
<physdesc><extent>6 items</extent></physdesc>
[other possible elements and text... ]
</did>
</c02>
[other possible elements and text... ]
</c01>

<archdesc langmaterial="eng" level="collection">
<did>[...]</did>
<admininfo>[...]</admininfo>
[other possible elements and text... ]
<controlaccess><head>Controlled Vocabulary Indexing Terms:</head>
<controlaccess><head>Subjects:</head>
<famname encodinganalog="600" source="lcnaf">Ferry family.</famname>
<geogname encodinganalog="651" source="lcsh">Ferry Field (University of Michigan)</geogname>
[other possible elements and text... ]
</controlaccess>
[other possible elements and text... ]
</controlaccess>
[other possible elements and text... ]
</archdesc>

Table of Contents

Home
Page Acknowledgments Introduction EAD Design
Principles Overview of
EAD Structure Tag Library
Conventions EAD Attributes EAD Elements
by Tag Name Index of
EAD Element Names

Go to:

Table of Contents
Home Page	Acknowledgments	Introduction	EAD Design Principles	Overview of EAD Structure	Tag Library Conventions	EAD Attributes	EAD Elements by Tag Name	Index of EAD Element Names