EAC Crosswalk

ISAAR(CPF) 2nd ed. (final 27-30 Oct. 2003) to EAC beta version

Document history

Ver.

Status

Date

Author(s)

Distribution/note

0.1

DRAFT

2002-07-18

P-G Ottosson


0.2

DRAFT

2002-09-04

P-G Ottosson

EAC Working Group:
http://jefferson.village.virginia.edu/eac/

0.3

DRAFT

2002-12-13

P-G Ottosson

Update to ISAAR(CPF)2, draft ver. 19-22 Nov. 2002

0.4

DRAFT

2003-09-26

P-G Ottosson

Update to EAC beta

0.5

FINAL DRAFT

2004-02-13

P-G Ottosson

Update to ISAAR(CPF)2, final 27-30 Oct. 2003

Status of this document:
This document is made available for discussion only, and it may be updated or replaced at any time.




ISAAR(CPF)2

The final version of ISAAR(CPF)2 will be available on the home page of ICA/CDS— http://www.hmc.gov.uk/icacds/eng/standards.htm | http://www.ica.org/biblio.php?pbodycode=CDS&ppubtype=pub&plangue=eng..

Conventions

@ signifies attribute, e.g. eacheader@type = the type attribute of eacheader <eacheader type="[XYZ]">
/ signifies a parent/child relation between elements, e.g. nameadds/date refers to the date element only within the element nameadds.

Uppercase AND & OR are used in the boolean sense.

ISAAR
section

ISAAR Elementname

EAC Tag/attribute name

EAC expanded name

Comments

5.

ELEMENTS OF DESCRIPTION

 

 

 

5.1

IDENTITY AREA

identity

 

 

5.1.1 

Type of entity

eac@type

 

In EAC the type is also distinguished by the names of the heading elements.

5.1.2 

Authorized form of name

corphead OR
pershead OR
famhead

Corporate name heading OR
Personal name heading OR
Family name heading

These EAC elements are used for all forms of names; the value of the attribute 'authorized' identifies the authorizing agency.

5.1.3 

Parallel forms of name

corpgrp/corphead OR
persgrp/pershead OR
famgrp/famhead

 

See comments to 5.1.2

5.1.4

Standardized forms of name according to other rules

corphead OR
pershead OR
famhead

 

See comments to 5.1.2

5.1.5

Other forms of name

corphead OR
pershead OR
famhead

 

See comments to 5.1.2

5.1.6

Identifiers for corporate bodies

legalid

Legal identity code/number

 

5.2

DESCRIPTION AREA

desc

Description

ISAAR 2 DRAFT allows for two approaches to the description: free text or structured, but in both cases dates of existence is supposed to be a separate and mandatory element.
In EAC <desc> may contain a free biographical, corporate or family history under <bioghist>; and/or
structured text contained in content specific elements under <corpdesc>, <persdesc> or <famhist>

5.2.1

Dates of existence

existdesc/existdate

Date

 

5.2.2

History

bioghist

Biography or history

 

5.2.3

Places

location/place

Location

 

5.2.4

Legal status

legalstatus

Legal status

In ISAAR limited to corporate bodies

5.2.5

Functions, occupations and activities

funactrels
funactrel

Function or activity relation(s)

<funactrels> and <funactrel>consist of elements for the function/activity term <funact>with attributes for linkage to controlled vocabulary, covering dates, and notes

5.2.6

Mandates/Sources of authority

causa

Causa

 

5.2.7

Internal structures/Genealogy

assetstruct

Assets or structure

 

5.2.8

General context

env

Environment

 

5.3

RELATIONSHIPS AREA

eacrels
eacrel

EAC relation(s)

 

5.3.1

Name/Identifier of the related corporate bodies, persons or families

eacrel@syskey
AND
corpname OR
persname OR
famname

 

 

5.3.2

Category of relationship

eacrel@reltype

Type of relation

In ISAAR there are three defined catgories--hierarchical, temporal and family and one undefined associative. In EAC these categories are more specified: subordinate, earlier, later, associative, parent, child, and identity. There are also attributes that allows for local and controlled vocabularies for classifications of relationships

5.3.3

Description of relationship

eacrel/descnote

 EAC relation/ descriptive note

 

5.3.4

Dates of the relationship

eacrel/date

EAC relation/date

 

5.4

CONTROL AREA

eacheader

EAC Header

 

5.4.1

Authority record identifier

eacid

EAC Identifier

 

5.4.2

Institution identifiers

eacid@ownercode

 


5.4.3

Rules and/or conventions

ruledecl

Rule declaration

One or more rules can be declared. With the attribute rule, available in relevant elements, it can be specified in which areas a particular rule has been applied

5.4.4

Status

eacheader@status

Status

 

5.4.5

Level of detail

eacheader@detaillevel

Level of detail

 

5.4.6

Dates of creation and revision

mainhist

Maintenance history

 

5.4.7

Language(s) and script(s) of record

languagedecl

Language declaration

 

5.4.8

Sources

sourcedecl

Sourcedeclaration

 

5.4.9

Maintenance notes

maindesc

Maintenance Description

 

6

RELATING CORPORATE BODIES, PERSONS AND FAMILIES TO ARCHIVAL MATERIALS AND OTHER RESOURCES

resourcerels/resourcerel

Resource relation(s)

6.1

Identifiers and titles of related resources

archunit/unitid archunit/unittitel
bibunit/title
musunit/title

 

 

6.2

Types of related resources


The EAC element <resourcerel>has subelements for archival <archunit>, bibliographic <bibunit>, and museum <musunit> units or objects.

6.3

Nature of relationship

resourcerel@reltyp


@reltype is used for a general classification that can be more specified in @type or @typekey

6.4

Dates of related resources and/or relationsships

resourcerel/date OR
archunit/unitdate OR
bibunit/imprint/date OR
musunit/imprint/date