[Archivesspace_Users_Group] Error Editing an Accession Record Created Using the Accession CSV Import Template

Custer, Mark mark.custer at yale.edu
Wed Feb 26 09:22:40 EST 2020


No problems at all sharing any and all Resource and Archival Object JSON records.  The only things that would have confidential info at the Beinecke are Accession JSON records.

It looks like the 3 files in "ycal_mss_42" are identical, though (all for the Resource record, though the filenames look like two different archival objects should be included). I'm not sure how the data is going to be extracted by Gobi, but if it follows the model used by the Digitization Work Order, then there could be lots of API calls, since each ancestor (the last being the Resource record) will need to be called, e.g.:

"ancestors": [{"ref": "/repositories/11/archival_objects/752429", "level": "subseries"}, {"ref": "/repositories/11/archival_objects/752356", "level": "subseries"}, {"ref": "/repositories/11/archival_objects/752355", "level": "series"}, {"ref": "/repositories/11/resources/1839", "level": "collection"}]

Speaking of that plugin, it might actually make sense for Gobi to hit those API endpoints.  Of course those endpoints aren't included in ArchivesSpace core, though, so they might not want to do that since it would not be a universal approach (and I suspect that would be their aim now that I think about it), but even if they didn't use them directly, the plugin approach would be a lot more performant than just using the API, I suspect, since the plugin approach can also run SQL queries as needed to speed things up when data needs to be aggregated.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Carbone, Maura <maura.carbone at yale.edu>
Sent: Thursday, February 20, 2020 9:31 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Error Editing an Accession Record Created Using the Accession CSV Import Template


Are you able to look in the logs and see what error you’re getting? It should show a bit more detail about what went wrong.



From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Corinne Chatnik <Corinne.Chatnik at nysed.gov>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, February 20, 2020 at 9:26 AM
To: "archivesspace_users_group at lyralists.lyrasis.org" <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Error Editing an Accession Record Created Using the Accession CSV Import Template


I’m importing Accession data using the Accession CSV Import Template: http://archivesspace.github.io/archivesspace/user/accession-csv-import-template/<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchivesspace.github.io%2Farchivesspace%2Fuser%2Faccession-csv-import-template%2F&data=02%7C01%7Cmark.custer%40yale.edu%7C72f862894f8a47ff0c7508d7b611a72a%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637178059247690136&sdata=NChUbitFEvIygGUFuYfTpJEnLM%2BYnN4OxeruFshECRQ%3D&reserved=0>

The import is successful and can select and view all those new records but when I try to edit a record that I imported I get the error message, “We're sorry, but something went wrong.”

The import csv headers are all in the file in the order in which they appear in the downloaded template.

I also followed all of the advice from this previous post: http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2015-September/002440.html<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fpipermail%2Farchivesspace_users_group%2F2015-September%2F002440.html&data=02%7C01%7Cmark.custer%40yale.edu%7C72f862894f8a47ff0c7508d7b611a72a%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637178059247700130&sdata=M9343PTj96gdp2LSTEM0l6aY5sER7jaHBEYA%2BY7QY0Y%3D&reserved=0>

I created what I thought was an identical accession record to an imported record manually and the manually created accession works as expected.

I’m using ArchivesSpace version 2.6 on windows with a MySQL database. The exact same thing occurs with the sandbox.

Has anyone else experienced this and am I missing something?


Corinne Chatnik
Digital Strategies
New York State Archives
Corinne.Chatnik at nysed.gov<mailto:Corinne.Chatnik at nysed.gov>

Confidentiality Notice

This email including all attachments is confidential and intended solely for the use of the individual or entity to which it is addressed. This communication may contain information that is protected from disclosure under State and/or Federal law. Please notify the sender immediately if you have received this communication in error and delete this email from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200226/86118df3/attachment.html>

More information about the Archivesspace_Users_Group mailing list