[Archivesspace_Users_Group] Archivesspace_Users_Group Digest, Vol 50, Issue 5
Cobourn, Alston
Alston.Cobourn at tamucc.edu
Mon Sep 18 18:23:39 EDT 2017
Re 4- Classifications
We have a Record Group classification and a Manuscript Collections classification. Therefore, we also find classifications useful for the reason Christie described, internal sorting and filter.
However, in the new public interface (which I generally LOVE), it seems that classifications displays in the menu and the Resource Records notes section with the label "Record Groups". This seems odd to me, as if classifications is not mean to be broader, and clearly does not work well in our usage of Classifications. So I will be asking my IT guy to try and remove that label from the main menu and to make that note not display or to relabel it if easier for him. Just an FYI if you plan to implement PUI later.
-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of archivesspace_users_group-request at lyralists.lyrasis.org
Sent: Monday, September 18, 2017 4:05 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: Archivesspace_Users_Group Digest, Vol 50, Issue 5
Send Archivesspace_Users_Group mailing list submissions to
archivesspace_users_group at lyralists.lyrasis.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
or, via email, send a message with subject or body 'help' to
archivesspace_users_group-request at lyralists.lyrasis.org
You can reach the person managing the list at
archivesspace_users_group-owner at lyralists.lyrasis.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of Archivesspace_Users_Group digest..."
Today's Topics:
1. Deleting Empty Top Containers (Stasiulatis, Suzanne)
2. Re: Deleting Empty Top Containers (Custer, Mark)
3. Re: Deleting Empty Top Containers (Galligan, Patrick)
4. Re: Classifications (Christie Peterson)
5. Deleting all the digital objects in a repository
(Daniel L Thacker)
6. Re: Deleting all the digital objects in a repository
(Jason Loeffler)
7. Re: Deleting all the digital objects in a repository
(Daniel L Thacker)
8. Top Containers Not Showing (Megan Blair)
----------------------------------------------------------------------
Message: 1
Date: Sat, 16 Sep 2017 17:55:14 +0000
From: "Stasiulatis, Suzanne" <sustasiula at pa.gov>
To: "archivesspace_users_group at lyralists.lyrasis.org"
<archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers
Message-ID: <3134b6337c3a483d8af4316b4b507bbe at ENCTCEXCH008.PA.LCL>
Content-Type: text/plain; charset="us-ascii"
Hello,
I am working in ArchivesSpace version 1.5.4. I'd like to delete all of our empty top containers through the staff interface. By empty, I mean top containers that aren't linked to any archival objects. I believe we created containers in the archival object page and then unlinked them at some point.
In Manage Top Containers, you can choose Yes for Unassociated containers and leave all other fields blank. This gives us a very long list. Can anyone confirm that this list includes all of our empty top containers and only our empty top containers?
[cid:image001.png at 01D32EEF.C216EC60]
Thanks!
Suzanne
Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090 www.phmc.pa.gov/Archives<http://www.phmc.pa.gov/Archives>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170916/2ce5e790/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 52962 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170916/2ce5e790/attachment-0001.png>
------------------------------
Message: 2
Date: Sun, 17 Sep 2017 18:09:48 +0000
From: "Custer, Mark" <mark.custer at yale.edu>
To: "archivesspace_users_group at lyralists.lyrasis.org"
<archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Deleting Empty Top Containers
Message-ID:
<BN3PR08MB1303545AA8A2E9CF54AD27AF8C620 at BN3PR08MB1303.namprd08.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"
Hi, Suzanne.
Yep, that's exactly the way to do it, and exactly why the "unassociated" option was added.
Since top containers are scoped to repositories, though, if you have multiple repositories in your installation, then you'll need to perform this action within each repository. We've assigned this cleanup task as something that our repository managers should do on a periodic basis.
We haven't decided to automate this task yet, however, which I guess gives us the opportunity to make sure that everything looks okay before activating the bulk delete option. That said, I think that automating this on a periodic basis outside of normal business hours could be the way to go. We had originally hoped that orphaned top containers could never be created in the staff application, but given that they can be associated with different resource, accession, and archival object records, it would be a bit tricky to do that, so orphaned, or unassociated, top containers will be created if an entire resource record is deleted, for instance. Same thing happens right now for digital object records; the only difference there is that digital objects can also be created as stand-alone records in the staff interface, whereas you can't do that with top containers (without using the API).
Mark
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Stasiulatis, Suzanne <sustasiula at pa.gov>
Sent: Saturday, September 16, 2017 1:55:14 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers
Hello,
I am working in ArchivesSpace version 1.5.4. I?d like to delete all of our empty top containers through the staff interface. By empty, I mean top containers that aren?t linked to any archival objects. I believe we created containers in the archival object page and then unlinked them at some point.
In Manage Top Containers, you can choose Yes for Unassociated containers and leave all other fields blank. This gives us a very long list. Can anyone confirm that this list includes all of our empty top containers and only our empty top containers?
[cid:image001.png at 01D32EEF.C216EC60]
Thanks!
Suzanne
Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090 www.phmc.pa.gov/Archives<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.phmc.pa.gov_Archives&d=DwMFAg&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=p6DgPzipKtHj5MNdBWmiUC7F9PxIagbI68ckkTxVYSQ&s=L5_6KoOslchLuYAG4MlU2hUAyE1KmI2Y-fkbpZn5N5o&e=>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170917/fc1da9b1/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 52962 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170917/fc1da9b1/attachment-0001.png>
------------------------------
Message: 3
Date: Mon, 18 Sep 2017 13:05:27 +0000
From: "Galligan, Patrick" <PGalligan at rockarch.org>
To: Archivesspace Users Group
<archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Deleting Empty Top Containers
Message-ID: <EA3AD6DB-B6C9-44C9-AA06-8D8C2A885A79 at rockarch.org>
Content-Type: text/plain; charset="utf-8"
Hey Suzanne,
We have automated this process for the most part.
If you want to have a method to just delete all orphaned top containers, you chan check out this Python script I wrote up really quickly: https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asDeleteOrphanContainers.py
Let me know if you have any questions.
From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Custer, Mark" <mark.custer at yale.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Sunday, September 17, 2017 at 2:09 PM
To: "archivesspace_users_group at lyralists.lyrasis.org" <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Deleting Empty Top Containers
Hi, Suzanne.
Yep, that's exactly the way to do it, and exactly why the "unassociated" option was added.
Since top containers are scoped to repositories, though, if you have multiple repositories in your installation, then you'll need to perform this action within each repository. We've assigned this cleanup task as something that our repository managers should do on a periodic basis.
We haven't decided to automate this task yet, however, which I guess gives us the opportunity to make sure that everything looks okay before activating the bulk delete option. That said, I think that automating this on a periodic basis outside of normal business hours could be the way to go. We had originally hoped that orphaned top containers could never be created in the staff application, but given that they can be associated with different resource, accession, and archival object records, it would be a bit tricky to do that, so orphaned, or unassociated, top containers will be created if an entire resource record is deleted, for instance. Same thing happens right now for digital object records; the only difference there is that digital objects can also be created as stand-alone records in the staff interface, whereas you can't do that with top containers (without using the API).
Mark
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Stasiulatis, Suzanne <sustasiula at pa.gov>
Sent: Saturday, September 16, 2017 1:55:14 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers
Hello,
I am working in ArchivesSpace version 1.5.4. I?d like to delete all of our empty top containers through the staff interface. By empty, I mean top containers that aren?t linked to any archival objects. I believe we created containers in the archival object page and then unlinked them at some point.
In Manage Top Containers, you can choose Yes for Unassociated containers and leave all other fields blank. This gives us a very long list. Can anyone confirm that this list includes all of our empty top containers and only our empty top containers?
[cid:image001.png at 01D3305D.44B4D5B0]
Thanks!
Suzanne
Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090 www.phmc.pa.gov/Archives<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.phmc.pa.gov_Archives&d=DwMFAg&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=p6DgPzipKtHj5MNdBWmiUC7F9PxIagbI68ckkTxVYSQ&s=L5_6KoOslchLuYAG4MlU2hUAyE1KmI2Y-fkbpZn5N5o&e=>
sustasiula at pa.gov<mailto:sustasiula at pa.gov>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170918/8e24888f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 52963 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170918/8e24888f/attachment-0001.png>
------------------------------
Message: 4
Date: Mon, 18 Sep 2017 13:59:31 +0000
From: Christie Peterson <cpeterson at smith.edu>
To: Archivesspace Users Group
<archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Classifications
Message-ID:
<CAFy-AY+Mkxkr3O_t67FjaRvaiR5bGSFGDSc94FVnxSd-9zMvWg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Nancy,
We aren't using the PUI right now, but have plans in that direction over the next 1-2 years. I honestly don't know if the classifications appear in the EAD, but even if they did I doubt that the consortial service we use to display them would do anything interesting with it. Right now, our biggest users of it are internal staff, and for that alone it's worth it.
Best,
Christie
On Fri, Sep 15, 2017 at 5:59 PM Kennedy, Nancy <KennedyN at si.edu> wrote:
> Thanks Christie. I see now .. I can add the classification parent or
> child from the accessions edit screen, even if I can't from the
> classification child screen itself.
>
> Are you all using the PUI? I wonder if it makes sense to make the
> classification available in the EAD.
>
>
> Nancy Kennedy
> Smithsonian Institution
> kennedyn at si.edu
> ------------------------------
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [
> archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of
> Christie Peterson [cpeterson at smith.edu]
> *Sent:* Friday, September 15, 2017 5:13 PM
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] Classifications
>
> Hi Nancy,
>
> We're using the classifications strictly for our College Archives,
> which has a long-standing Record Group system in place. We're not
> using it for the Sophia Smith Collection or the Mortimer Rare Book
> Collection, both of which are set up as separate repositories within our ASpace instance.
>
> The classifications mirror the pre-existing RG system, so, for
> example,
> RG12 is "Special Events and People," and the child classification
> 12.01 is "Anniversaries."
>
> [image: Screen Shot 2017-09-15 at 5.10.27 PM.png] We just went into
> production with this, so I can't comment on how well it works yet, but
> it seemed like the logical thing for us to do. We do have accessions
> linked to both top-level and child-level classifications, so that
> functionality appears to work.
>
> Best,
>
> Christie Peterson
>
> On Fri, Sep 15, 2017 at 4:52 PM Kennedy, Nancy <KennedyN at si.edu> wrote:
>
>> All ?
>>
>> How are you using classifications at your institutions? In
>> particular, can anyone speak to the nested ?child? classifications?
>> I?ve been looking at the feature in our test installations, but am
>> interested to see if anyone is using this out in the wild. What?s
>> the purpose of nested child classifications, given that it seems I
>> can only attach a resource/accession/digital object to the top parent classification term?
>>
>>
>>
>> I see AR-1884 <https://archivesspace.atlassian.net/browse/AR-1884>
>> suggesting that classifications be available across multiple repositories.
>> I can see some benefit there, though so far, most of my users have
>> seemed to prefer the idea that classifications would be repo
>> specific. We haven?t adopted classifications yet, but if it looks
>> like they would become global, I?d like to get more details sooner than later.
>>
>>
>>
>>
>>
>> Thanks!
>>
>>
>>
>>
>>
>> Nancy Kennedy
>>
>> Smithsonian Institution
>>
>> kennedyn at si.edu
>>
>>
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_gro
>> up
>>
> --
> ??
> Christie S. Peterson
>
> Head of Technical Services for Special Collections Smith College
> Northampton, Mass.
> 413-585-2996 <(413)%20585-2996>
> cpeterson at smith.edu
>
> pronouns: she/her/hers
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_grou
> p
>
--
?
Christie S. Peterson
Head of Technical Services for Special Collections Smith College Northampton, Mass.
413-585-2996
cpeterson at smith.edu
pronouns: she/her/hers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170918/67e75698/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-09-15 at 5.10.27 PM.png
Type: image/png
Size: 58683 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170918/67e75698/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-09-15 at 5.10.27 PM.png
Type: image/png
Size: 58683 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170918/67e75698/attachment-0003.png>
------------------------------
Message: 5
Date: Mon, 18 Sep 2017 14:18:11 +0000
From: Daniel L Thacker <Daniel.Thacker at tamuk.edu>
To: "archivesspace_users_group at lyralists.lyrasis.org"
<archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Deleting all the digital objects
in a repository
Message-ID:
<CY4PR08MB27606D60641FE1B1EB1EAA4481630 at CY4PR08MB2760.namprd08.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"
I was using a second repository to upload legacy collections into ASpace and then once the finding aid was complete I would transfer them over to our main repository. The trouble I ran into was the digital objects transferred but they stayed in the second repository. Is there anyway to do a mass deletion? There is around 11,000 digital objects and right now the only way I can delete them is one by one and 10 per page.
Thanks,
Daniel Thacker
Digital Archivist
James C. Jernigan Library
Texas A&M University-Kingsville
MSC 197
700 University Blvd
Kingsville, TX 78363-8202
361-593-4154
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170918/a1a19e99/attachment-0001.html>
------------------------------
Message: 6
Date: Mon, 18 Sep 2017 13:03:24 -0400
From: Jason Loeffler <j at minorscience.com>
To: Archivesspace Users Group
<archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Deleting all the digital
objects in a repository
Message-ID:
<CAP4gJsUXBtF9+6KiAHESaMFAfieaM-hGsQnZx7_QW1OmdQM=fg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Daniel,
To my knowledge, bulk delete operations of resource components and digital objects from the staff interface is not currently supported.
I'm not sure whether you can simply delete the repository, as it may orphan the digital objects it contains. Maybe someone else can confirm.
If you're able to gain command line access to your instance, you can first list all of the ids in a given repository, then pipe that into a delete request.
More here:
https://archivesspace.github.io/archivesspace/api/#post-repo
sitories-repo_id-digital_objects
https://archivesspace.github.io/archivesspace/api/#delete-re
positories-repo_id-digital_objects-id
Lydia Tang pulled together existing JIRA tickets on this matter here:
https://archivesspace.atlassian.net/browse/AR-1849
Some of us the Technical Advisory Council are interested in putting together an API cookbook for cases like yours. I'll add it to our work plan.
It's also possible to do this with a plugin, though that's certainly more labor intensive.
Note that you can increase the default page size by editing config.rb at "AppConfig[:default_page_size]".
Best, Jason
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 Mon, Sep 18, 2017 at 10:18 AM, Daniel L Thacker <Daniel.Thacker at tamuk.edu
> wrote:
> I was using a second repository to upload legacy collections into
> ASpace and then once the finding aid was complete I would transfer
> them over to our main repository. The trouble I ran into was the digital objects
> transferred but they stayed in the second repository. Is there anyway to
> do a mass deletion? There is around 11,000 digital objects and right
> now the only way I can delete them is one by one and 10 per page.
>
>
> Thanks,
>
>
> Daniel Thacker
>
> Digital Archivist
>
> James C. Jernigan Library
>
> Texas A&M University-Kingsville
>
> MSC 197
>
> 700 University Blvd
>
> Kingsville, TX 78363-8202
>
> 361-593-4154 <(361)%20593-4154>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_grou
> p
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170918/a87be318/attachment-0001.html>
------------------------------
Message: 7
Date: Mon, 18 Sep 2017 17:31:13 +0000
From: Daniel L Thacker <Daniel.Thacker at tamuk.edu>
To: Archivesspace Users Group
<archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Deleting all the digital
objects in a repository
Message-ID:
<CY4PR08MB2760923FDE2E0596F622A72581630 at CY4PR08MB2760.namprd08.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Thank you Jason,
There is a plug in for digital object duplicates. I would think there might be a plug in for the current problem as well.
We are re-updating some collections and I can change them quickly with a pythonscipt, where I can delete the collection and reupload it, and then delete the duplicates with the plug in. It seems like there would be a way to delete the collection along with the digital objects.
Thank you again for your input. I may just delete that repository, but I will hold off until I get confirmation on the possible orphan digital objects.
Sincerely,
Daniel Thacker
Digital Archivist
James C. Jernigan Library
Texas A&M University-Kingsville
MSC 197
700 University Blvd
Kingsville, TX 78363-8202
361-593-4154
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jason Loeffler <j at minorscience.com>
Sent: Monday, September 18, 2017 12:03:24 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Deleting all the digital objects in a repository
Hi Daniel,
To my knowledge, bulk delete operations of resource components and digital objects from the staff interface is not currently supported.
I'm not sure whether you can simply delete the repository, as it may orphan the digital objects it contains. Maybe someone else can confirm.
If you're able to gain command line access to your instance, you can first list all of the ids in a given repository, then pipe that into a delete request.
More here:
https://archivesspace.github.io/archivesspace/api/#post-repositories-repo_id-digital_objects<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.github.io_archivesspace_api_-23post-2Drepositories-2Drepo-5Fid-2Ddigital-5Fobjects&d=DwMFaQ&c=URKFmO0h1-PpCttSQ3v_bEhalPi_sNmh-_LG0Bso5YA&r=b3souzMEzT-OJXsXOvK9YInkZPMZDws8WozdGpuzrcA&m=cIh8DAXEdTsqpYxu3tHEFcot0Z5u2rRcqdQp3MsAqi4&s=KylN3EW7nIY-_R9gLIYHS_FBrP9lrk_n4kuuEUzN3EM&e=>
https://archivesspace.github.io/archivesspace/api/#delete-repositories-repo_id-digital_objects-id<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.github.io_archivesspace_api_-23delete-2Drepositories-2Drepo-5Fid-2Ddigital-5Fobjects-2Did&d=DwMFaQ&c=URKFmO0h1-PpCttSQ3v_bEhalPi_sNmh-_LG0Bso5YA&r=b3souzMEzT-OJXsXOvK9YInkZPMZDws8WozdGpuzrcA&m=cIh8DAXEdTsqpYxu3tHEFcot0Z5u2rRcqdQp3MsAqi4&s=mO-r53fLxruObcmepFWQYefXvkRKmyhKZSOnXsQ9mrM&e=>
Lydia Tang pulled together existing JIRA tickets on this matter here: https://archivesspace.atlassian.net/browse/AR-1849<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1849&d=DwMFaQ&c=URKFmO0h1-PpCttSQ3v_bEhalPi_sNmh-_LG0Bso5YA&r=b3souzMEzT-OJXsXOvK9YInkZPMZDws8WozdGpuzrcA&m=cIh8DAXEdTsqpYxu3tHEFcot0Z5u2rRcqdQp3MsAqi4&s=95IvpQKyhWLa5cDlu5e5zak4-K6T0deLs2QmkZPQfQo&e=>
Some of us the Technical Advisory Council are interested in putting together an API cookbook for cases like yours. I'll add it to our work plan.
It's also possible to do this with a plugin, though that's certainly more labor intensive.
Note that you can increase the default page size by editing config.rb at "AppConfig[:default_page_size]".
Best, Jason
Jason Loeffler
Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com<mailto:jason at minorscience.com>
(347) 405-0826<tel:(347)%20405-0826>
minorscience (Skype)
On Mon, Sep 18, 2017 at 10:18 AM, Daniel L Thacker <Daniel.Thacker at tamuk.edu<mailto:Daniel.Thacker at tamuk.edu>> wrote:
I was using a second repository to upload legacy collections into ASpace and then once the finding aid was complete I would transfer them over to our main repository. The trouble I ran into was the digital objects transferred but they stayed in the second repository. Is there anyway to do a mass deletion? There is around 11,000 digital objects and right now the only way I can delete them is one by one and 10 per page.
Thanks,
Daniel Thacker
Digital Archivist
James C. Jernigan Library
Texas A&M University-Kingsville
MSC 197
700 University Blvd
Kingsville, TX 78363-8202
361-593-4154<tel:(361)%20593-4154>
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto: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=DwMFaQ&c=URKFmO0h1-PpCttSQ3v_bEhalPi_sNmh-_LG0Bso5YA&r=b3souzMEzT-OJXsXOvK9YInkZPMZDws8WozdGpuzrcA&m=cIh8DAXEdTsqpYxu3tHEFcot0Z5u2rRcqdQp3MsAqi4&s=FPmKPUrRup58hjt2FkcXMyfqLdJrNTGtMi9HicK1PdI&e=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170918/14818d94/attachment-0001.html>
------------------------------
Message: 8
Date: Mon, 18 Sep 2017 16:04:34 -0500
From: Megan Blair <mblair1 at stedwards.edu>
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Top Containers Not Showing
Message-ID:
<CAHMBTNniVHLKiKzSOevzDf8-dYs1FALLTve9i17aqDZkq93B_Q at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
We had a issue start this weekend where top containers after number 9 are no longer showing in the drop down. I have tried a couple of different work arounds but the only way I am getting it to show up is to click browse and then keyword search box 10 or box 11. I have attached a screenshot.
Any suggestions?
Thanks!
Megan[image: Inline image 1]
--
Megan M. Blair
Archivist and Public Services Librarian
Munday Library
St. Edward's University
3001 S. Congress Ave.
Austin, TX 78704
512.428.1047
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170918/30b12bb8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-09-18 at 4.02.43 PM.png
Type: image/png
Size: 543297 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170918/30b12bb8/attachment.png>
------------------------------
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
End of Archivesspace_Users_Group Digest, Vol 50, Issue 5
********************************************************
More information about the Archivesspace_Users_Group
mailing list