[Archivesspace_Users_Group] digital object import questions
Brian Hoffman
brianjhoffman at gmail.com
Wed Apr 8 12:18:06 EDT 2015
Hi Ben,
No, with the current digital object importer, you can’t do that.
Brian
On Apr 8, 2015, at 11:03 AM, Ben Goldman <bmg17 at psu.edu> wrote:
> Hi Brian,
>
> Thanks for the tip. That did the trick.
>
> I'm still wondering, however, whether there's any way to identify a related archival object on import, rather than attaching each of these manually after import.
>
> Thanks,
> Ben
>
> ----- Original Message -----
> From: "Brian Hoffman" <brianjhoffman at gmail.com>
> To: "Archivesspace Users Group" <archivesspace_users_group at lyralists.lyrasis.org>
> Sent: Tuesday, April 7, 2015 1:16:19 PM
> Subject: Re: [Archivesspace_Users_Group] digital object import questions
>
> Hi,
>
> You need to add a ‘is_component’ column with a value of ‘true’ for each row.
>
> Also, you need to add a row for the parent object (digital_object_id: pstsc_00084, is_component: false, digital_object_component_id: null)
>
> Brian
>
>
> On Apr 7, 2015, at 12:57 PM, Ben Goldman <bmg17 at psu.edu> wrote:
>
>> Hello everyone,
>>
>> I'm testing the digital object import option in ASpace and am encountering an issue. I am trying to import a group of digital objects and make them components of a parent digital object record. I've set this up according to the import mappings, which seem to indicate I should use the parent digital_object_id for the each row's digital_object_id, then use digital_object_component_id for the component level identifier values. Even so, I get an error on import (see attached screenshot).
>>
>> More generally, I am wondering if there is a way to relate these digital objects with archival objects on ingest. A use case might be we digitize 100 audio cassettes related to a collection, and then import a modified metadata spreadsheet (somewhat unsatisfying, obviously) to create digital objects. I don't think it will be feasible for us to move through these 100 new digital objects one by one attaching them to archival objects.
>>
>> By the way, we are still in v1.1.2, so if the error noted is addressed in 1.2, great!
>>
>> Best,
>> Ben
>>
>>
>> Ben Goldman
>> Digital Records Archivist
>> Penn State University Libraries
>> University Park, PA
>> 814-863-8333
>> http://www.libraries.psu.edu/psul/speccolls.html <Sheet1.csv><Screen Shot 2015-04-07 at 12.52.31 PM.png>_______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
More information about the Archivesspace_Users_Group
mailing list