Error importing MODS XML

67 views
Skip to first unread message

elizabet...@mcgill.ca

unread,
Apr 10, 2017, 4:04:53 PM4/10/17
to AtoM Users
Hi,
We have recently installed AtoM 2.3.1 on a linux platform.

I'm trying to import a MODS XML file of name authorities using the Import XML function. The import is failing with "500 Internal Server Error" and the error in web log is: 

FastCGI sent in stderr: "PHP message: Unknown schema or import format: """ while reading response header from upstream, client: 132.206.197.107, server: qa-ams.library.mcgill.ca, request: "POST /index.php/object/import HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.atom.sock:" [...]

The MODS was generated from MARC using MarcEdit. I can confirm that the XML is well-formed and valid (validated using oXygen).  

Has anyone else encountered this issue ?  Can anyone provide samples of MODS XML files which are known to load ?

Many thanks for any light folks might be able to shed.

Tim Hutchinson

unread,
Apr 11, 2017, 11:42:00 AM4/11/17
to AtoM Users, elizabet...@mcgill.ca
Hi Elizabeth,

Does your MODS file include the namespace attributes? I.e.:

With that in the XML, the import works for me in 2.3.

Or are you trying to validate against a different schema? This post reports the same error except for EAD: https://groups.google.com/d/topic/ica-atom-users/CzTim16kqfc/discussion

I should warn you that the MODS import (which we contributed to) was focused on the use case of importing records from Islandora, so the element set is quite limited. Names should import but it's possible there will be subelements or attributes that aren't accounted for in terms of more detailed authority records.

Tim

Elizabeth Thomson

unread,
Apr 11, 2017, 12:20:01 PM4/11/17
to Tim Hutchinson, AtoM Users

Hello Tim,

Many thanks for the suggestion.  I successfully imported a single mods record using <mods> as the root element as per your suggestion. 

 

I was hoping to be able to import a set of records – the file I have uses <modsCollection> as the root element (with namespaces as per your suggestion), which seems to be causing the problem.  I’m curious to know how you imported records from Islandora.

 

Thanks again

Dan Gillean

unread,
Apr 11, 2017, 12:29:17 PM4/11/17
to ICA-AtoM Users, elizabet...@mcgill.ca
Hi Elizabeth,

In case it is useful, I am attaching some resources which I used for some local testing - and I'll report back what I found in 2.3.1.

I have a file I often use for testing (attached below), which I consider a sort of "crosswalk" for AtoM's EAD XML 2002 implementation. Essentially, I have filled out all of AtoM's ISAD fields with the ISAD names, and then exported it as EAD.

I imported this into my 2.3.1 test instance, flipped the template to MODS, and then exported. Then I re-imported the resulting MODS XML as a new file.

The import completed successfully, but with many warnings, shown below:



It appears that some of the standardized MODS controlled vocabulary terms do not exactly match those that AtoM uses, which causes at least some of the warnings. In any case, some data is lost on both export (because there is no clear mapping from ISAD to MODS XML, or because AtoM has not yet implemented one) and on import, likely owing to the same reasons, and the warnings above.

Ultimately, this is the description I ended up with:



It is interesting to note that the dates and creators did not survive this roundtrip experiment. The dates and creator names were included in the export, so this suggests that AtoM's MODS import needs to be addressed.

I hope that this will at least help you perform your own tests, and get a better sense of how AtoM's MODS XML import/export is currently implemented. If you or your institution is interested in sponsoring bug fixes or enhancements to the current functionality, please feel free to contact me off-list.

Cheers,


Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056
@accesstomemory

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/f1515960-e0f2-4a32-bd56-17682a452e68%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

isad-ead-crosswalk-2.3.xml
isad-mods-crosswalk;mods.xml

Elizabeth Thomson

unread,
Apr 11, 2017, 12:39:01 PM4/11/17
to Dan Gillean, ICA-AtoM Users

Hello Dan,

Many thanks for these resources. They’ll be extremely useful to us. 

I now realize that I need to be looking at EAC rather than MODS when dealing with authorities.

 

Thanks !

 

From: Dan Gillean [mailto:d...@artefactual.com]

Sent: Tuesday, April 11, 2017 12:29 PM
To: ICA-AtoM Users <ica-ato...@googlegroups.com>
Cc: Elizabeth Thomson <elizabet...@mcgill.ca>

To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.

Hutchinson, Tim

unread,
Apr 11, 2017, 1:13:09 PM4/11/17
to Elizabeth Thomson, AtoM Users

Hi Elizabeth,

 

I’m pretty sure <modsCollection> is not supported. But you’d be able to do a batch import of any number of individual via the command line.

 

In terms of Islandora, we haven’t taken this into production yet, but we developed a custom module to batch export the MODS (more generally any datastream) from Islandora. It’s currently available in Islandora Labs:

https://github.com/Islandora-Labs/islandora_datastream_exporter

 

Tim

 

Tim Hutchinson
Head, University Archives & Special Collections
University Library, University of Saskatchewan

Tel: (306) 966-6028  Fax: (306) 966-6040

Email: tim.hut...@usask.ca

Web: http://library.usask.ca/archives/

elizabet...@mcgill.ca

unread,
Apr 12, 2017, 5:09:35 PM4/12/17
to AtoM Users, elizabet...@mcgill.ca
Hi Tim,
Many thanks for the reminder about the command line option. I'll be sure to explore it.


On Tuesday, 11 April 2017 13:13:09 UTC-4, Tim Hutchinson wrote:

Hi Elizabeth,

 

I’m pretty sure <modsCollection> is not supported. But you’d be able to do a batch import of any number of individual via the command line.

 

In terms of Islandora, we haven’t taken this into production yet, but we developed a custom module to batch export the MODS (more generally any datastream) from Islandora. It’s currently available in Islandora Labs:

https://github.com/Islandora-Labs/islandora_datastream_exporter

 

Tim

 

Tim Hutchinson
Head, University Archives & Special Collections
University Library, University of Saskatchewan

Tel: (306) 966-6028  Fax: (306) 966-6040

Email: tim.hut...@usask.ca

Web: http://library.usask.ca/archives/

 

From: Elizabeth Thomson [mailto:elizabet...@mcgill.ca]
Sent: Tuesday, April 11, 2017 10:20 AM
To: Hutchinson, Tim <tim.hut...@usask.ca>; AtoM Users <ica-ato...@googlegroups.com>
Subject: RE: Error importing MODS XML

 

Hello Tim,

Many thanks for the suggestion.  I successfully imported a single mods record using <mods> as the root element as per your suggestion. 

 

I was hoping to be able to import a set of records – the file I have uses <modsCollection> as the root element (with namespaces as per your suggestion), which seems to be causing the problem.  I’m curious to know how you imported records from Islandora.

 

Thanks again

Reply all
Reply to author
Forward
0 new messages