[Archivesspace_Users_Group] attaching digital objects to archival objects

[Callahan, Maureen]

I’m really thankful for the thoughtful replies and bummed out that this won’t be easy. Kevin, I’m looking at this:

What I ended up having to do was, once the digital object had been created, grab its URI, download the JSON for the original archival object, attach the digital object URI as a linked instance, and re-upload the new JSON through the backend.

What do you mean when you say that you attach the digital object URI as a linked resource here? Do you have examples of this process that you could send me?

My feature request finger is itching…

Maureen


On Aug 7, 2015, at 2:08 PM, Nathan Stevens <ns96 at nyu.edu<mailto:ns96 at nyu.edu>> wrote:

Kevin is correct, this is the way to do this using the REST APIs.  NYU, is also going to have to tackle this issue since they make extensive use of an AT plugin which does this.  I was thinking of creating a desktop version of the AT plugin that works with ASpace, but time or the budget to do so is not currently there.

On Fri, Aug 7, 2015 at 2:02 PM, Kevin Clair <Kevin.Clair at du.edu<mailto:Kevin.Clair at du.edu>> wrote:
Hi Maureen,

I've been working on a plugin that allows us to create new digital objects based on the metadata in an existing item record, to aid in our digitization workflow, and this is one of the problems it sets out to fix for us. What I ended up having to do was, once the digital object had been created, grab its URI, download the JSON for the original archival object, attach the digital object URI as a linked instance, and re-upload the new JSON through the backend. As far as I know that's the only solution, unless it's possible to write a plug-in with a backend controller that handles all those steps in one go.

We also can't do this in batches yet, it only allows for linking single digital objects to single items.

The code is here, with huge caveats that it's written specifically for our workflows and isn't actually in production at Denver yet: https://github.com/duspeccoll/digitized_object<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_duspeccoll_digitized-5Fobject&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=hInqqLnf-60PnmBDeh7I3Kwgy-EPNE_tvp1rzNImRaw&s=ngoF2sPnkYOh89JAmQh_uSlA3cO1tK9PbfJC7Da221A&e=>  -k

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Callahan, Maureen
Sent: Friday, August 07, 2015 11:45 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] attaching digital objects to archival objects

Hi everyone,

This may be a dumb question. I’m trying to wade in from the shallow end.

I have a list of digital objects that I want to create in ArchivesSpace and a list of which archival objects they should become instances of. I’m sitting down to write a script to start doing this work, and I’m wondering if this is possible — if there’s actually an endpoint that will let me do this. I see that I can post children digital objects to already-existing digital objects (POST /repositories/:repo_id/digital_object_components/:id/children), but I don’t see an explicit way to add digital objects as instances of archival objects.

Thoughts? How would others approach this work?

Maureen
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=hInqqLnf-60PnmBDeh7I3Kwgy-EPNE_tvp1rzNImRaw&s=W2RYENC9A3pZfY24DgqHTXH376cGs5UiZJqFIO49f8I&e=>
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=hInqqLnf-60PnmBDeh7I3Kwgy-EPNE_tvp1rzNImRaw&s=W2RYENC9A3pZfY24DgqHTXH376cGs5UiZJqFIO49f8I&e=>



--
Nathan Stevens
Programmer/Analyst
Digital Library Technology Services
New York University

1212-998-2653
ns96 at nyu.edu<mailto:ns96 at nyu.edu>
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=hInqqLnf-60PnmBDeh7I3Kwgy-EPNE_tvp1rzNImRaw&s=W2RYENC9A3pZfY24DgqHTXH376cGs5UiZJqFIO49f8I&e=

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