[Archivesspace_Users_Group] Anyone making use of Harvard's aspace-import-excel plugin?

[Peale, Anne]

Hi Emily,

We installed the plugin about a year ago and it's been working brilliantly.
We have loaded several very large files (up to c. 1500 items), and the
process is a little slow but it does complete.

However, we have also noticed that when we use the plugin in our sandbox
environment, it is much less tolerant of large sets of items and can only
cope with short lists. I'm not the administrator for ASpace at Williams and
don't know much about the way our server is set up, but I wonder if the
problem has something to do with server capacity and if the plugin will
actually work fine when you try to load to your main ASpace system. If
you'd like more information, I can ask our administrator for details.

The plugin has been an absolute joy to work with, especially for importing
legacy finding aids. We've also had good luck having student assistants
enter data into a google form or sheet, then proofreading before importing
-- much smoother than trying to proofread additions made directly by rapid
data entry.

All best,
Anne

On Tue, Jan 8, 2019 at 6:12 PM Emily Pyers <epyers at slv.vic.gov.au> wrote:

> Link to it in GitHub here:
> https://github.com/harvard-library/aspace-import-excel
>
>
>
> We’re really excited about it (the 80% rule!) and have implemented it on
> our test system (v2.4.0).  We’ve been testing it and it’s mostly working
> fine, until we attempt to load spreadsheets that have more than around 100
> lines. Attempts to load spreadsheets over this size are resulting in job
> timeouts and overall system slowdowns, and we’ve tested pretty thoroughly –
> it doesn’t seem to be an issue with the data.  Our tech team have
> reviewed the system logs, but are unable to pinpoint the source of the
> problem.
>
>
>
> I was hoping someone out there might be able to confirm that a) they have
> successfully used the plugin to load spreadsheets greater than 100 lines
> (since this seems to be a point of scepticism for some of our internal
> stakeholders), and that b) if you might be able to point us towards any
> potential areas of investigation?
>
>
>
> I would be so appreciative for any help on this!
>
>
>
> Cheers,
>
>
>
> Emily
>
> *Emily Pyers | Metadata & Archival Systems Specialist | Collection
> Development & Description *
> In the office Monday, Wednesday - Friday 9.30am-3pm
> State Library Victoria | 328 Swanston Street | Melbourne VIC 3000
> T +61 3 8664 7368 | epyers at slv.vic.gov.au
> slv.vic.gov.au
>
>
> <https://www.slv.vic.gov.au/email_campaign>
> [image: follow us]
> [image: SLV facebook]
> <http://www.facebook.com/pages/Melbourne-Australia/State-Library-of-Victoria/32256104331> [image:
> SLV twitter] <http://twitter.com/Library_Vic> [image: SLV youtube]
> <http://www.youtube.com/user/statelibraryvictoria> [image: SLV instagram]
> <http://instagram.com/library_vic> [image: RACV logo]
> This message and any attachment is intended only for the use of the
> Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL.
> If you are not the intended recipient, you are hereby notified that any
> dissemination of this communication is strictly prohibited. If you have
> received this communication in error, please delete all copies of the
> message and its attachments and notify the sender immediately. Thank you.
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190108/801a33bc/attachment.html>