[Archivesspace_Users_Group] Top container ranges

Mayo, Dave dave_mayo at harvard.edu
Thu Jun 18 09:04:14 EDT 2020


The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they’re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn’t mind going more into why that’s not a viable solution for you, it might help us provide better advice?

Either way, at 7000 finding aids, the solution would basically need to be automated – if your box ranges are very regular (i.e. only single number or range, no “3,4,7-10” or similar), it wouldn’t be too difficult – split the range on ‘-‘, generate list of numbers, replace container with multiple containers.

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into ArchivesSpace and are wondering how other institutions have handled top container ranges.



For example, we have finding aids coded like this:



<c02><did><container type="box" label="Box">3-4</container><unittitle>Photographs</unittitle></did></c02>



This imports into ASpace just fine (yay!), but of course also creates a top container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding to:



<c02><did><container type="box" label="Box">3</container><unittitle>Photographs</unittitle></did></c02>



<c02><did><container type="box" label="Box">4 </container><unittitle>Photographs</unittitle></did></c02>



For several reasons, this is not a viable solution for us. Have other institutions figured out a way to deal with this issue that does not include editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image001.png at 01D5F200.0D957C80]<https://urldefense.proofpoint.com/v2/url?u=https-3A__library.unc.edu_wilson_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=tkJE1JdGvSoNb5i6NSRbF3z1n28dGeVJ4ogcFmpTpQo&s=e9r4LIAN87oWg7LLTrzui9bCYcCMX-8twYfh3y0I8tY&e=>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/a529ae55/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8589 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/a529ae55/attachment.png>


More information about the Archivesspace_Users_Group mailing list