[Archivesspace_Users_Group] EAD import extents mapping

Rees, John (NIH/NLM) [E] reesj at mail.nlm.nih.gov
Thu Jun 21 15:42:59 EDT 2018

Using the background job importer, I'm trying to import extent data from EAD 2002 schema XML, specifically the other extent data we record in parenthesis like <physdesc label="Extent:" encodinganalog="300"> <extent>15.0 linear feet (36 boxes + oversize folder)</extent> </physdesc>

I'd like these parenthetical statements to map to the Container Summary field. According to the EAD import mapper http://archivesspace.org/wp-content/uploads/2016/05/EAD-Import-Export-Mapping-20171030.xlsx anything after a number and space that can't be parsed should import into Container Summary.

Is there a syntax for making this string unparsable and force this behavior? Currently "linear feet (36 boxes + oversize folder)" from the above imports to Extent @Type as a new unique value and I don't want all that data pollution.


John P. Rees
Archivist and Digital Resources Manager
History of Medicine Division
National Library of Medicine

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180621/06944fba/attachment.html>

More information about the Archivesspace_Users_Group mailing list