Introduction
Prompt for recruitment.
Tiers of Support
Updates to the MARC Importer
Current copy of the MARC Importer Mapping
Community MARC Discussion
Current behavior:
The MARC importer attempts to separate numeric and textual information in the 300$a, assigning the former to an extent value and the latter to an extent-type value. If the parser fails, a default of 1 linear feet is inserted, presumably because extent is a required field and the import would otherwise fail.
As an aside -- if you bulk-imported MARC records into ArchivesSpace, check to see how many 1 linear feet collections are there - you might be unpleasantly surprised.
5 ǂf boxes ǂa (3 ǂf linear ft.)
Should this pattern be supported? How should this be parsed? How should all of that punctuation be handled?
If an extent cannot be parsed, ASpace supplies “1 linear feet” and does not warn the user. We propose that if the 300 field cannot be parsed, the import should fail. Thoughts?
A recent ticket also noted that 300$f fields are ignored entirely.