[Archivesspace_Users_Group] ArchivesSpace integrations with Alma

[Kevin Clair]

Hello,

I wrote a plugin that performs some integrations between ArchivesSpace and our 
Alma instance: https://github.com/duspeccoll/alma_integrations

It takes as input a Resource provided by the user; it looks in the user-defined 
field we’ve assigned for Alma MMS IDs to see if one exists, then queries the 
Alma API to determine if there’s a Bibliographic record with that ID, and if 
so, if there are any Holdings records attached to it. From there the user has 
the option to push metadata changes from ArchivesSpace out to Alma (via MARC 
export), and to create new Holdings based on a pre-defined list of location 
codes we use for Special Collections and Archives materials. If the plugin is 
creating a new bibliographic record in Alma, it grabs the MMS ID of the new 
record and adds it to user_defined.string_2 for us.

This code is functional but it’s not very pretty; I have plans to eventually 
clean it up and make it less focused on DU’s specific integration use case 
(i.e. by allowing a user to configure what field the MMS ID is assigned to). If 
you’re an ArchivesSpace/Alma shop and don’t mind taking risks, or would like to 
test it against the Alma sandbox, comments and/or pull requests are welcome!

cheers,
-k
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Slow load time for records with lots of instances

[Christine Di Bella]

Dear Jordon,

There were changes made in version 2.0.0 to better accommodate resource 
hierarchies with many components at the same level as well as records with many 
linked records at the same level. I’d recommend doing a test upgrade to a more 
recent ArchivesSpace version to see if that improves performance with this type 
of record. There are still ways that performance could be improved in the 
application, but given that you’re running a version that is quite a few back 
at this point, that’s where I’d recommend starting.

I think 1300 instances attached to a single accession record (or 1300 top 
containers attached to a single instance) is likely to be an edge case, no 
matter what, however. Please feel free to file a JIRA issue about it, though I 
will admit that accommodating quick loading of such a record may require major 
refactoring of the ArchivesSpace application and we’d have to weigh the pros 
and cons and determine the extent to which such a scenario is needed in the 
community. I’d certainly be interested to hear how common something like this 
is.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Jordon 
Steele
Sent: Tuesday, March 13, 2018 12:44 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Slow load time for records with lots 
of instances

Oh sorry, meant to mention this: 1.5.4.

Best,

Jordon

Jordon Steele
Hodson Curator of the University Archives
Sheridan Libraries
Johns Hopkins University
3400 N Charles St
Baltimore, MD 21218
jste...@jhu.edu

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Donald Mennerich
Sent: Tuesday, March 13, 2018 12:19 PM
To: Archivesspace Users Group 
>
Subject: Re: [Archivesspace_Users_Group] Slow load time for records with lots 
of instances

Jordan:
What version of Aspace are you running?
Don

Donald R. Mennerich, digital archivist
New York University Libraries
don.menner...@nyu.edu (212) 992-6264


On Tue, Mar 13, 2018 at 11:52 AM, Jordon Steele 
> wrote:
Hi,

We have an accession record that has over 1300 containers assigned to it in the 
instance module. The record takes almost 3 minutes to load in the staff 
interface, the same amount of time if you enter data and save. Sometimes, heavy 
interaction with this record causes ASpace to crash. We’ve doubled our memory 
to mitigate this, but there appears to be a correlation between the amount of 
instances we have and the slow load time.

I’m wondering if anyone else in the community has experienced this and/or if 
ASpace is aware of this.

Thanks!

Best,

Jordon

Jordon Steele
Hodson Curator of the University Archives
Sheridan Libraries
Johns Hopkins University
3400 N Charles St
Baltimore, MD 21218
jste...@jhu.edu


___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group