[Archivesspace_Users_Group] ArchivesSpace API questions

Kevin W. Schlottmann kws2126 at columbia.edu
Mon Feb 17 10:26:12 EST 2020

Hi Alan,

We faced a similar issue during our EAD migration. We decided to create the
most-updated copy of the record externally to AS by combining legacy
records, deleting the AS record, and re-importing.  We matched on the
bibliographic ID, which is a stable unique identifier in the metadata in
every record. Our basic workflow was captured in Figure 1 here:
https://journal.code4lib.org/articles/14871 We were working in XML, but the
same method could be applied using the JSON record.  The advantage of doing
this is that there was no need to persist AS IDs.  This was possible in
part because we don't use the AS front-end to publish our finding aids, so
this didn't break any existing published links. I'd be happy to chat
offline if you think this approach would be worth exploring.


On Mon, Feb 17, 2020 at 10:03 AM Huebschen, Alan M <ahueb2 at uis.edu> wrote:

> Hi all,
> I've been working on a project to remigrate our original database from
> Archon to ArchivesSpace due to some top container issues in the first
> migration we ran. After our initial migration, changes were made in
> ArchivesSpace and those changes would not be present in the new migration.
> In an attempt to merge the changes from our old ASpace db to the new one,
> I've been working with the ArchivesSpace API via ArchivesSnake to pull JSON
> copies of any record that was modified after the original migration. My
> goal is to import these modified records to the newly migrated db, but I
> seem to have run into a problem.
> After remigrating, it looks like the IDs of records have changed so it
> isn't as easy as deleting the unmodified record from the new migration and
> importing the modified JSON because their IDs do not match up. From what I
> saw in the ArchivesSnake and ASpace API docs, it appears that the only way
> to refer to a record is with that ID. Are there any other ways I can
> compare records through the API or am I stuck using the ID?
> The only way I have been able to compare records to each other and find
> the new ID of the modified record is to iterate over all records in a
> specific category for each and every one of the records I am attempting to
> upload. This takes an incredibly long time. Theoretically I think I can
> load all IDs and records into local memory to iterate over rather than
> querying the ASpace API and this should speed up the process but I was
> wondering if anyone knew of a better way to accomplish this such as using
> EAD ID rather than ID through the API.
> Thank you,
> -Alan Huebschen
> Brookens Library Information Systems
> University of Illinois at Springfield
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Kevin Schlottmann
Head of Archives Processing
Rare Book & Manuscript Library
Butler Library, Room 801
Columbia University
535 W. 114th St., New York, NY  10027
(212) 854-8483
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200217/8eb84c6c/attachment.html>

More information about the Archivesspace_Users_Group mailing list