[Archivesspace_Users_Group] subject/agent marcxml import

Steven Majewski sdm7g at virginia.edu
Wed Nov 5 10:13:59 EST 2014


I have been able to import LCNAF marcxml records downloaded from id.loc.gov 
( and I’ve enabled the lcnaf plugin which seems to be a much handier way to do it ),
but on trying to import LCSH files from the same source, I get an error every time: 

source : Property is required but was missing. 


==================================================


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!  IMPORT ERROR  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
The following errors were found:
	source : Property is required but was missing


 For JSONModel(:subject): 
 #"subject", "external_ids"=>[], "publish"=>true, "terms"=>[{"term_type"=>"geographic", "term"=>"Scotland", "vocabulary"=>"/vocabularies/1"}, {"term_type"=>"topical", "term"=>"History", "vocabulary"=>"/vocabularies/1"}, {"term_type"=>"temporal", "term"=>"James V, 1513-1542", "vocabulary"=>"/vocabularies/1"}], "external_documents"=>[], "uri"=>"/subjects/import_dbea0ae0-f9bc-45f0-a49a-c67ba48bd5cb", "vocabulary"=>"/vocabularies/1"}>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


And if i snag the json output from the parser and stick insert a  ‘source’ : ‘anything’, 
posting to  /repositories/$REPO/batch_imports does successfully create a subject record. 

Should  ‘source’  be optional or have a default value ? 

BTW: Had anyone tried or contemplated batch import of a large set, like the entire LCNAF ? 
Are there performance reasons that might make this a bad idea ? 


Also — same issue as with EAD import: 
Since the import error messages refer to the intermediate JSON model (which we don’t get to see)
rather than the imported XML file, it’s sometimes difficult to figure out exactly what the import problems are
without seeing that intermediate code and comparing it to the schemas or json output from the backend API. 

I’ve been resorting to commenting out the validation and running from the jirb console to produce a JSON
file to insspect,  and perhaps edit and submit to batch_import. It would be nice to have a better way to do this. 

— Steve Majewski







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20141105/e064d3fd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4943 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20141105/e064d3fd/attachment.bin>


More information about the Archivesspace_Users_Group mailing list