[Archivesspace_Users_Group] Deleting in Bulk From the Staff Interface

Thu Dec 15 15:25:14 EST 2016

Thanks, Noah. I've looked at your scripts in the past and liked what I saw.
CalTech is also doing great work with their Go project. That said,
standardizing around a common toolset would take the burden off of
institutions with developing one-off workarounds (assuming they have
developer support in the first place, of course).

We perform all of our bulk operations with the API. For record creation and
updates, I'm using Catmandu <http://librecat.org/> extensively to process
CSV, MARC, and other formats to ArchivesSpace JSON. (Catmandu is a
meta-language that has a lot of support from the European ILS communities
and it's part of the latest branch of Koha.) Happy to share my Catmandu
scripts with you, if you like. There's also an EAD processor
<https://github.com/LibreCat/Catmandu-EAD> already afoot which I'm eager to
implement.

If there's further community interest, I'd be interested in taking this
offline or forming an informal working group.

JL

On Thu, Dec 15, 2016 at 2:25 PM, Noah Huffman <noah.huffman at duke.edu> wrote:

> Jason,
>
>
>
> I’ve used the API to perform several kinds of batch operations, but like
> Bria, I’m no expert.  I describe a few of these operations in this blog
> post
> <http://blogs.library.duke.edu/bitstreams/2016/09/21/archivesspace-api-fun/>.
> I know there are many others who have written little utility scripts
> (usually in Python) to make bulk updates via the API.  Some of those are
> shared on the ArchivesSpace wiki
> <https://archivesspace.atlassian.net/wiki/display/ADC/Plugins+and+Scripts>
> or are available in Github: https://github.com/search?utf8=%E2%9C%93&q=
> archivesspace+scripts
>
>
>
> It would be interesting to identify the most common tasks folks are trying
> to perform using the API and then think about developing those most common
> batch operations into a set of feature requests that could be performed
> directly in the staff interface.  My sense is that so many of the bulk
> operations are really institution-specific, but maybe there are a few
> obvious ones that would rise to the top.  For example, one thing I’d like
> to see is a way to batch import component (archival object) records from
> CSV (not using RDE).  We have some workarounds
> <https://sleepy-ocean-6616.herokuapp.com/> for this and I know others do
> as well.
>
>
>
> -Noah
>
>
>
> ================
>
> Noah Huffman
>
> Archivist for Metadata, Systems, and Digital Records
>
> David M. Rubenstein Rare Book & Manuscript Library
>
> Duke University | 919-660-5982 <(919)%20660-5982>
>
> http://library.duke.edu/rubenstein/
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Bria
> Lynn Parker
> *Sent:* Thursday, December 15, 2016 12:10 PM
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Deleting in Bulk From the
> Staff Interface
>
>
>
> I have command line access to the API, and I've had decent success using
> the API to do bulk updates and deletions. It's been great for when we
> notice something didn't import as we had expected/hoped.
>
>
>
> I used the API extensively when the processing status moved to an event
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__icantiemyownshoes.wordpress.com_2015_11_20_how-2Di-2Dlearned-2Dto-2Dstop-2Dworrying-2Dand-2Dlove-2Dthe-2Dapi_&d=CwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=AwhJM0d3pLVDp4SpyrDUA939maLvuOkFS9pd0S03TX4&s=A5avVx7im_AOTuiBftCnFEI9kRcsmHiCJMCV2Jo6A5I&e=>and
> we didn't want to manually add each one.
>
>
>
> I'm not an expert at it by any means, but I could answer questions for
> anyone who is new to the API and is interested in trying it!
>
>
>
> --
>
> Bria L. Parker
>
> Metadata Librarian
>
> 2200 McKeldin Library
>
> University of Maryland
>
> College Park, MD 20742-7011
>
> (301) 405-9067
>
> blparker at umd.edu
>
>
>
> On Thu, Dec 15, 2016 at 12:03 PM, Jason Loeffler <j at minorscience.com>
> wrote:
>
> In general, I'm interested to know more about how people currently perform
> bulk operations on ArchivesSpace objects, including record creation
> (without the RDE), bulk updates, deletions, etc.
>
>
>
> Just curious if any of you have command line access to the server running
> your ArchivesSpace instance and are able to work with the API. Without it,
> you have to resort to workarounds which, though helpful, can be a little
> clunky and/or error prone.
>
>
>
> It would be great to include a set of bulk operation tools in a future
> ArchivesSpace release.
>
>
> Jason Loeffler
>
> Technology Consultant | The American Academy in Rome
>
> Minor Science | Application Development & Metadata Strategy
>
> Brooklyn, New York
>
> jason at minorscience.com
>
> (347) 405-0826
>
> minorscience (Skype)
>
>
>
>
>
> On Thu, Dec 15, 2016 at 10:07 AM, Noah Huffman <noah.huffman at duke.edu>
> wrote:
>
> Suzanne,
>
>
>
> In addition to Mark’s strategy (I’d never thought of that), here’s another
> way to batch delete components, especially if you need to search for them:
>
>
>
> 1.       Go to Browse>Resources
>
> 2.       Check the “show components” box
>
> 3.       Search for matches in the “Filter by text” box
>
> 4.       Use facets to filter results if necessary
>
> 5.       Check all the archival object records you want to delete
>
> 6.       Click Delete.
>
>
>
> -Noah
>
>
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Custer,
> Mark
> *Sent:* Thursday, December 15, 2016 9:49 AM
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Deleting in Bulk From the
> Staff Interface
>
>
>
> Suzanne,
>
>
>
> Here’s one workaround for that:
>
>
>
> ·         Add a child-level component to the resource, and name it
> something like “delete-me”, and give it any level whatever (since those two
> fields are required to create a new archival object).
>
> ·         Select all of the archival components that you want to delete
> (you can use the shift and/or control keys to select whatever you need to
> select), and then use the “move” function to move them into the
> newly-created delete-me wrapper.
>
> ·         Then, just delete that delete-me component.
>
>
>
> Mark
>
>
>
>
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [
> mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org
> <archivesspace_users_group-bounces at lyralists.lyrasis.org>] *On Behalf Of *Stasiulatis,
> Suzanne
> *Sent:* Thursday, 15 December, 2016 9:32 AM
> *To:* archivesspace_users_group at lyralists.lyrasis.org
> *Subject:* [Archivesspace_Users_Group] Deleting in Bulk From the Staff
> Interface
>
>
>
> Is there any way to delete multiple archival objects in a resource. Can
> you select multiple archival objects and delete them in bulk? What are your
> workarounds or solutions?
>
>
>
> Thanks in advance,
>
>
>
> Suzanne
>
>
>
>
>
> *Suzanne Stasiulatis *| Archivist II
> Pennsylvania Historical and Museum Commission | Pennsylvania State
> Archives
> 350 North Street | Harrisburg, PA 17120-0090
>
> Phone: 717-787-5953 <(717)%20787-5953>
>
> http://www.phmc.pa.gov
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.phmc.pa.gov_&d=CwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=f33wlBF941e1CcSbiMoNu4w15r-LncWN9Jvu2sJL_us&s=8L1uVdHw_uPoFgAUv-p9ds7hvM-TTysrbmyQQ1kMxFU&e=>
>
> sustasiula at pa.gov
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> 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=CwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=AwhJM0d3pLVDp4SpyrDUA939maLvuOkFS9pd0S03TX4&s=S2Az2pFkvwUY3sYvOtWGwgeGCBYxMjGuoxq1lk1mV8Y&e=>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> 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=CwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=AwhJM0d3pLVDp4SpyrDUA939maLvuOkFS9pd0S03TX4&s=S2Az2pFkvwUY3sYvOtWGwgeGCBYxMjGuoxq1lk1mV8Y&e=>
>
>
>
>
>
>
>
> _______________________________________________
> 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/20161215/73a9a9d9/attachment.html>