Mark,
Thanks again for the background information! I was able to add a $f undated
to each 245, and the records did load into AS. Do you know if there is a
way for us to locally edit the mapping table so that item record notes and
barcodes can be imported into the AS records, too?
Thanks!
Eddie
*From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of *Custer,
Mark
*Sent:* Wednesday, May 20, 2020 6:07 PM
*To:* Archivesspace Users Group <
archivesspace_users_group@lyralists.lyrasis.org>
*Subject:* Re: [Archivesspace_Users_Group] MARCXML Import Error
Eddie,
Thanks! Having the file on hand make it much easier to see what’s going
on. The kicker is that the first record that the ASpace MARC importer is
failing on is the record with a title remainder = More “Yale Talks” 😊.
So, the issue is that the ASpace importer isn’t sophisticated enough to
handle every type of MARC record. In this case, the importer is ignoring
the 008 dates in that specific record because those dates are characterized
as Publication and Copyright dates (with the “t” in position 6 of the 008
control field), whereas ASpace is only going to expect begin and/or end
dates. Further, the importer doesn’t look at the 264 field at all, so it’s
not getting the date from there either. An import/export map is available
on the ArchivesSpace website. Here’s a direct link:
https://archivesspace.org/wp-content/uploads/2016/08/MARCXML-Import-Export-Mapping-20130715.xlsx
It’s largely accurate, but I’ve found that sometimes it doesn’t match the
codebase exactly.
Anyhow, it seems that I should be able to add 260s, with a subfield c, for
those records that have the publication and copyright dates in the 008, but
I still got an error when I tried that. Instead, I edited the 008 fields
for the affected records, going with an “s” in position 6, and that made
everything work. And as you said, you could also add a 245$f globally to
get everything to import, but you might want to check and make sure you
don’t wind up duplicate dates in that case, depending on what the importer
does.
A nice feature request would be to update the ASpace MARC importer to
understand 008 fields with publication and copyright dates, as well as the
264 fields, perhaps! But in the meantime, you can edit the MARC records
prior to ingest.
I’m attaching the file that I edited, in hopes that it helps (and that it
works in your instance).
Mark
*From:* archivesspace_users_group-boun...@lyralists.lyrasis.org [
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org
] *On Behalf Of *Eddie
Clem
*Sent:* Wednesday, 20 May, 2020 4:36 PM
*To:* Archivesspace Users Group <
archivesspace_users_group@lyralists.lyrasis.org>
*Subject:* Re: [Archivesspace_Users_Group] MARCXML Import Error
Mark,
Thanks for your reply. I’ve attached the file that I was attempting to
import. I can globally add a 245$f undated if that would make ArchivesSpace
happy….
All of my MARC records do have dates in the 008/260/264 fields….
Eddie
*From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of *Custer,
Mark
*Sent:* Wednesday, May 20, 2020 4:31 PM
*To:* archivesspace_users_group@lyralists.lyrasis.org
*Subject:* Re: [Archivesspace_Users_Group] MARCXML Import Error
Eddie,
ArchivesSpace requires a few different data elements to be present before a
new Resource record can be saved. Based on this error, it looks like the
MARC record does not have any date information where the ArchiveSpace
MARCXML importer would expect dates to be present (i.e. dates : At least 1
item(s) is required). And yet, dates are not required in a MARC
bibliographic record, which is why the file can still be completely valid
but not import.
If you have dates in any of the likely places, like the 008 control field,
or even if there are no dates worth mentioning but you add something like
"undated" to a 245 field, subfield f, then I *think* your file will likely
import fine. But if not, can you attach the file so that someone can take
a look?
I hope that helps,
Mark
--
*From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Eddie
Clem
*Sent:* Wednesday, May 20, 2020 4:18 PM
*To:* archivesspace_users_group@lyralists.lyrasis.org <
archivesspace_users_group@lyralists.lyrasis.org>
*Subject:* [Archivesspace_Users_Group] MARCXML Import Error
Hi! I am trying to import a MARCXML file (for Resource) into ArchivesSpace.
I am getting the following error. I’ve searched the Help Center and Google,
and I can’t figure out what it means. I’ve also validated the XML file with
Oxygen, and it says “validation successful.” Can anyone help me decipher
what this error means and h
