File naming and identification

EADID

Outsourced XML files will return with an empty <eadid> element nested within the <eadheader>. EADID requires a formatted string for its content prior to sending the file to the TARO production server.* The content format remains the same whether you are tagging to the EAD 1.0 or EAD 2002 specification.

FOR: Rice, Texas A&M, Texas Tech, University of Houston and UT Austin repositories . . .

The content for <eadid> needs to follow this format:

urn:taro:[institution].[unit].[xxxxx]

• where. . .
• institution = uh, utexas, rice, tamu, ttu
• unit
• for texas = hrc, cah, law, aaa, blac
• for tamu = cush
• for ttu = sw, swcpc, rb, ua
• for rice = wrc
• for uh = ua, sc, warc, me
• xxxxx = a unique FIVE DIGIT number, starting with 00001, assigned to each finding aid

FOR: Texas State Library, Austin History Center, Houston Public, Texas State University, UT Arlington, UT El Paso, UT Panam, UT Medical Branch, UT San Antonio, M. D. Anderson Cancer Center, Southern Methodist University, Dallas Pubic Library, Houston Academy of Medicine, Old Jail Art, Texas Womens University repositories . . .

urn:taro:[institution].[xxxxx]

• where. . .
• institution = tslac, aushc, houpub, tsusm, utarl, utep, utpanam, utmb, utsa, utmda, smu, dalpub, hamtmc, ojac, twu
• xxxxx = a unique FIVE DIGIT number, starting with 00001, assigned to each finding aid

File names

The name you give each XML file must coincide with the last five digits of the URN in the <eadid> of that file. In this example, if the urn is:

urn:taro:utexas.hrc.00012

. . . then you would name the XML file -- 00012.xml

*EAD 2002 also requires the presence of certain attributes for <eadid>.