[Archivesspace_Users_Group] Is it possible to include a summary note in a digital object CSV?

[Custer, Mark]

Angela,

Just an FYI that the code that I reference is not mine; it’s the code that ArchivesSpace uses for its CSV digital object import process.

Also, if you’re duplicating information between the archival objects and digital objects, is there any reason *not* to try and cut down on that as much as possible (a DAO title is required by ASpace right now, but other than that, there shouldn’t be any need for duplication, I don’t think)?

Sticking with this particular example, though, I think you have a few options (although my personal favorite, which I won’t list again, is simply not to duplicate those notes ☺):

·         Ask for these changes to take place in the core code

·         Use a plugin to modify the behavior of the ASpace CSV digital object importer (Noah Huffman, at Duke, has some good examples of this: https://github.com/noahgh221/archivesspace-duke-plugins)

·         Use the API to make the updates without using the staff interface’s import option.

Mark



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Doiel, Robert
Sent: Friday, 22 April, 2016 12:55 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Is it possible to include a summary note in a digital object CSV?

Hello Angela,

I found looking at http://archivesspace.github.io/archivesspace/api/<https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.github.io_archivesspace_api_&d=AwMGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=2nSz7Byayrt-FrJdVZ2J1CShWmYJkfZx7e0EU1Lnrk0&s=tidtB-S7NK8vQJtSAJ8lZOHTjcqZCXU9oFIsTAd_lAU&e=> after watching the developer screen casts on YouTube very helpful in understanding what was available in the API. The file.API.html document is good for understanding the basic web transaction to get content out or in but doesn’t do the API justice interns of the actual content available (e.g. Fields, sub-fields, and possible values).

All the best,

Robert

--
R. S. Doiel, <rsdoiel at caltech.edu<mailto:rsdoiel at caltech.edu>>
Digital Library Development
Caltech Library

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Angela Kroeger <akroeger at unomaha.edu<mailto:akroeger at unomaha.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Friday, April 22, 2016 at 9:06 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Is it possible to include a summary note in a digital object CSV?

Mark,

Thank you for your helpful reply! I'll start by mentioning that I'm not a programmer and have never used an API before, so I don't know how to do it, but knowing that it CAN be done is a good start.

I looked at your digital object converter code, and I see that there is a bioghist note in it. I imagine a summary note could be added the same way, copying that code? Again, I'm not sure where to put this code or how to use it, but seeing it gives me hope.

I found the documentation for the ArchivesSpace RESTful API on github (http://archivesspace.github.io/archivesspace/doc/file.API.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.github.io_archivesspace_doc_file.API.html&d=AwMGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=2nSz7Byayrt-FrJdVZ2J1CShWmYJkfZx7e0EU1Lnrk0&s=41UC49clPCCwADyt0lvTQCWMkY1CQokwFSlo8ptWKdQ&e=>), but it's somewhat beyond my present level of knowledge and understanding.

Since I know essentially nothing about APIs, I'm going to follow the advice in the University of Michigan's blog post on ArchivesSpace APIs (http://archival-integration.blogspot.com/2015/09/the-archivesspace-api.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__archival-2Dintegration.blogspot.com_2015_09_the-2Darchivesspace-2Dapi.html&d=AwMGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=2nSz7Byayrt-FrJdVZ2J1CShWmYJkfZx7e0EU1Lnrk0&s=HMbmOayjpp8Ag4xXYuG80vs_mie_ACCkOPkz-rer9Lk&e=>) and look at the ArchivesSpace Developer Screencasts (https://www.youtube.com/playlist?list=PLJFitFaE9AY_DDlhl3Kq_vFeX27F1yt6I<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_playlist-3Flist-3DPLJFitFaE9AY-5FDDlhl3Kq-5FvFeX27F1yt6I&d=AwMGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=2nSz7Byayrt-FrJdVZ2J1CShWmYJkfZx7e0EU1Lnrk0&s=c3Sb-xkUuxhFoM1VJFsZ2alLMmEJa7_g4xlpPgV4tis&e=>).

Can you recommend any other resources or tutorials I should look at to get started?
We are hosted by LYRASIS, if that changes anything.

Thanks also for the advice about not using the user defined fields for this. I'll throw that idea away.

You asked how we were using digital objects. You used the phrase "glorified linking mechanism," and that's pretty close to how we're using them. A lot (most) of the information is duplicated between our digital objects and the archival objects they're linked to.

Here's a sample digital object from our institution:
http://unomaha-public.lyrasistechnology.org/repositories/4/digital_objects/211<https://urldefense.proofpoint.com/v2/url?u=http-3A__unomaha-2Dpublic.lyrasistechnology.org_repositories_4_digital-5Fobjects_211&d=AwMGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=2nSz7Byayrt-FrJdVZ2J1CShWmYJkfZx7e0EU1Lnrk0&s=587cXkff2K8Zy-vpNqq6Q3CvbzZuLXJkeHh1Q2cVOYE&e=>

And here's its corresponding archival object:
http://unomaha-public.lyrasistechnology.org/repositories/4/archival_objects/33757<https://urldefense.proofpoint.com/v2/url?u=http-3A__unomaha-2Dpublic.lyrasistechnology.org_repositories_4_archival-5Fobjects_33757&d=AwMGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=2nSz7Byayrt-FrJdVZ2J1CShWmYJkfZx7e0EU1Lnrk0&s=9BydiD3i35oIcQBI0WDTBP5GJeYT6RyozKUQpu3aqN0&e=>

We had considered creating series-level archival objects and linking all appropriate digital objects to them, but after the advice from several folks on this list (discussion in early February), we went with a one-to-one relationship between item-level archival objects and digital objects.

We've been manually adding digital objects and archival objects from our spreadsheet one at a time, and it is painfully slow. I saw the digital object import as a way of cutting out one of the steps. After importing the CSV of digital object records, as far as I can tell, we'll still have to manually create the archival object records and manually link each one to its corresponding digital object. Or can that also be done with an API?

Thanks, again!
--Angela

Angela Kroeger
akroeger at unomaha.edu<mailto:akroeger at unomaha.edu>
Archives and Special Collections Associate
Dr. C.C. and Mabel L. Criss Library
University of Nebraska at Omaha
(402) 554-4159


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