Hello all,

I'm looking for an appropriate way to encode a bib system number in EAD and
found this thread.  I think the multiple <unitid> approach that Michele
describes is the best approach--one for the collection number and one for
the bib system number--but there is one catch.  As far as I can tell,
Archivists' Toolkit only supports the use of one <unitid> element at the
collection level.  If you try to import an EAD file with more than one
collection level <unitid> element, AT just imports the one without any

I suppose I could insert the <unitid encodinganalog="001" type="bibsysno">
after exporting EAD from AT, but I'd prefer to find a solution where I
could manage both the collection number and bib system number in AT and
export them both in EAD without having to post-process the EAD file.

And so I consult the collective wisdom of the EAD list... Any AT users have




Noah Huffman

Archivist for Metadata and Encoding

David M. Rubenstein Rare Book & Manuscript Library

Duke University

[log in to unmask]


Visit our blog "The Devil's Tale":

Be our fan on Facebook:

On Fri, Mar 16, 2012 at 11:59 AM, Michele R Combs <[log in to unmask]> wrote:

>  We map the 001 field (the BIBID) to the collection-level <unitid>
> (ead/archdesc/did/unitid) .    The definition of unitid seems to support
> this as the correct choice: “Any alpha-numeric text string that serves as a
> unique reference point or control number for the described material, such
> as a lot number, an accession number, a classification number*, or an
> entry number in a bibliography or catalog*...the TYPE attribute may be
> used to indicate the system from which the <unitid> was derived, e.g.,
> accessioning system, record group classification scheme, records retention
> scheduling system, etc.”****
> ** **
> For example:****
> ** **
> <unitid encodinganalog="001" type=”opac” label="Identification: "
> countrycode="US" repositorycode="NSyU">148784</unitid>****
> ** **
> <unitid> is of course usable at any c0# level, so you could have different
> ones for fonds, series, etc. at the appropriate level of the description.*
> ***
> ** **
> Michele****
> ** **
> *From:* Encoded Archival Description List [mailto:[log in to unmask]] *On
> Behalf Of *Vicky Phillips
> *Sent:* Thursday, March 15, 2012 6:33 PM
> *To:* [log in to unmask]
> *Subject:* System Control Number in EAD****
> ** **
> Hello, We are currently starting on the digitisation of archives and
> manuscripts and for the first time will be working with EAD within METS.
> The standard transformation from MARC to EAD does not incorporate the MARC
> field 001, which contains the System Control Number/Unique identifier
> within the catalogue, which we depend on heavily in the digitisation
> workflow. I was wondering if those of you who are already using EAD could
> let me know if you include this in your EAD and if so which element and
> attributes do you use? For example the manuscript collection<>I am starting with has a System Control Number at Fonds, Series and File
> level. We were thinking on the lines of placing the System Control Number
> (vtls004593617) for the Fonds in the element within element using
> identifier and encodinganalog attributes as follows: The above could also
> contain the handle to the parent object e.g. Then the element within
> element for FONDS level record will contain the NRA Code (MARC field 099)
> However, I notice that the LC have done this differently. Placing handle in
> identifier in eadid and note regarding Catalogue Record (System Control
> Number) in a note element within filedesc
> ****
> Catalog Record: ****
> For all sub levels Then for all sub levels (Series, File) which have a
> bibliographic record of placing the System Control Number in the identifier
> attribute within the element along with encodinganalog attribute which will
> contain the MARC field number and possibly label attribute e.g. Being
> relatively new to EAD I was wondering if what we have suggested is ok or
> whether those of you who have implemented have any other suggestions and
> better still examples of how you have incorporated LCNs into your EAD. Any
> guidance / feedback would be greatly appreciated. Thanks, Vicky ** **