From kws2126 at columbia.edu  Mon Jun  1 14:27:32 2020
From: kws2126 at columbia.edu (Kevin W. Schlottmann)
Date: Mon, 1 Jun 2020 14:27:32 -0400
Subject: [Archivesspace_Users_Group] Duplicated fields in resources bug?
Message-ID: <CAPB3iyHC+cTFfiNFN1dWNzZ_BSLisQfxwM4nzOgrHWn90iFLvg@mail.gmail.com>

 Hi all,

We are chasing an odd bug where certain fields are being inadvertently
duplicated by AS when some other edit action is taken on the resource
record.  The fields being duplicated are language notes, extent notes, and
date notes at the resource-level.

We are unable to replicate the bug reliably, on any given record, or for a
record on a Test server where we see the behavior on Production. We are
running 2.7.0, hosted by Lyrasis, with limited customizations.

Has anyone come across this or a similar bug?

Kevin

-- 
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/20200601/be829a8f/attachment.html>

From dmichelson at smith.edu  Mon Jun  1 14:51:58 2020
From: dmichelson at smith.edu (Daniel Michelson)
Date: Mon, 1 Jun 2020 14:51:58 -0400
Subject: [Archivesspace_Users_Group] Duplicated fields in resources bug?
In-Reply-To: <CAPB3iyHC+cTFfiNFN1dWNzZ_BSLisQfxwM4nzOgrHWn90iFLvg@mail.gmail.com>
References: <CAPB3iyHC+cTFfiNFN1dWNzZ_BSLisQfxwM4nzOgrHWn90iFLvg@mail.gmail.com>
Message-ID: <CAOS_AZkgO34edWRf9VCHmYyH05=doGBCXh07pswyeS-CsP+Fig@mail.gmail.com>

Hi Kevin,

I'm sure this isn't much help, but we've also encountered this bug on one
resource record in 2.7.1.  We could not determine what might have caused it.

Dan

On Mon, Jun 1, 2020 at 2:27 PM Kevin W. Schlottmann <kws2126 at columbia.edu>
wrote:

> Hi all,
>
> We are chasing an odd bug where certain fields are being inadvertently
> duplicated by AS when some other edit action is taken on the resource
> record.  The fields being duplicated are language notes, extent notes,
> and date notes at the resource-level.
>
> We are unable to replicate the bug reliably, on any given record, or for a
> record on a Test server where we see the behavior on Production. We are
> running 2.7.0, hosted by Lyrasis, with limited customizations.
>
> Has anyone come across this or a similar bug?
>
> Kevin
>
> --
> 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
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Dan Michelson
Project Manager Archivist
Smith College Special Collections

The Special Collections reading room is closed. As of March 18th, all
Special Collections staff will be working remotely. Smith course support is
our primary responsibility at this time.

Minimal reference services will be managed remotely by staff. Reference
inquiries that require access to physical materials will be held in order
of when they were received and responded to once the campus is reopened.
Expect a four to six week delay, minimum. There is a moratorium on
digitization services.

For information about Smith College?s response to Covid-19, please visit
the college?s official website
<https://www.smith.edu/student-life/health-wellness/coronavirus>. For
information about library services during this time, information is
available on our website
<https://libraries.smith.edu/library-services-during-covid-19>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200601/ad789b9a/attachment.html>

From gordon_daines at byu.edu  Mon Jun  1 16:55:07 2020
From: gordon_daines at byu.edu (Gordon Daines)
Date: Mon, 1 Jun 2020 20:55:07 +0000
Subject: [Archivesspace_Users_Group] 4th Quarter Board Update
Message-ID: <DM5PR08MB2667562AF3EC5074E7B1C99B9A8A0@DM5PR08MB2667.namprd08.prod.outlook.com>

Dear ArchivesSpace members,
I first want to acknowledge the incredible sadness and challenges of the times through which we are living. Where we are and what we are doing now is probably not what most of us expected when the year began. Thank you for being with us, in whatever way you are able.

I am writing to report on the ArchivesSpace Governance Board 4th Quarter meeting, a virtual meeting that was conducted on May 21st.

The board approved appointments to the Technical Advisory Council and User Advisory Council, and the election slate for the Governance Board. We thanked the Nominating Committee, chaired by John Wilkin, for their careful and hard work. John will send out an announcement of all of the appointments once the process is complete.

We reviewed:

  *   an operations report which highlighted the many COVID-19 related activities that the ArchivesSpace team is supporting for the larger archival community during this challenging time
  *   a financial report that confirmed we are on budget
  *   the continued excellent work of TAC and UAC and thanked the members for their dedicated participation

We discussed membership renewal efforts underway to ensure we can continue to support the larger community and continued advancement of the software.

This will be my last message to the community as Board Chair as my one-year term ends June 30, 2020.  I have been privileged to serve in this role. Nick Zmijewski will serve as the next Governance Board Chair effective July 1. We are especially pleased to have Nick in this pivotal position as he will be the first representative from the "Very Small" membership level to serve as Chair. Thank you Nick!

As we look ahead to a new membership year, while there is much uncertainty and trepidation in our world, there is also much for which to be thankful. What we know for certain for ArchivesSpace is that our community members will continue to support each other, and those we each serve, in many ways. The Board welcomes your communications and comments on anything mentioned here, or anything else related to ArchivesSpace that is of concern or interest to you.



_______________________________________
J. Gordon Daines III
Curator of Research and Instruction Services
Curator of the Yellowstone National Park collection
1130 HBLL
Brigham Young University
Provo, UT 84602
801-422-5821
gordon_daines at byu.edu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200601/d42a8c0b/attachment.html>

From kws2126 at columbia.edu  Tue Jun  2 12:48:17 2020
From: kws2126 at columbia.edu (Kevin W. Schlottmann)
Date: Tue, 2 Jun 2020 12:48:17 -0400
Subject: [Archivesspace_Users_Group] Duplicated fields in resources bug?
In-Reply-To: <CAOS_AZkgO34edWRf9VCHmYyH05=doGBCXh07pswyeS-CsP+Fig@mail.gmail.com>
References: <CAPB3iyHC+cTFfiNFN1dWNzZ_BSLisQfxwM4nzOgrHWn90iFLvg@mail.gmail.com>
 <CAOS_AZkgO34edWRf9VCHmYyH05=doGBCXh07pswyeS-CsP+Fig@mail.gmail.com>
Message-ID: <CAPB3iyHtXtpA9FUn9HEkntALptBLBr6jgtVkhXPNMy5G2JSMtw@mail.gmail.com>

Thanks Dan.  I'm glad (I guess?) to hear that it's not unique to our
instance.

On Mon, Jun 1, 2020 at 2:52 PM Daniel Michelson <dmichelson at smith.edu>
wrote:

> Hi Kevin,
>
> I'm sure this isn't much help, but we've also encountered this bug on one
> resource record in 2.7.1.  We could not determine what might have caused it.
>
> Dan
>
> On Mon, Jun 1, 2020 at 2:27 PM Kevin W. Schlottmann <kws2126 at columbia.edu>
> wrote:
>
>> Hi all,
>>
>> We are chasing an odd bug where certain fields are being inadvertently
>> duplicated by AS when some other edit action is taken on the resource
>> record.  The fields being duplicated are language notes, extent notes,
>> and date notes at the resource-level.
>>
>> We are unable to replicate the bug reliably, on any given record, or for
>> a record on a Test server where we see the behavior on Production. We are
>> running 2.7.0, hosted by Lyrasis, with limited customizations.
>>
>> Has anyone come across this or a similar bug?
>>
>> Kevin
>>
>> --
>> 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
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
>
>
> --
> Dan Michelson
> Project Manager Archivist
> Smith College Special Collections
>
> The Special Collections reading room is closed. As of March 18th, all
> Special Collections staff will be working remotely. Smith course support is
> our primary responsibility at this time.
>
> Minimal reference services will be managed remotely by staff. Reference
> inquiries that require access to physical materials will be held in order
> of when they were received and responded to once the campus is reopened.
> Expect a four to six week delay, minimum. There is a moratorium on
> digitization services.
>
> For information about Smith College?s response to Covid-19, please visit
> the college?s official website
> <https://www.smith.edu/student-life/health-wellness/coronavirus>. For
> information about library services during this time, information is
> available on our website
> <https://libraries.smith.edu/library-services-during-covid-19>.
> _______________________________________________
> 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/20200602/acb6150c/attachment.html>

From Lora.Woodford at lyrasis.org  Tue Jun  2 14:41:38 2020
From: Lora.Woodford at lyrasis.org (Lora Woodford)
Date: Tue, 2 Jun 2020 18:41:38 +0000
Subject: [Archivesspace_Users_Group] searching for suppressed records?
Message-ID: <0FE6819C-014F-4B9D-94CC-55DE0BA83FFE@lyrasis.org>

Hi Donnelly,

Sorry for a belated reply, but I thought someone else might get to this one sooner.

As to the first part of the question ? how to find suppressed records ? I can think of three different ways to go about doing this that each have their pros/cons depending on your setup there, the number of repositories you have, the permissions of various users, and your access to and/or level of comfort with the underlying ArchivesSpace database and/or the API.

1) You can get the Staff interface to return a normal looking set of search results for resources with the status of suppressed by slightly altering the existing URL you get when you do the following:

  *   Browse > Resources
  *   Use the left sidebar to filter to Published
  *   Change the ?published? in the URL to ?suppressed?
So, in test.archivesspace.org, I can see all the suppressed records in the YNHSC repository by visiting: http://test.archivesspace.org/staff/resources?filter_term%5B%5D=%7B%22suppressed%22%3A%22true%22%7D

This has two drawbacks as far as I can see.  1) the results will be limited to the current repository to which you are logged in; and 2) actually doing something with the list of results could be somewhat manual and require a lot of clicking.  But, if you are most comfortable in the staff interface and/or only have access to the staff interface, this might be your best approach.

2) Second, you can go a step further and use the API search endpoints to return a full listing of all the resource records with a suppressed status of true.  Assuming the user that you log into the API with has full permissions to view suppressed records across all repositories, this has the added benefit of returning all hits across your entire installation of ArchivesSpace.  Similarly, you could build upon this API call to programmatically do the rest of your request ? export the relevant records and/or delete them ? by writing a script that iterates through the results that you get by this initial search request.  Obviously, the barrier to entry is higher here, but I suspect many of the API knowledgeable folks and/or folks working on the ArchivesSnake library, or, possibly, others who have done exactly this type of task could get you started on your way and/or share their prior work in this area.

A query returning the suppressed records on test.archivesspace.org would look something like this (line breaks added so that it?d be easier to read): http://test.archivesspace.org/staff/api/search?page=1&filter={"query": {"op":"AND", "subqueries":[{"jsonmodel_type":"field_query","field":"primary_type","value":"resource","literal":true},
{"jsonmodel_type":"field_query","field":"suppressed","value":"true","literal":true}],"jsonmodel_type":"boolean_query"},
"jsonmodel_type":"advanced_query"}

Note that search results are paged, so if you have a ton of suppressed records, you?ll have to iterate over many pages of results.  You can set the page_size (equal to or less what the max_page_size is set to in your config.rb) as an additional parameter to your request.

3) Finally, if you have access to your database (ideally a read-only copy of your database when initially testing) you can use something along the lines of the following sequel query to return all resources with a suppressed status of true (or, in the case of the DB, `1`).  This would work across repositories and then, as with option 1 above, you could choose how you wish to proceed with this list from there.

SELECT * FROM resource WHERE suppressed=1;

Hope others chime in with how they?ve tackled similar projects, and happy to follow up if you have other questions.

Best,

Lora

--
Lora J. Woodford
Junior Developer
lora.woodford at lyrasis.org<mailto:lora.woodford at lyrasis.org>
800.999.8558 x4808
Cell: 404.877.8158

[signature_658561908]


From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Walton, Donnelly" <dfwalton at ua.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Tuesday, May 26, 2020 at 1:02 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] searching for suppressed records?








 Hi!

Is there a way to search for suppressed resource records? We have suppressed hundreds for a project. I want to find them, export the data as XML or PDF (maybe both), and delete them.



Thanks,
Donnelly Walton

University of Alabama Libraries Special Collections
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200602/95b862d9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 113751 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200602/95b862d9/attachment.png>

From andrew.morrison at bodleian.ox.ac.uk  Wed Jun  3 03:57:31 2020
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Wed, 3 Jun 2020 08:57:31 +0100
Subject: [Archivesspace_Users_Group] Duplicated fields in resources bug?
In-Reply-To: <CAPB3iyHtXtpA9FUn9HEkntALptBLBr6jgtVkhXPNMy5G2JSMtw@mail.gmail.com>
References: <CAPB3iyHC+cTFfiNFN1dWNzZ_BSLisQfxwM4nzOgrHWn90iFLvg@mail.gmail.com>
 <CAOS_AZkgO34edWRf9VCHmYyH05=doGBCXh07pswyeS-CsP+Fig@mail.gmail.com>
 <CAPB3iyHtXtpA9FUn9HEkntALptBLBr6jgtVkhXPNMy5G2JSMtw@mail.gmail.com>
Message-ID: <ae12df02-58ef-03e2-5f0b-cd2b037b69f7@bodleian.ox.ac.uk>

Something else which are duplicated are ARKs, if you have them turned on:

https://archivesspace.atlassian.net/browse/ANW-1060

But they're generated for you, so could be an unrelated bug.

Andrew.


On 02/06/2020 17:48, Kevin W. Schlottmann wrote:
> Thanks Dan.? I'm glad (I guess?) to hear that it's not unique to our 
> instance.
>
> On Mon, Jun 1, 2020 at 2:52 PM Daniel Michelson <dmichelson at smith.edu 
> <mailto:dmichelson at smith.edu>> wrote:
>
>     Hi Kevin,
>
>     I'm sure this isn't much help, but we've also encountered this bug
>     on one resource record in 2.7.1.? We could not determine what
>     might have caused it.
>
>     Dan
>
>     On Mon, Jun 1, 2020 at 2:27 PM Kevin W. Schlottmann
>     <kws2126 at columbia.edu <mailto:kws2126 at columbia.edu>> wrote:
>
>         Hi all,
>
>         We are chasing an odd bug where certain fields are being
>         inadvertently duplicated by AS when some other edit action is
>         taken on the resource record.? The fields being duplicated are
>         language notes, extent notes, and date notes at the
>         resource-level.
>
>         We are unable to replicate the bug reliably, on any given
>         record, or for a record on a Test server where we see the
>         behavior on Production. We are running 2.7.0, hosted by
>         Lyrasis, with limited customizations.
>
>         Has anyone come across this or a similar bug?
>
>         Kevin
>
>         -- 
>         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
>         _______________________________________________
>         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
>
>
>
>     -- 
>     Dan Michelson
>     Project Manager Archivist
>     Smith College Special Collections
>
>     The Special Collections reading room is closed. As of March 18th,
>     all Special Collections staff will be working remotely. Smith
>     course support is our primary responsibility at this time.
>
>
>     Minimal reference services will be managed remotely by staff.
>     Reference inquiries that require access to physical materials will
>     be held in order of when they were received and responded to once
>     the campus is reopened. Expect a four to six week delay, minimum.
>     There is a moratorium on digitization services.
>
>
>     For information about Smith College?s response to Covid-19, please
>     visit the college?s official website
>     <https://www.smith.edu/student-life/health-wellness/coronavirus>.
>     For information about library services during this time,
>     information is available on our website
>     <https://libraries.smith.edu/library-services-during-covid-19>.
>     _______________________________________________
>     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
>
>
>
> -- 
> 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
>
> _______________________________________________
> 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/20200603/565b89d8/attachment.html>

From kws2126 at columbia.edu  Wed Jun  3 09:44:23 2020
From: kws2126 at columbia.edu (Kevin W. Schlottmann)
Date: Wed, 3 Jun 2020 09:44:23 -0400
Subject: [Archivesspace_Users_Group] Duplicated fields in resources bug?
In-Reply-To: <ae12df02-58ef-03e2-5f0b-cd2b037b69f7@bodleian.ox.ac.uk>
References: <CAPB3iyHC+cTFfiNFN1dWNzZ_BSLisQfxwM4nzOgrHWn90iFLvg@mail.gmail.com>
 <CAOS_AZkgO34edWRf9VCHmYyH05=doGBCXh07pswyeS-CsP+Fig@mail.gmail.com>
 <CAPB3iyHtXtpA9FUn9HEkntALptBLBr6jgtVkhXPNMy5G2JSMtw@mail.gmail.com>
 <ae12df02-58ef-03e2-5f0b-cd2b037b69f7@bodleian.ox.ac.uk>
Message-ID: <CAPB3iyE8hvFbF87Ma3z5-shuWtHiVd5a+Pt0PgkRYrBbN5uY4g@mail.gmail.com>

Thanks Andrew, that could be a useful lead.

On Wed, Jun 3, 2020 at 3:57 AM Andrew Morrison <
andrew.morrison at bodleian.ox.ac.uk> wrote:

> Something else which are duplicated are ARKs, if you have them turned on:
>
> https://archivesspace.atlassian.net/browse/ANW-1060
>
> But they're generated for you, so could be an unrelated bug.
>
> Andrew.
>
>
> On 02/06/2020 17:48, Kevin W. Schlottmann wrote:
>
> Thanks Dan.  I'm glad (I guess?) to hear that it's not unique to our
> instance.
>
> On Mon, Jun 1, 2020 at 2:52 PM Daniel Michelson <dmichelson at smith.edu>
> wrote:
>
>> Hi Kevin,
>>
>> I'm sure this isn't much help, but we've also encountered this bug on one
>> resource record in 2.7.1.  We could not determine what might have caused it.
>>
>> Dan
>>
>> On Mon, Jun 1, 2020 at 2:27 PM Kevin W. Schlottmann <kws2126 at columbia.edu>
>> wrote:
>>
>>> Hi all,
>>>
>>> We are chasing an odd bug where certain fields are being inadvertently
>>> duplicated by AS when some other edit action is taken on the resource
>>> record.  The fields being duplicated are language notes, extent notes,
>>> and date notes at the resource-level.
>>>
>>> We are unable to replicate the bug reliably, on any given record, or for
>>> a record on a Test server where we see the behavior on Production. We are
>>> running 2.7.0, hosted by Lyrasis, with limited customizations.
>>>
>>> Has anyone come across this or a similar bug?
>>>
>>> Kevin
>>>
>>> --
>>> 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
>>> _______________________________________________
>>> Archivesspace_Users_Group mailing list
>>> Archivesspace_Users_Group at lyralists.lyrasis.org
>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>>
>>
>>
>> --
>> Dan Michelson
>> Project Manager Archivist
>> Smith College Special Collections
>>
>> The Special Collections reading room is closed. As of March 18th, all
>> Special Collections staff will be working remotely. Smith course support is
>> our primary responsibility at this time.
>>
>> Minimal reference services will be managed remotely by staff. Reference
>> inquiries that require access to physical materials will be held in order
>> of when they were received and responded to once the campus is reopened.
>> Expect a four to six week delay, minimum. There is a moratorium on
>> digitization services.
>>
>> For information about Smith College?s response to Covid-19, please visit
>> the college?s official website
>> <https://www.smith.edu/student-life/health-wellness/coronavirus>. For
>> information about library services during this time, information is
>> available on our website
>> <https://libraries.smith.edu/library-services-during-covid-19>.
>> _______________________________________________
>> 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
>
> _______________________________________________
> Archivesspace_Users_Group mailing listArchivesspace_Users_Group at lyralists.lyrasis.orghttp://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
> _______________________________________________
> 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/20200603/8b1e0def/attachment.html>

From andrew.morrison at bodleian.ox.ac.uk  Wed Jun  3 14:16:04 2020
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Wed, 3 Jun 2020 19:16:04 +0100
Subject: [Archivesspace_Users_Group] Blank collection organization view for
	all resources
Message-ID: <2e851659-222f-51b5-6f7e-c80fe51e716d@bodleian.ox.ac.uk>

Hello,

Has anyone encountered a problem with the collection organization view 
not displaying any of the contents of the collection? All the resource 
records in our system are affected, but here is one example:

https://archives.bodleian.ox.ac.uk/repositories/2/resources/4976/collection_organization

The child archival objects are listed in the sidebar. Their IDs are 
embedded in data-uris attributes in div elements waiting to be 
populated, the JavaScript to fetch them is running, but the HTTP 
requests to retrieve JSON containing snippets of HTML are returning 500 
internal server errors. The application log reports a NoMethodError each 
time, seemingly due to nil objects being passed to one of the Rails 
libraries:

F, [2020-06-03T08:47:23.813482 #1315] FATAL -- : [4251522f-7cdc-4744-a371-5865d02d5124]
F, [2020-06-03T08:47:23.815452 #1315] FATAL -- : [4251522f-7cdc-4744-a371-5865d02d5124] NoMethodError (undefined method `+' for nil:NilClass):
F, [2020-06-03T08:47:23.815548 #1315] FATAL -- : [4251522f-7cdc-4744-a371-5865d02d5124]
F, [2020-06-03T08:47:23.815644 #1315] FATAL -- : [4251522f-7cdc-4744-a371-5865d02d5124] actionpack (5.0.1) lib/action_dispatch/journey/path/pattern.rb:131:in `[]'
[4251522f-7cdc-4744-a371-5865d02d5124] actionpack (5.0.1) lib/action_dispatch/journey/path/pattern.rb:127:in `block in captures'
[4251522f-7cdc-4744-a371-5865d02d5124] org/jruby/RubyArray.java:638:in `initialize'
[4251522f-7cdc-4744-a371-5865d02d5124] actionpack (5.0.1) lib/action_dispatch/journey/path/pattern.rb:127:in `captures'
[4251522f-7cdc-4744-a371-5865d02d5124] actionpack (5.0.1) lib/action_dispatch/journey/router.rb:114:in `block in find_routes'

But I cannot figure out why this might be happening.

It only started since a server reboot following an operating system 
update. But we have an identically-configured QA testing system which 
received the same update and does not have this problem. Nothing seems 
to be missing or on a different version when comparing the two systems.

Does anyone have any suggestions?

Thanks,

Andrew.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200603/6023b1a9/attachment.html>

From baileys at ou.edu  Thu Jun  4 11:37:10 2020
From: baileys at ou.edu (Hoffner, Bailey E.)
Date: Thu, 4 Jun 2020 15:37:10 +0000
Subject: [Archivesspace_Users_Group] PDF Export Logo Issue
Message-ID: <CE21DF14-A368-4667-91F5-CF8A1E8EC4C6@ou.edu>

Morning All,

We have an odd issue where our branding image does not show up on the PDF that can be exported from the public interface, but it does show up on the PDF that can be exported from the staff interface. The ArchivesSpace logo no longer shows up, but neither does the branding image.

Any suggestions? Has anyone had an issue like this before?

Thanks!

-Bailey

Bailey Hoffner, MLIS
Metadata and Collections Management Archivist
University of Oklahoma Libraries
405-325-1566

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200604/a4a3f1b9/attachment.html>

From crumins at clemson.edu  Thu Jun  4 15:42:31 2020
From: crumins at clemson.edu (Clayton Joseph Ruminski)
Date: Thu, 4 Jun 2020 19:42:31 +0000
Subject: [Archivesspace_Users_Group] Error deleting agents
Message-ID: <MN2PR06MB56784661B08EE89BF4E355CAA8890@MN2PR06MB5678.namprd06.prod.outlook.com>

Hello,

We are doing some data cleanup in ASpace, and one agent in particular is giving me the following error when trying to delete it:

Record deletion failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLIntegrityConstraintViolationException: Cannot delete or update a parent row: a foreign key constraint fails (`archivesspace`.`user`, CONSTRAINT `user_ibfk_1` FOREIGN KEY (`agent_record_id`) REFERENCES `agent_person` (`id`))

I looked on the user group archives but was unable to find an answer. The agent looks to have been autogenerated at some point and is not linked to any records.

Thanks!

Clayton Ruminski CLEMSON UNIVERSITY

Digital and Preservation Archivist
Special Collections and Archives
Clemson University Libraries
crumins at clemson.edu<mailto:crumins at clemson.edu>
864-656-0234

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200604/5e0ccdac/attachment.html>

From blake.carver at lyrasis.org  Thu Jun  4 15:46:00 2020
From: blake.carver at lyrasis.org (Blake Carver)
Date: Thu, 4 Jun 2020 19:46:00 +0000
Subject: [Archivesspace_Users_Group] Error deleting agents
In-Reply-To: <MN2PR06MB56784661B08EE89BF4E355CAA8890@MN2PR06MB5678.namprd06.prod.outlook.com>
References: <MN2PR06MB56784661B08EE89BF4E355CAA8890@MN2PR06MB5678.namprd06.prod.outlook.com>
Message-ID: <DM6PR22MB230934175297A8286272CA5B9F890@DM6PR22MB2309.namprd22.prod.outlook.com>

We've seen that happen when a user is also an agent.  Probably there's an agent (person) record linked to that user account so the account cannot be deleted. You can delete the agent record first, then the user -- that should work. Careful, sometimes you need that agent record. In that case I'd suggest disabling the account by resetting the password to something long and random so the account cannot be used (and perhaps add "DISABLED" to "Additional Contact Information" as a note).
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Clayton Joseph Ruminski <crumins at clemson.edu>
Sent: Thursday, June 4, 2020 3:42 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Error deleting agents


Hello,



We are doing some data cleanup in ASpace, and one agent in particular is giving me the following error when trying to delete it:



Record deletion failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLIntegrityConstraintViolationException: Cannot delete or update a parent row: a foreign key constraint fails (`archivesspace`.`user`, CONSTRAINT `user_ibfk_1` FOREIGN KEY (`agent_record_id`) REFERENCES `agent_person` (`id`))



I looked on the user group archives but was unable to find an answer. The agent looks to have been autogenerated at some point and is not linked to any records.



Thanks!



Clayton Ruminski CLEMSON UNIVERSITY



Digital and Preservation Archivist

Special Collections and Archives

Clemson University Libraries

crumins at clemson.edu<mailto:crumins at clemson.edu>

864-656-0234


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200604/0e5607c9/attachment.html>

From mayoc at bc.edu  Fri Jun  5 10:02:29 2020
From: mayoc at bc.edu (Chris Mayo)
Date: Fri, 5 Jun 2020 10:02:29 -0400
Subject: [Archivesspace_Users_Group] PDF Export Logo Issue
In-Reply-To: <CE21DF14-A368-4667-91F5-CF8A1E8EC4C6@ou.edu>
References: <CE21DF14-A368-4667-91F5-CF8A1E8EC4C6@ou.edu>
Message-ID: <CAHPoN43nu2-4ekdEDQ=Nj6njd-4VC+6QwUUwCLMWVMsP74ZQ7g@mail.gmail.com>

Hi Bailey,

My institution doesn't use the PUI, so I can't really speculate about why
there's a difference between the staff and public interfaces. That being
said, the appearance of the PDFs are controlled by the as-ead-pdf.xsl
stylesheet, and I've noticed in the past that it's really easy for the
logos to break for a number of reasons:

   - if the logo file gets renamed or goes missing during a software update
   - if you're modifying the stylesheet for other reasons and accidentally
   comment out, delete, or modify the part that calls for the logo file

I don't know if either of those is the case in your application, but I'd
start with looking at the stylesheet and logo files and making sure they're
all cross-referencing properly.

Best,
Chris

On Thu, Jun 4, 2020 at 11:37 AM Hoffner, Bailey E. <baileys at ou.edu> wrote:

> Morning All,
>
>
>
> We have an odd issue where our branding image does not show up on the PDF
> that can be exported from the public interface, but it does show up on the
> PDF that can be exported from the staff interface. The ArchivesSpace logo
> no longer shows up, but neither does the branding image.
>
>
>
> Any suggestions? Has anyone had an issue like this before?
>
>
>
> Thanks!
>
>
>
> -Bailey
>
>
>
> Bailey Hoffner, MLIS
>
> Metadata and Collections Management Archivist
>
> University of Oklahoma Libraries
>
> 405-325-1566
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Chris Mayo
Digital Production Librarian
Boston College
chris.mayo at bc.edu
pronouns: they/them/theirs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200605/e10c2b35/attachment.html>

From sdm7g at virginia.edu  Fri Jun  5 10:58:02 2020
From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Fri, 5 Jun 2020 14:58:02 +0000
Subject: [Archivesspace_Users_Group] PDF Export Logo Issue
In-Reply-To: <CAHPoN43nu2-4ekdEDQ=Nj6njd-4VC+6QwUUwCLMWVMsP74ZQ7g@mail.gmail.com>
References: <CE21DF14-A368-4667-91F5-CF8A1E8EC4C6@ou.edu>,
 <CAHPoN43nu2-4ekdEDQ=Nj6njd-4VC+6QwUUwCLMWVMsP74ZQ7g@mail.gmail.com>
Message-ID: <EF17B597-1E2F-4384-8A06-84CE2248C229@virginia.edu>

That style sheet is only used in the staff PDF export.
The PUI PDF is generated differently.


Sent from my iPad

On Jun 5, 2020, at 10:02 AM, Chris Mayo <mayoc at bc.edu> wrote:

?
Hi Bailey,

My institution doesn't use the PUI, so I can't really speculate about why there's a difference between the staff and public interfaces. That being said, the appearance of the PDFs are controlled by the as-ead-pdf.xsl stylesheet, and I've noticed in the past that it's really easy for the logos to break for a number of reasons:

  *   if the logo file gets renamed or goes missing during a software update
  *   if you're modifying the stylesheet for other reasons and accidentally comment out, delete, or modify the part that calls for the logo file

I don't know if either of those is the case in your application, but I'd start with looking at the stylesheet and logo files and making sure they're all cross-referencing properly.

Best,
Chris

On Thu, Jun 4, 2020 at 11:37 AM Hoffner, Bailey E. <baileys at ou.edu<mailto:baileys at ou.edu>> wrote:
Morning All,

We have an odd issue where our branding image does not show up on the PDF that can be exported from the public interface, but it does show up on the PDF that can be exported from the staff interface. The ArchivesSpace logo no longer shows up, but neither does the branding image.

Any suggestions? Has anyone had an issue like this before?

Thanks!

-Bailey

Bailey Hoffner, MLIS
Metadata and Collections Management Archivist
University of Oklahoma Libraries
405-325-1566

_______________________________________________
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


--
Chris Mayo
Digital Production Librarian
Boston College
chris.mayo at bc.edu<mailto:chris.mayo at bc.edu>
pronouns: they/them/theirs
_______________________________________________
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/20200605/aaed0a2a/attachment.html>

From blake.carver at lyrasis.org  Fri Jun  5 11:44:58 2020
From: blake.carver at lyrasis.org (Blake Carver)
Date: Fri, 5 Jun 2020 15:44:58 +0000
Subject: [Archivesspace_Users_Group] PDF Export Logo Issue
In-Reply-To: <EF17B597-1E2F-4384-8A06-84CE2248C229@virginia.edu>
References: <CE21DF14-A368-4667-91F5-CF8A1E8EC4C6@ou.edu>,
 <CAHPoN43nu2-4ekdEDQ=Nj6njd-4VC+6QwUUwCLMWVMsP74ZQ7g@mail.gmail.com>,
 <EF17B597-1E2F-4384-8A06-84CE2248C229@virginia.edu>
Message-ID: <DM6PR22MB2309F60919467F971C4E9B409F860@DM6PR22MB2309.namprd22.prod.outlook.com>


I was just typing out a reply to say the same thing, here's a PR that gives you a decent idea of some of the files that are used on the PUI side PDF
https://github.com/archivesspace/archivesspace/pull/1480
It's not an area that you want to mess with, usually.
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Majewski, Steven Dennis (sdm7g) <sdm7g at virginia.edu>
Sent: Friday, June 5, 2020 10:58 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] PDF Export Logo Issue

That style sheet is only used in the staff PDF export.
The PUI PDF is generated differently.


Sent from my iPad

On Jun 5, 2020, at 10:02 AM, Chris Mayo <mayoc at bc.edu> wrote:

?
Hi Bailey,

My institution doesn't use the PUI, so I can't really speculate about why there's a difference between the staff and public interfaces. That being said, the appearance of the PDFs are controlled by the as-ead-pdf.xsl stylesheet, and I've noticed in the past that it's really easy for the logos to break for a number of reasons:

  *   if the logo file gets renamed or goes missing during a software update
  *   if you're modifying the stylesheet for other reasons and accidentally comment out, delete, or modify the part that calls for the logo file

I don't know if either of those is the case in your application, but I'd start with looking at the stylesheet and logo files and making sure they're all cross-referencing properly.

Best,
Chris

On Thu, Jun 4, 2020 at 11:37 AM Hoffner, Bailey E. <baileys at ou.edu<mailto:baileys at ou.edu>> wrote:

Morning All,



We have an odd issue where our branding image does not show up on the PDF that can be exported from the public interface, but it does show up on the PDF that can be exported from the staff interface. The ArchivesSpace logo no longer shows up, but neither does the branding image.



Any suggestions? Has anyone had an issue like this before?



Thanks!



-Bailey



Bailey Hoffner, MLIS

Metadata and Collections Management Archivist

University of Oklahoma Libraries

405-325-1566



_______________________________________________
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


--
Chris Mayo
Digital Production Librarian
Boston College
chris.mayo at bc.edu<mailto:chris.mayo at bc.edu>
pronouns: they/them/theirs
_______________________________________________
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/20200605/76f10729/attachment.html>

From andrew.morrison at bodleian.ox.ac.uk  Fri Jun  5 13:28:17 2020
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Fri, 5 Jun 2020 18:28:17 +0100
Subject: [Archivesspace_Users_Group] PDF Export Logo Issue
In-Reply-To: <DM6PR22MB2309F60919467F971C4E9B409F860@DM6PR22MB2309.namprd22.prod.outlook.com>
References: <CE21DF14-A368-4667-91F5-CF8A1E8EC4C6@ou.edu>
 <CAHPoN43nu2-4ekdEDQ=Nj6njd-4VC+6QwUUwCLMWVMsP74ZQ7g@mail.gmail.com>
 <EF17B597-1E2F-4384-8A06-84CE2248C229@virginia.edu>
 <DM6PR22MB2309F60919467F971C4E9B409F860@DM6PR22MB2309.namprd22.prod.outlook.com>
Message-ID: <1a34fc22-f639-3bdb-3109-e540d67df174@bodleian.ox.ac.uk>

Anything that involves the backend, or XSL, is the code for the PDFs you 
get in the staff interface.


The public user interface generates its own PDFs, by first building a 
HTML document using ERB templates, just as it does for ordinary pages. 
But instead of returning that it stores it as a temporary HTML file, 
then converts that to a PDF file using a Java library 
<https://github.com/flyingsaucerproject/flyingsaucer>. Then it sends the 
PDF file to the user.


The logo is an /img/ tag with the /src/ attribute using the branding 
image URL set for the repository of the resource. The HTML-to-PDF 
library is effectively like a web browser running on the server, viewing 
a local file, so it needs a full URL, not a path relative to the server 
root. Or, if the image is hosted on another server, then there must be 
nothing to block the outgoing HTTP request or returned response. Ask you 
local network admins if unsure. It doesn't cache the image, so every 
time a user requests a PDF, the ArchivesSpace server will download the 
image from wherever you specify.


The image must be in a format supported by the HTML-to-PDF library, but 
I can't find a list. Standard PNGs work.


Because it uses templates, you can override the relevant file 
(_titlepage.html.erb) in a plug-in, and make it display whatever you 
want (such as the logo for your whole organization, if you don't want 
PDFs branded differently per repository, or no logo at all if you just 
want text.) But it also contains code to add the other things on the 
first page, so if you override it you might have to update it when 
upgrading to a future release.


Andrew.



On 05/06/2020 16:44, Blake Carver wrote:
>
> I was just typing out a reply to say the same thing, here's a PR that 
> gives you a decent idea of some of the files that are used on the PUI 
> side PDF
> https://github.com/archivesspace/archivesspace/pull/1480
> It's not an area that you want to mess with, usually.
> ------------------------------------------------------------------------
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org 
> <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of 
> Majewski, Steven Dennis (sdm7g) <sdm7g at virginia.edu>
> *Sent:* Friday, June 5, 2020 10:58 AM
> *To:* Archivesspace Users Group 
> <archivesspace_users_group at lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] PDF Export Logo Issue
> That style sheet is only used in the staff PDF export.
> The PUI PDF is generated differently.
>
>
> Sent from my iPad
>
>> On Jun 5, 2020, at 10:02 AM, Chris Mayo <mayoc at bc.edu> wrote:
>>
>> ?
>> Hi Bailey,
>>
>> My institution doesn't use the PUI, so I can't really speculate about 
>> why there's a difference between the staff and public interfaces. 
>> That being said, the appearance of the PDFs are controlled by the 
>> as-ead-pdf.xsl stylesheet, and I've noticed in the past that it's 
>> really easy for the logos to break for a number of reasons:
>>
>>   * if the logo file gets renamed or goes missing during a software
>>     update
>>   * if you're modifying the stylesheet for other reasons and
>>     accidentally comment out, delete, or modify the part that calls
>>     for the logo file
>>
>> I don't know if either of those is the case in your application, but 
>> I'd start with looking at the stylesheet and logo files and making 
>> sure they're all cross-referencing properly.
>>
>> Best,
>> Chris
>>
>> On Thu, Jun 4, 2020 at 11:37 AM Hoffner, Bailey E. <baileys at ou.edu 
>> <mailto:baileys at ou.edu>> wrote:
>>
>>     Morning All,
>>
>>     We have an odd issue where our branding image does not show up on
>>     the PDF that can be exported from the public interface, but it
>>     does show up on the PDF that can be exported from the staff
>>     interface. The ArchivesSpace logo no longer shows up, but neither
>>     does the branding image.
>>
>>     Any suggestions? Has anyone had an issue like this before?
>>
>>     Thanks!
>>
>>     -Bailey
>>
>>     Bailey Hoffner, MLIS
>>
>>     Metadata and Collections Management Archivist
>>
>>     University of Oklahoma Libraries
>>
>>     405-325-1566
>>
>>     _______________________________________________
>>     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
>>
>>
>>
>> -- 
>> Chris Mayo
>> Digital Production Librarian
>> Boston College
>> chris.mayo at bc.edu <mailto:chris.mayo at bc.edu>
>> pronouns: they/them/theirs
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
> _______________________________________________
> 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/20200605/ccce08b8/attachment.html>

From bobbi at bobbifox.net  Fri Jun  5 13:32:32 2020
From: bobbi at bobbifox.net (Bobbi Fox)
Date: Fri, 5 Jun 2020 13:32:32 -0400 (EDT)
Subject: [Archivesspace_Users_Group] Using ArchivesSpace for Records
	Management?
Message-ID: <alpine.BSF.2.20.16.2006051330410.64687@siur.pair.com>

Hi,

Is anyone using ArchivesSpace for Records Management, including, of 
course, retention dates/periods, reporting of same, and deletion once past 
the retention date (plus everything else this software developer doesn't 
know about records detention)?

You can respond to me privately, if you like.

Thanks,


--
Bobbi Fox  bobbi at bobbifox.net


From andrew.morrison at bodleian.ox.ac.uk  Fri Jun  5 13:52:46 2020
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Fri, 5 Jun 2020 18:52:46 +0100
Subject: [Archivesspace_Users_Group] Blank collection organization view
 for all resources
In-Reply-To: <2e851659-222f-51b5-6f7e-c80fe51e716d@bodleian.ox.ac.uk>
References: <2e851659-222f-51b5-6f7e-c80fe51e716d@bodleian.ox.ac.uk>
Message-ID: <4c74f78d-96b1-48cd-4580-d746d16a3732@bodleian.ox.ac.uk>

If anyone has this problem in the future, a restart of the ArchivesSpace 
application seems to restore the collection organization view. If this 
issue is related...

https://github.com/rails/rails/issues/33026

...then it may be fixable by updating to a newer version of Rails. But 
we've only had one occurrence in countless restarts, so it isn't a huge 
priority.

Andrew.


On 03/06/2020 19:16, Andrew Morrison wrote:
>
> Hello,
>
> Has anyone encountered a problem with the collection organization view 
> not displaying any of the contents of the collection? All the resource 
> records in our system are affected, but here is one example:
>
> https://archives.bodleian.ox.ac.uk/repositories/2/resources/4976/collection_organization
>
> The child archival objects are listed in the sidebar. Their IDs are 
> embedded in data-uris attributes in div elements waiting to be 
> populated, the JavaScript to fetch them is running, but the HTTP 
> requests to retrieve JSON containing snippets of HTML are returning 
> 500 internal server errors. The application log reports a 
> NoMethodError each time, seemingly due to nil objects being passed to 
> one of the Rails libraries:
>
> F, [2020-06-03T08:47:23.813482 #1315] FATAL -- : [4251522f-7cdc-4744-a371-5865d02d5124]
> F, [2020-06-03T08:47:23.815452 #1315] FATAL -- : [4251522f-7cdc-4744-a371-5865d02d5124] NoMethodError (undefined method `+' for nil:NilClass):
> F, [2020-06-03T08:47:23.815548 #1315] FATAL -- : [4251522f-7cdc-4744-a371-5865d02d5124]
> F, [2020-06-03T08:47:23.815644 #1315] FATAL -- : [4251522f-7cdc-4744-a371-5865d02d5124] actionpack (5.0.1) lib/action_dispatch/journey/path/pattern.rb:131:in `[]'
> [4251522f-7cdc-4744-a371-5865d02d5124] actionpack (5.0.1) lib/action_dispatch/journey/path/pattern.rb:127:in `block in captures'
> [4251522f-7cdc-4744-a371-5865d02d5124] org/jruby/RubyArray.java:638:in `initialize'
> [4251522f-7cdc-4744-a371-5865d02d5124] actionpack (5.0.1) lib/action_dispatch/journey/path/pattern.rb:127:in `captures'
> [4251522f-7cdc-4744-a371-5865d02d5124] actionpack (5.0.1) lib/action_dispatch/journey/router.rb:114:in `block in find_routes'
>
> But I cannot figure out why this might be happening.
>
> It only started since a server reboot following an operating system 
> update. But we have an identically-configured QA testing system which 
> received the same update and does not have this problem. Nothing seems 
> to be missing or on a different version when comparing the two systems.
>
> Does anyone have any suggestions?
>
> Thanks,
>
> Andrew.
>
>
>
> _______________________________________________
> 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/20200605/3292bf1b/attachment.html>

From andrew.morrison at bodleian.ox.ac.uk  Fri Jun  5 14:56:06 2020
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Fri, 5 Jun 2020 19:56:06 +0100
Subject: [Archivesspace_Users_Group] PDF Export Logo Issue
In-Reply-To: <1a34fc22-f639-3bdb-3109-e540d67df174@bodleian.ox.ac.uk>
References: <CE21DF14-A368-4667-91F5-CF8A1E8EC4C6@ou.edu>
 <CAHPoN43nu2-4ekdEDQ=Nj6njd-4VC+6QwUUwCLMWVMsP74ZQ7g@mail.gmail.com>
 <EF17B597-1E2F-4384-8A06-84CE2248C229@virginia.edu>
 <DM6PR22MB2309F60919467F971C4E9B409F860@DM6PR22MB2309.namprd22.prod.outlook.com>
 <1a34fc22-f639-3bdb-3109-e540d67df174@bodleian.ox.ac.uk>
Message-ID: <1949b02a-7234-56f8-b5bd-36db826fe48d@bodleian.ox.ac.uk>

You also need to trigger a re-index after you change the branding image 
URL. That is because when generating PDFs the PUI uses a copy of the URL 
included in every resource, along with other repository information, at 
index time.


SVGs don't work. PNGs and JPEGs do.


Andrew.



On 05/06/2020 18:28, Andrew Morrison wrote:
>
> Anything that involves the backend, or XSL, is the code for the PDFs 
> you get in the staff interface.
>
>
> The public user interface generates its own PDFs, by first building a 
> HTML document using ERB templates, just as it does for ordinary pages. 
> But instead of returning that it stores it as a temporary HTML file, 
> then converts that to a PDF file using a Java library 
> <https://github.com/flyingsaucerproject/flyingsaucer>. Then it sends 
> the PDF file to the user.
>
>
> The logo is an /img/ tag with the /src/ attribute using the branding 
> image URL set for the repository of the resource. The HTML-to-PDF 
> library is effectively like a web browser running on the server, 
> viewing a local file, so it needs a full URL, not a path relative to 
> the server root. Or, if the image is hosted on another server, then 
> there must be nothing to block the outgoing HTTP request or returned 
> response. Ask you local network admins if unsure. It doesn't cache the 
> image, so every time a user requests a PDF, the ArchivesSpace server 
> will download the image from wherever you specify.
>
>
> The image must be in a format supported by the HTML-to-PDF library, 
> but I can't find a list. Standard PNGs work.
>
>
> Because it uses templates, you can override the relevant file 
> (_titlepage.html.erb) in a plug-in, and make it display whatever you 
> want (such as the logo for your whole organization, if you don't want 
> PDFs branded differently per repository, or no logo at all if you just 
> want text.) But it also contains code to add the other things on the 
> first page, so if you override it you might have to update it when 
> upgrading to a future release.
>
>
> Andrew.
>
>
>
> On 05/06/2020 16:44, Blake Carver wrote:
>>
>> I was just typing out a reply to say the same thing, here's a PR that 
>> gives you a decent idea of some of the files that are used on the PUI 
>> side PDF
>> https://github.com/archivesspace/archivesspace/pull/1480
>> It's not an area that you want to mess with, usually.
>> ------------------------------------------------------------------------
>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org 
>> <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf 
>> of Majewski, Steven Dennis (sdm7g) <sdm7g at virginia.edu>
>> *Sent:* Friday, June 5, 2020 10:58 AM
>> *To:* Archivesspace Users Group 
>> <archivesspace_users_group at lyralists.lyrasis.org>
>> *Subject:* Re: [Archivesspace_Users_Group] PDF Export Logo Issue
>> That style sheet is only used in the staff PDF export.
>> The PUI PDF is generated differently.
>>
>>
>> Sent from my iPad
>>
>>> On Jun 5, 2020, at 10:02 AM, Chris Mayo <mayoc at bc.edu> wrote:
>>>
>>> ?
>>> Hi Bailey,
>>>
>>> My institution doesn't use the PUI, so I can't really speculate 
>>> about why there's a difference between the staff and public 
>>> interfaces. That being said, the appearance of the PDFs are 
>>> controlled by the as-ead-pdf.xsl stylesheet, and I've noticed in the 
>>> past that it's really easy for the logos to break for a number of 
>>> reasons:
>>>
>>>   * if the logo file gets renamed or goes missing during a software
>>>     update
>>>   * if you're modifying the stylesheet for other reasons and
>>>     accidentally comment out, delete, or modify the part that calls
>>>     for the logo file
>>>
>>> I don't know if either of those is the case in your application, but 
>>> I'd start with looking at the stylesheet and logo files and making 
>>> sure they're all cross-referencing properly.
>>>
>>> Best,
>>> Chris
>>>
>>> On Thu, Jun 4, 2020 at 11:37 AM Hoffner, Bailey E. <baileys at ou.edu 
>>> <mailto:baileys at ou.edu>> wrote:
>>>
>>>     Morning All,
>>>
>>>     We have an odd issue where our branding image does not show up
>>>     on the PDF that can be exported from the public interface, but
>>>     it does show up on the PDF that can be exported from the staff
>>>     interface. The ArchivesSpace logo no longer shows up, but
>>>     neither does the branding image.
>>>
>>>     Any suggestions? Has anyone had an issue like this before?
>>>
>>>     Thanks!
>>>
>>>     -Bailey
>>>
>>>     Bailey Hoffner, MLIS
>>>
>>>     Metadata and Collections Management Archivist
>>>
>>>     University of Oklahoma Libraries
>>>
>>>     405-325-1566
>>>
>>>     _______________________________________________
>>>     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
>>>
>>>
>>>
>>> -- 
>>> Chris Mayo
>>> Digital Production Librarian
>>> Boston College
>>> chris.mayo at bc.edu <mailto:chris.mayo at bc.edu>
>>> pronouns: they/them/theirs
>>> _______________________________________________
>>> Archivesspace_Users_Group mailing list
>>> Archivesspace_Users_Group at lyralists.lyrasis.org
>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
> _______________________________________________
> 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/20200605/d11de561/attachment.html>

From christine.dibella at lyrasis.org  Fri Jun  5 17:40:41 2020
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Fri, 5 Jun 2020 21:40:41 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace at this time, some ideas,
	and upcoming open call
Message-ID: <MN2PR22MB18875BCA35B8F57EC614F3F7F1860@MN2PR22MB1887.namprd22.prod.outlook.com>

Hello ArchivesSpace people,



Like so many in our community we've been wanting to reach out this week and struggling to find a way to do so that's meaningful, at a time when violence against people of color and many of the structures that perpetuate it have been especially laid bare. We've been thinking about the good that archives do, all the while mindful that archives and software applications are not neutral, and are themselves capable of perpetuating structures that harm or silence. We've been thinking about the part that ArchivesSpace can play in making progress in these often disheartening times.


We've been specifically thinking of ways ArchivesSpace can support and amplify those that document and empower individuals, organizations and communities that work to make the world a more inclusive place. We've also been thinking about how ArchivesSpace itself can be more inclusive. We've come up with a few ideas so far like subsidizing memberships and deployments for some community archives, tribal archives, and grassroots organizations; convening a working group to examine unconscious bias and barriers to entry in the ArchivesSpace application; and working with organizations and groups that help others understand ethical collecting and archival description to identify best practices for using (or not using) ArchivesSpace. We've started a running list for discussion at https://docs.google.com/document/d/1b-GlCSObflqZufIiN4dJ__hlppwPloHXzytsUEVlZp4/edit?usp=sharing.


What we want most is to hear your ideas. We're going to devote our next open call on June 24 to these issues, and we also want to consider ways we can incorporate them more organically into our ongoing programming and our users' experience of ArchivesSpace. Please come with your thoughts, questions, and suggestions. And please reach out to us at any time. We welcome your participation in any form.


We're so proud that the ArchivesSpace community reflects many different kinds of archives, serving many different communities. We're so proud that our members range from entirely volunteer-run non-profit organizations to some of the largest academic archives in the world. We truly appreciate the many different viewpoints represented by the collections people manage in ArchivesSpace, and the many different viewpoints of the people who manage these collections in ArchivesSpace. We believe our community can become even richer by drawing in more viewpoints.


We're also mindful that many of us have been pushed to or past our limits already, not only by the events of recent months but also by the different challenges we each face even in the best of times. We recognize that none of us carries the same load, but that some of us go through life with one that is heavier than others. While we have no delusions about the role of an archival information management system in the grand scheme of things, in the end we hope to in some small way contribute to making those loads lighter, not heavier.


Thank you for the part you play in that and for being with us at this incredibly challenging time. We wish you health, safety, and solace as, like us, you grapple with how best to navigate this world with those you love and make it better.


All best,

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200605/5b02bb72/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200605/5b02bb72/attachment.jpg>

From alancaster at cals.org  Mon Jun  8 12:00:28 2020
From: alancaster at cals.org (Anna Lancaster)
Date: Mon, 8 Jun 2020 16:00:28 +0000
Subject: [Archivesspace_Users_Group] Unfindable resources
Message-ID: <AC203DB6-DC80-4605-B562-2430419CEA72@cals.org>

Hello,
I?m hoping I?ve overlooked something basic, but I?ve run into a dead end with this problem. 
 
Original Problem.
Not able to find recently created Resource records.  Through search or browse.  I can get to the resources through linked accession records so they are saved but not listing in browse nor are they showing up in a search..

Theory 1
First theory was that we needed to reindex.  I asked our IT department to delete the sole_index and Indexer_state files and restart ArchiveSpace.  They did that and when I logged in there were no records in the database.  We restored from back up.

Theory 2
In the meantime I have discovered that it is not just recently created Resource records that are not findable.  Any thing recently created is not findable, accessions, containers, or subjects.  Any modifications to older resources is are saved, but the resource record is not recording that the modification happened.  In other words.  The last modification date does not take into account recent modifications even though the modifications have been saved.  Which makes me think this is a problem with timestamps for when records are created or modified and I really don?t know where to go from there.

If it is a reindexing problem I need to know what I did wrong in trying to reindex.  If it is a timestamp creation problem?I?m not sure where to start.

Anna

Anna Lancaster
Roberts Library
Central Arkansas Library System

From bobbi at bobbifox.net  Mon Jun  8 12:08:29 2020
From: bobbi at bobbifox.net (Bobbi Fox)
Date: Mon, 8 Jun 2020 12:08:29 -0400 (EDT)
Subject: [Archivesspace_Users_Group] Unfindable resources
In-Reply-To: <AC203DB6-DC80-4605-B562-2430419CEA72@cals.org>
References: <AC203DB6-DC80-4605-B562-2430419CEA72@cals.org>
Message-ID: <alpine.BSF.2.20.16.2006081206050.64336@siur.pair.com>

It might be worth looking at the indexing logs.  When I was at Harvard, we 
noticed that sometimes the indexer would hit a error, then just restart 
(hitting the same error, restarting, shampoo, rinse, repeat).  This means 
that anything that needed to be indexed past the point of the error didn't 
get indexed.

Hope this helps.


On Mon, 8 Jun 2020, Anna Lancaster wrote:

> Hello,
> I?m hoping I?ve overlooked something basic, but I?ve run into a dead end with this problem.
>
> Original Problem.
> Not able to find recently created Resource records.  Through search or browse.  I can get to the resources through linked accession records so they are saved but not listing in browse nor are they showing up in a search..
>
> Theory 1
> First theory was that we needed to reindex.  I asked our IT department to delete the sole_index and Indexer_state files and restart ArchiveSpace.  They did that and when I logged in there were no records in the database.  We restored from back up.
>
> Theory 2
> In the meantime I have discovered that it is not just recently created Resource records that are not findable.  Any thing recently created is not findable, accessions, containers, or subjects.  Any modifications to older resources is are saved, but the resource record is not recording that the modification happened.  In other words.  The last modification date does not take into account recent modifications even though the modifications have been saved.  Which makes me think this is a problem with timestamps for when records are created or modified and I really don?t know where to go from there.
>
> If it is a reindexing problem I need to know what I did wrong in trying to reindex.  If it is a timestamp creation problem?I?m not sure where to start.
>
> Anna
>
> Anna Lancaster
> Roberts Library
> Central Arkansas Library System
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

--
Bobbi Fox  bobbi at bobbifox.net
Database-driven and Web-enabled applications development
http://www.bobbifox.net

From ldedeyan at mikekelleyfoundation.org  Tue Jun  9 11:56:41 2020
From: ldedeyan at mikekelleyfoundation.org (Lori Dedeyan)
Date: Tue, 9 Jun 2020 08:56:41 -0700
Subject: [Archivesspace_Users_Group] Using request button in PUI
Message-ID: <CANa8_0594xhomWs=78enfTuv2_wEzR901YvoJrRWwcwgO+uMwQ@mail.gmail.com>

Hi all,

I work for a small repository that doesn?t use request management software
like Aeon. We'd like to begin using the Request button in the ArchivesSpace
PUI to receive and manage user requests.  Would anyone who is currently
using it be willing to share their internal workflows and any instructions
they?ve created for users? We?re also interested in any capacity to
generate information for reporting purposes.

Any information would be much appreciated. Please feel free to respond
privately, if you?d prefer.

Best,
Lori
-- 
Lori Dedeyan
ldedeyan at mikekelleyfoundation.org

Mike Kelley Foundation for the Arts
7019 N. Figueroa Street
Los Angeles, CA  90042
www.mikekelleyfoundation.org

*Please note that our entire team is working remotely while we monitor the
COVID-19 situation, which impacts access to our office lines and postal
service. Thank you for your patience and understanding. *
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200609/4e448a0d/attachment.html>

From emtanner at ualr.edu  Tue Jun  9 14:35:42 2020
From: emtanner at ualr.edu (Elise Tanner)
Date: Tue, 9 Jun 2020 13:35:42 -0500
Subject: [Archivesspace_Users_Group] Print to PDF Failed
Message-ID: <CABkK+0Q2--B8ztW6JYZE5SyjRpvLyt4Wp6SEsCnRGvM5Hq1NKw@mail.gmail.com>

To answer your questions, Blake Carver:

The file exists in the lib folder
aspace version 2.7.0
Java version v8.201  (1.8.0_201-b09)

Any other ideas about what could be causing this issue? Thanks!

-- 
Elise Tanner | Director of Digital Projects and Initiatives
Center for Arkansas History and Culture
University of Arkansas at Little Rock
501-320-5770 | emtanner at ualr.edu | ualr.edu/cahc
facebook.com/ualrcahc | twitter.com/ualrcahc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200609/031168d4/attachment.html>

From blake.carver at lyrasis.org  Wed Jun 10 11:06:50 2020
From: blake.carver at lyrasis.org (Blake Carver)
Date: Wed, 10 Jun 2020 15:06:50 +0000
Subject: [Archivesspace_Users_Group] Print to PDF Failed
In-Reply-To: <CABkK+0Q2--B8ztW6JYZE5SyjRpvLyt4Wp6SEsCnRGvM5Hq1NKw@mail.gmail.com>
References: <CABkK+0Q2--B8ztW6JYZE5SyjRpvLyt4Wp6SEsCnRGvM5Hq1NKw@mail.gmail.com>
Message-ID: <DM6PR22MB2309B412932369849C21EAE69F830@DM6PR22MB2309.namprd22.prod.outlook.com>

Sadly, no clue. That error is pretty clear:
"Generating PDF for Little Rock Scenes photograph collection, 1945-1965
fop.jar not found."

Wherefore art thou fop.jar? Why can't ArchivesSpace find you?
It's where it should be, so why can't ArchivesSpace find it?

Anyone else running Windows have this problem?
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Elise Tanner <emtanner at ualr.edu>
Sent: Tuesday, June 9, 2020 2:35 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Print to PDF Failed

To answer your questions, Blake Carver:

The file exists in the lib folder
aspace version 2.7.0
Java version v8.201  (1.8.0_201-b09)

Any other ideas about what could be causing this issue? Thanks!

--
Elise Tanner | Director of Digital Projects and Initiatives
Center for Arkansas History and Culture
University of Arkansas at Little Rock
501-320-5770 | emtanner at ualr.edu<mailto:emtanner at ualr.edu> | ualr.edu/cahc<http://ualr.edu/cahc>
facebook.com/ualrcahc<http://facebook.com/ualrcahc> | twitter.com/ualrcahc<http://twitter.com/ualrcahc>
[https://ualr.edu/communications/files/2011/04/ua-little-rock-h-rgb.jpg]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200610/7550e036/attachment.html>

From Jessica.Crouch at lyrasis.org  Wed Jun 10 13:24:26 2020
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Wed, 10 Jun 2020 17:24:26 +0000
Subject: [Archivesspace_Users_Group] Open call on how ArchivesSpace can
 amplify and support efforts around antiracism and inclusion
Message-ID: <041064CA-6C5C-4084-B2D2-B310812F17EF@lyrasis.org>

Dear ArchivesSpace Members,



Please join us for our next community call, June 24th at 2-3pm ET (11-noon PT), via Zoom. This open call will be devoted to a discussion of ways ArchivesSpace can support and amplify efforts around antiracism and inclusion, and how ArchivesSpace itself can be more inclusive.  We also want to consider how we can incorporate these considerations more organically into our ongoing programming and our users' experience of ArchivesSpace.



We've come up with a few ideas. What we want most is to hear your ideas.


The running list for discussion is at https://docs.google.com/document/d/1b-GlCSObflqZufIiN4dJ__hlppwPloHXzytsUEVlZp4/edit?usp=sharing. Please feel free to add to or comment on this list in advance of the call or simply join us on the 24th with your thoughts, questions, and suggestions.


In order to better facilitate this conversation, an anonymous chat feature will be offered during the call.  The call will not be recorded.


Whether you can be at the call or not, please reach out to us at ArchivesSpaceHome at lyrasis.org at any time. We welcome your participation in any form.


Here are the details to join the call:


Join from PC, Mac, Linux, iOS or Android

https://lyrasis.zoom.us/j/96142471315?pwd=d1JhV3FUdTFzOVhEcnB2UWdxd2Fkdz09

Meeting ID: 961 4247 1315

Password: 807993



One tap mobile

+19292056099,,96142471315# US (New York)

+13017158592,,96142471315# US (Germantown)



Dial by your location

Meeting ID: 961 4247 1315

Find your local number: https://lyrasis.zoom.us/u/aXaScvS60

International numbers available: https://zoom.us/zoomconference?m=-CnZdNUzB4VhAipYXVQs3X1IOX8LOfFC


We seek to provide a welcoming, inclusive, and safe community experience for everyone and adhere to Code4Lib?s CodeofConduct4Lib. The full text of the code of conduct is available at: http://bit.ly/coc4lib.



Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200610/d37a33f9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 29061 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200610/d37a33f9/attachment.jpg>

From Jessica.Crouch at lyrasis.org  Thu Jun 11 11:08:00 2020
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Thu, 11 Jun 2020 15:08:00 +0000
Subject: [Archivesspace_Users_Group] Take a break with ArchivesSpace on
	Fridays
In-Reply-To: <C56994B7-A96D-4DF3-9CB7-1D932B101927@lyrasis.org>
References: <D815E633-2930-485F-83D9-C2715CCE9F8C@lyrasis.org>
 <4C151ED1-3A98-4217-908A-55C7BA8ED233@lyrasis.org>
 <939F1E31-3ECB-44AD-93A6-6634E8BFF8F7@lyrasis.org>
 <C715180D-A70F-4DFB-8473-AD53F8136486@lyrasis.org>
 <C07A34DF-74FF-481C-A336-A923E6C76FC0@lyrasis.org>
 <512F3C3D-C506-4E11-B5FB-4B9EBF4775B0@lyrasis.org>
 <614B918C-6F58-4D55-89F5-18680C71701B@lyrasis.org>
 <F0569015-EC75-4C21-96D7-6B8B024647CA@lyrasis.org>
 <C56994B7-A96D-4DF3-9CB7-1D932B101927@lyrasis.org>
Message-ID: <69AD5D49-2C12-450D-9763-D88A59297611@lyrasis.org>

Dear ArchivesSpace Users,



We?ll be hosting another casual open call via zoom at 12pm ET tomorrow. With no set agenda or presentation for these calls, this forum is an opportunity to connect, chat and recharge. Use this as a time to get help or talk about ArchivesSpace (or anything else) in an informal setting or just have a beverage with other ArchivesSpace users during this stressful time.



Most of us are doing our jobs under much different conditions than usual. As a browser based system you can access from anywhere, the ArchivesSpace application may offer a sense of archival normalcy as we each adjust. And with a welcoming and robust member community all over the world, ArchivesSpace can also offer camaraderie when many of us may feel isolated from our colleagues or the professional communities we interact with regularly.



Thank you to everyone who joined us last week for a great chat.



We hope to see you all tomorrow.

When: Fridays
Time: 12:00 p.m. ? 1:00 p.m. ET (9:00 a.m. ? 10:00 a.m. PT)
Where: Zoom

Join the call via the information below:


Join Zoom Meeting

https://lyrasis.zoom.us/j/281962467



Meeting ID: 281 962 467



One tap mobile

+19292056099,,281962467# US (New York)

+13126266799,,281962467# US (Chicago)



Dial by your location

        +1 929 205 6099 US (New York)

        +1 312 626 6799 US (Chicago)

        +1 301 715 8592 US

        +1 346 248 7799 US (Houston)

        +1 669 900 6833 US (San Jose)

        +1 253 215 8782 US

        888 475 4499 US Toll-free

        877 853 5257 US Toll-free

Meeting ID: 281 962 467

Find your local number: https://lyrasis.zoom.us/u/awkFNWPxh

We seek to provide a welcoming, fun, and safe community experience for everyone and adhere to Code4Lib?s CodeofConduct4Lib. The full text of the code of conduct is available at: http://bit.ly/coc4lib.

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200611/af355c4b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 29071 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200611/af355c4b/attachment.jpg>

From ltang5 at msu.edu  Thu Jun 11 12:48:08 2020
From: ltang5 at msu.edu (Tang, Lydia)
Date: Thu, 11 Jun 2020 16:48:08 +0000
Subject: [Archivesspace_Users_Group] Draft Collection Organization Usability
	Report call for comments
Message-ID: <164AD5BE-A6F8-46F4-B11A-53543F449E2D@msu.edu>

Hello, everyone!
In the interest of continuing to evolve ArchivesSpace?s public user interface to be as user-friendly as possible, User Advisory Council?s Usability Subteam<https://archivesspace.atlassian.net/wiki/spaces/AC/pages/893714474/Usability> has prepared this draft report<https://docs.google.com/document/d/1laL3pkQKCJ83RXu2OzOFQe_h6BLdxzOAiw-agMauf9U/edit?usp=sharing> which identifies common themes from user-submitted feature request tickets, existing usability studies, and compiles examples of customizations that repositories have taken to address these topics. We hope to hold a webinar or open call in the future to continue to gather community feedback on these ideas. There are many possible paths forward, so the goal is to build consensus on a desired direction to continue to evolve the Collection Organization view of the PUI.

We welcome your feedback and suggestions. Please feel free to comment in this doc or email me at ltang5 at msu.edu<mailto:ltang5 at msu.edu> by the end of this month.

Thanks for your help and feedback!

Lydia Tang, Kate Blalack, Lori Dedeyan, Brittanyt Newberry, Julia Novakovic, and Althea Topek

Usability Subteam



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200611/6484fae8/attachment.html>

From crumins at clemson.edu  Fri Jun 12 09:12:51 2020
From: crumins at clemson.edu (Clayton Joseph Ruminski)
Date: Fri, 12 Jun 2020 13:12:51 +0000
Subject: [Archivesspace_Users_Group] Error deleting agents
In-Reply-To: <DM6PR22MB230934175297A8286272CA5B9F890@DM6PR22MB2309.namprd22.prod.outlook.com>
References: <MN2PR06MB56784661B08EE89BF4E355CAA8890@MN2PR06MB5678.namprd06.prod.outlook.com>
 <DM6PR22MB230934175297A8286272CA5B9F890@DM6PR22MB2309.namprd22.prod.outlook.com>
Message-ID: <MN2PR06MB56784A3FC77422BB8BF54BD6A8810@MN2PR06MB5678.namprd06.prod.outlook.com>

Thanks for your response. I see no indication that there is a user linked to this particular agent. Maybe the agent name might help, as it seems autogenerated: "full name not entered ##2e3 zzzz."

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Blake Carver
Sent: Thursday, June 4, 2020 3:46 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Error deleting agents

We've seen that happen when a user is also an agent.  Probably there's an agent (person) record linked to that user account so the account cannot be deleted. You can delete the agent record first, then the user -- that should work. Careful, sometimes you need that agent record. In that case I'd suggest disabling the account by resetting the password to something long and random so the account cannot be used (and perhaps add "DISABLED" to "Additional Contact Information" as a note).
________________________________
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<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Clayton Joseph Ruminski <crumins at clemson.edu<mailto:crumins at clemson.edu>>
Sent: Thursday, June 4, 2020 3:42 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org> <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Error deleting agents


Hello,



We are doing some data cleanup in ASpace, and one agent in particular is giving me the following error when trying to delete it:



Record deletion failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLIntegrityConstraintViolationException: Cannot delete or update a parent row: a foreign key constraint fails (`archivesspace`.`user`, CONSTRAINT `user_ibfk_1` FOREIGN KEY (`agent_record_id`) REFERENCES `agent_person` (`id`))



I looked on the user group archives but was unable to find an answer. The agent looks to have been autogenerated at some point and is not linked to any records.



Thanks!



Clayton Ruminski CLEMSON UNIVERSITY



Digital and Preservation Archivist

Special Collections and Archives

Clemson University Libraries

crumins at clemson.edu<mailto:crumins at clemson.edu>

864-656-0234


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200612/494ac60a/attachment.html>

From elizabeth.russell1 at maine.edu  Fri Jun 12 13:03:33 2020
From: elizabeth.russell1 at maine.edu (Elizabeth Russell)
Date: Fri, 12 Jun 2020 13:03:33 -0400
Subject: [Archivesspace_Users_Group] Mukurtu question
Message-ID: <CAA8JP9BOu+OdPKitUkPzp-9rNJjwef5HWNw7z5yqCLg-LYo-Aw@mail.gmail.com>

Hello Group,

My institution is partnering with a Native American group to review
potentially sensitive material we may have in our collections.  They use
Mukurtu, a CMS developed for indigenous people, and is built on Drupal.
The proposal is to import the collection records to Mukurtu, they can
review and add TK (traditional knowledge) labels.  Then the records will be
added back to ASpace with the new information.

My question is - does anyone know how or if I can import or export records
to and from ASpace and Mukurtu, without using the API?  I'm not comfortable
using APIs because I don't really know how to use them.

Thank you,

Beth

-- 
Beth Russell
Archivist / Special Collections Librarian

University of Maine, 5729 Raymond H. Fogler Library
Orono, ME 04469-5729
207.581.1676
elizabeth.russell1 at maine.edu
http://www.library.umaine.edu/speccoll
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200612/cc0a1980/attachment.html>

From Corey.Schmidt at uga.edu  Fri Jun 12 14:19:16 2020
From: Corey.Schmidt at uga.edu (Corey Schmidt)
Date: Fri, 12 Jun 2020 18:19:16 +0000
Subject: [Archivesspace_Users_Group] Mukurtu question
In-Reply-To: <CAA8JP9BOu+OdPKitUkPzp-9rNJjwef5HWNw7z5yqCLg-LYo-Aw@mail.gmail.com>
References: <CAA8JP9BOu+OdPKitUkPzp-9rNJjwef5HWNw7z5yqCLg-LYo-Aw@mail.gmail.com>
Message-ID: <BN6PR02MB31563EEF9B4F1D9226D8C348F3810@BN6PR02MB3156.namprd02.prod.outlook.com>

Beth,

If you want to batch export records (EADs, MARCXML, Container labels, PDFs won't work on ASpace versions 2.6-2.7.1) from ArchivesSpace, I'm developing a program<https://github.com/uga-libraries/ASpace_Batch_Export-Cleanup-Upload> to do just that. All you need is your ArchivesSpace username, password, and API URL, which is usually just your ArchivesSpace URL with a :8089 tacked on the end (whoever hosts your ASpace should know). You can find the Windows version here: https://github.com/uga-libraries/ASpace_Batch_Export-Cleanup-Upload/releases/tag/v0.6.1  - click the asbatch-v061.exe. Hopefully a Mac version will be coming soon.

It does not batch import records into ArchivesSpace, as ASpace does that with background jobs already. If you want to export records one at a time, you can do that from the staff interface.

As far as importing and exporting from Mukurtu, I'm not sure how that operates. My hope is the program I'm working on will expand to be interoperable with other systems, but that will take some time.

Let me know if this is helpful and/or you have any questions.

Corey

Corey Schmidt
ArchivesSpace Project Manager
University of Georgia Special Collections Libraries
Email: Corey.Schmidt at uga.edu
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Elizabeth Russell <elizabeth.russell1 at maine.edu>
Sent: Friday, June 12, 2020 1:03 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Mukurtu question

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]

Hello Group,

My institution is partnering with a Native American group to review potentially sensitive material we may have in our collections.  They use Mukurtu, a CMS developed for indigenous people, and is built on Drupal.  The proposal is to import the collection records to Mukurtu, they can review and add TK (traditional knowledge) labels.  Then the records will be added back to ASpace with the new information.

My question is - does anyone know how or if I can import or export records to and from ASpace and Mukurtu, without using the API?  I'm not comfortable using APIs because I don't really know how to use them.

Thank you,

Beth

--
Beth Russell
Archivist / Special Collections Librarian

University of Maine, 5729 Raymond H. Fogler Library
Orono, ME 04469-5729
207.581.1676
elizabeth.russell1 at maine.edu<mailto:elizabeth.russell1 at maine.edu>
http://www.library.umaine.edu/speccoll
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200612/f4b2da6e/attachment.html>

From elizabeth.russell1 at maine.edu  Fri Jun 12 14:23:48 2020
From: elizabeth.russell1 at maine.edu (Elizabeth Russell)
Date: Fri, 12 Jun 2020 14:23:48 -0400
Subject: [Archivesspace_Users_Group] Mukurtu question
In-Reply-To: <BN6PR02MB31563EEF9B4F1D9226D8C348F3810@BN6PR02MB3156.namprd02.prod.outlook.com>
References: <CAA8JP9BOu+OdPKitUkPzp-9rNJjwef5HWNw7z5yqCLg-LYo-Aw@mail.gmail.com>
 <BN6PR02MB31563EEF9B4F1D9226D8C348F3810@BN6PR02MB3156.namprd02.prod.outlook.com>
Message-ID: <CAA8JP9BrYeLfkDJYpYbkH1Rp0rSj5_Wk+Ld6NBCE2Q_944SR-w@mail.gmail.com>

Hi Corey,

This sounds very promising.  I just heard back from Mukurtu and they do not
have a working API, so that aspect is moot.  However, they use a CSV
template for import.  Would your program be able to export CSV archival
object records?

Best,

Beth

On Fri, Jun 12, 2020 at 2:20 PM Corey Schmidt <Corey.Schmidt at uga.edu> wrote:

> Beth,
>
> If you want to batch export records (EADs, MARCXML, Container labels, PDFs
> won't work on ASpace versions 2.6-2.7.1) from ArchivesSpace, I'm developing
> a program
> <https://github.com/uga-libraries/ASpace_Batch_Export-Cleanup-Upload> to
> do just that. All you need is your ArchivesSpace username, password, and
> API URL, which is usually just your ArchivesSpace URL with a :8089 tacked
> on the end (whoever hosts your ASpace should know). You can find the
> Windows version here:
> https://github.com/uga-libraries/ASpace_Batch_Export-Cleanup-Upload/releases/tag/v0.6.1
> - click the asbatch-v061.exe. Hopefully a Mac version will be coming
> soon.
>
> It does not batch import records into ArchivesSpace, as ASpace does that
> with background jobs already. If you want to export records one at a time,
> you can do that from the staff interface.
>
> As far as importing and exporting from Mukurtu, I'm not sure how that
> operates. My hope is the program I'm working on will expand to be
> interoperable with other systems, but that will take some time.
>
> Let me know if this is helpful and/or you have any questions.
>
> Corey
>
> Corey Schmidt
> ArchivesSpace Project Manager
> University of Georgia Special Collections Libraries
> *Email:* Corey.Schmidt at uga.edu
> ------------------------------
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
> Elizabeth Russell <elizabeth.russell1 at maine.edu>
> *Sent:* Friday, June 12, 2020 1:03 PM
> *To:* archivesspace_users_group at lyralists.lyrasis.org <
> archivesspace_users_group at lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] Mukurtu question
>
> [EXTERNAL SENDER - PROCEED CAUTIOUSLY]
>
> Hello Group,
>
> My institution is partnering with a Native American group to review
> potentially sensitive material we may have in our collections.  They use
> Mukurtu, a CMS developed for indigenous people, and is built on Drupal.
> The proposal is to import the collection records to Mukurtu, they can
> review and add TK (traditional knowledge) labels.  Then the records will be
> added back to ASpace with the new information.
>
> My question is - does anyone know how or if I can import or export records
> to and from ASpace and Mukurtu, without using the API?  I'm not comfortable
> using APIs because I don't really know how to use them.
>
> Thank you,
>
> Beth
>
> --
> Beth Russell
> Archivist / Special Collections Librarian
>
> University of Maine, 5729 Raymond H. Fogler Library
> Orono, ME 04469-5729
> 207.581.1676
> elizabeth.russell1 at maine.edu
> http://www.library.umaine.edu/speccoll
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Beth Russell
Archivist / Special Collections Librarian

University of Maine, 5729 Raymond H. Fogler Library
Orono, ME 04469-5729
207.581.1676
elizabeth.russell1 at maine.edu
http://www.library.umaine.edu/speccoll
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200612/0691bc62/attachment.html>

From seth.shaw at unlv.edu  Fri Jun 12 15:04:00 2020
From: seth.shaw at unlv.edu (Seth Shaw)
Date: Fri, 12 Jun 2020 12:04:00 -0700
Subject: [Archivesspace_Users_Group] Mukurtu question
In-Reply-To: <CAA8JP9BrYeLfkDJYpYbkH1Rp0rSj5_Wk+Ld6NBCE2Q_944SR-w@mail.gmail.com>
References: <CAA8JP9BOu+OdPKitUkPzp-9rNJjwef5HWNw7z5yqCLg-LYo-Aw@mail.gmail.com>
 <BN6PR02MB31563EEF9B4F1D9226D8C348F3810@BN6PR02MB3156.namprd02.prod.outlook.com>
 <CAA8JP9BrYeLfkDJYpYbkH1Rp0rSj5_Wk+Ld6NBCE2Q_944SR-w@mail.gmail.com>
Message-ID: <CANuEgP7nPwge_jBZ7ZUcxHEDm8o97ziHsEgoE9EZ4kksF9D5cA@mail.gmail.com>

I don't believe the AS API has a CSV export option, however, I have an XSL
that can turn an EAD into a CSV of archival objects (using the c-levels; it
goes up to 5 levels deep):
https://github.com/seth-shaw-unlv/small-stuff/blob/master/ead-numbered-components_to_tsv.xsl.
You would just need to add the collection level data separately.

On Fri, Jun 12, 2020 at 11:25 AM Elizabeth Russell <
elizabeth.russell1 at maine.edu> wrote:

> Hi Corey,
>
> This sounds very promising.  I just heard back from Mukurtu and they do
> not have a working API, so that aspect is moot.  However, they use a CSV
> template for import.  Would your program be able to export CSV archival
> object records?
>
> Best,
>
> Beth
>
> On Fri, Jun 12, 2020 at 2:20 PM Corey Schmidt <Corey.Schmidt at uga.edu>
> wrote:
>
>> Beth,
>>
>> If you want to batch export records (EADs, MARCXML, Container labels,
>> PDFs won't work on ASpace versions 2.6-2.7.1) from ArchivesSpace, I'm
>> developing a program
>> <https://github.com/uga-libraries/ASpace_Batch_Export-Cleanup-Upload> to
>> do just that. All you need is your ArchivesSpace username, password, and
>> API URL, which is usually just your ArchivesSpace URL with a :8089 tacked
>> on the end (whoever hosts your ASpace should know). You can find the
>> Windows version here:
>> https://github.com/uga-libraries/ASpace_Batch_Export-Cleanup-Upload/releases/tag/v0.6.1
>> - click the asbatch-v061.exe. Hopefully a Mac version will be coming
>> soon.
>>
>> It does not batch import records into ArchivesSpace, as ASpace does that
>> with background jobs already. If you want to export records one at a time,
>> you can do that from the staff interface.
>>
>> As far as importing and exporting from Mukurtu, I'm not sure how that
>> operates. My hope is the program I'm working on will expand to be
>> interoperable with other systems, but that will take some time.
>>
>> Let me know if this is helpful and/or you have any questions.
>>
>> Corey
>>
>> Corey Schmidt
>> ArchivesSpace Project Manager
>> University of Georgia Special Collections Libraries
>> *Email:* Corey.Schmidt at uga.edu
>> ------------------------------
>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
>> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
>> Elizabeth Russell <elizabeth.russell1 at maine.edu>
>> *Sent:* Friday, June 12, 2020 1:03 PM
>> *To:* archivesspace_users_group at lyralists.lyrasis.org <
>> archivesspace_users_group at lyralists.lyrasis.org>
>> *Subject:* [Archivesspace_Users_Group] Mukurtu question
>>
>> [EXTERNAL SENDER - PROCEED CAUTIOUSLY]
>>
>> Hello Group,
>>
>> My institution is partnering with a Native American group to review
>> potentially sensitive material we may have in our collections.  They use
>> Mukurtu, a CMS developed for indigenous people, and is built on Drupal.
>> The proposal is to import the collection records to Mukurtu, they can
>> review and add TK (traditional knowledge) labels.  Then the records will be
>> added back to ASpace with the new information.
>>
>> My question is - does anyone know how or if I can import or export
>> records to and from ASpace and Mukurtu, without using the API?  I'm not
>> comfortable using APIs because I don't really know how to use them.
>>
>> Thank you,
>>
>> Beth
>>
>> --
>> Beth Russell
>> Archivist / Special Collections Librarian
>>
>> University of Maine, 5729 Raymond H. Fogler Library
>> Orono, ME 04469-5729
>> 207.581.1676
>> elizabeth.russell1 at maine.edu
>> http://www.library.umaine.edu/speccoll
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
>
>
> --
> Beth Russell
> Archivist / Special Collections Librarian
>
> University of Maine, 5729 Raymond H. Fogler Library
> Orono, ME 04469-5729
> 207.581.1676
> elizabeth.russell1 at maine.edu
> http://www.library.umaine.edu/speccoll
> _______________________________________________
> 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/20200612/d7e756a8/attachment.html>

From Corey.Schmidt at uga.edu  Fri Jun 12 15:26:36 2020
From: Corey.Schmidt at uga.edu (Corey Schmidt)
Date: Fri, 12 Jun 2020 19:26:36 +0000
Subject: [Archivesspace_Users_Group] Mukurtu question
In-Reply-To: <CANuEgP7nPwge_jBZ7ZUcxHEDm8o97ziHsEgoE9EZ4kksF9D5cA@mail.gmail.com>
References: <CAA8JP9BOu+OdPKitUkPzp-9rNJjwef5HWNw7z5yqCLg-LYo-Aw@mail.gmail.com>
 <BN6PR02MB31563EEF9B4F1D9226D8C348F3810@BN6PR02MB3156.namprd02.prod.outlook.com>
 <CAA8JP9BrYeLfkDJYpYbkH1Rp0rSj5_Wk+Ld6NBCE2Q_944SR-w@mail.gmail.com>,
 <CANuEgP7nPwge_jBZ7ZUcxHEDm8o97ziHsEgoE9EZ4kksF9D5cA@mail.gmail.com>
Message-ID: <BN6PR02MB31569B069FD636FF5DE576DBF3810@BN6PR02MB3156.namprd02.prod.outlook.com>

Beth and Seth,

Currently my program does not export CSV archival object records. Though it sounds like Seth's XSL might help with that. You could try seeing how Seth's script works and if you want to just export a bunch of EADs, my program could still help with that.

Corey
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Seth Shaw <seth.shaw at unlv.edu>
Sent: Friday, June 12, 2020 3:04 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Mukurtu question

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]

I don't believe the AS API has a CSV export option, however, I have an XSL that can turn an EAD into a CSV of archival objects (using the c-levels; it goes up to 5 levels deep): https://github.com/seth-shaw-unlv/small-stuff/blob/master/ead-numbered-components_to_tsv.xsl. You would just need to add the collection level data separately.

On Fri, Jun 12, 2020 at 11:25 AM Elizabeth Russell <elizabeth.russell1 at maine.edu<mailto:elizabeth.russell1 at maine.edu>> wrote:
Hi Corey,

This sounds very promising.  I just heard back from Mukurtu and they do not have a working API, so that aspect is moot.  However, they use a CSV template for import.  Would your program be able to export CSV archival object records?

Best,

Beth

On Fri, Jun 12, 2020 at 2:20 PM Corey Schmidt <Corey.Schmidt at uga.edu<mailto:Corey.Schmidt at uga.edu>> wrote:
Beth,

If you want to batch export records (EADs, MARCXML, Container labels, PDFs won't work on ASpace versions 2.6-2.7.1) from ArchivesSpace, I'm developing a program<https://github.com/uga-libraries/ASpace_Batch_Export-Cleanup-Upload> to do just that. All you need is your ArchivesSpace username, password, and API URL, which is usually just your ArchivesSpace URL with a :8089 tacked on the end (whoever hosts your ASpace should know). You can find the Windows version here: https://github.com/uga-libraries/ASpace_Batch_Export-Cleanup-Upload/releases/tag/v0.6.1  - click the asbatch-v061.exe. Hopefully a Mac version will be coming soon.

It does not batch import records into ArchivesSpace, as ASpace does that with background jobs already. If you want to export records one at a time, you can do that from the staff interface.

As far as importing and exporting from Mukurtu, I'm not sure how that operates. My hope is the program I'm working on will expand to be interoperable with other systems, but that will take some time.

Let me know if this is helpful and/or you have any questions.

Corey

Corey Schmidt
ArchivesSpace Project Manager
University of Georgia Special Collections Libraries
Email: Corey.Schmidt at uga.edu<mailto:Corey.Schmidt at uga.edu>
________________________________
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<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Elizabeth Russell <elizabeth.russell1 at maine.edu<mailto:elizabeth.russell1 at maine.edu>>
Sent: Friday, June 12, 2020 1:03 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org> <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Mukurtu question

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]

Hello Group,

My institution is partnering with a Native American group to review potentially sensitive material we may have in our collections.  They use Mukurtu, a CMS developed for indigenous people, and is built on Drupal.  The proposal is to import the collection records to Mukurtu, they can review and add TK (traditional knowledge) labels.  Then the records will be added back to ASpace with the new information.

My question is - does anyone know how or if I can import or export records to and from ASpace and Mukurtu, without using the API?  I'm not comfortable using APIs because I don't really know how to use them.

Thank you,

Beth

--
Beth Russell
Archivist / Special Collections Librarian

University of Maine, 5729 Raymond H. Fogler Library
Orono, ME 04469-5729
207.581.1676
elizabeth.russell1 at maine.edu<mailto:elizabeth.russell1 at maine.edu>
http://www.library.umaine.edu/speccoll
_______________________________________________
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


--
Beth Russell
Archivist / Special Collections Librarian

University of Maine, 5729 Raymond H. Fogler Library
Orono, ME 04469-5729
207.581.1676
elizabeth.russell1 at maine.edu<mailto:elizabeth.russell1 at maine.edu>
http://www.library.umaine.edu/speccoll
_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200612/4e2333fd/attachment-0001.html>

From elizabeth.russell1 at maine.edu  Fri Jun 12 15:29:52 2020
From: elizabeth.russell1 at maine.edu (Elizabeth Russell)
Date: Fri, 12 Jun 2020 15:29:52 -0400
Subject: [Archivesspace_Users_Group] Mukurtu question
In-Reply-To: <BN6PR02MB31569B069FD636FF5DE576DBF3810@BN6PR02MB3156.namprd02.prod.outlook.com>
References: <CAA8JP9BOu+OdPKitUkPzp-9rNJjwef5HWNw7z5yqCLg-LYo-Aw@mail.gmail.com>
 <BN6PR02MB31563EEF9B4F1D9226D8C348F3810@BN6PR02MB3156.namprd02.prod.outlook.com>
 <CAA8JP9BrYeLfkDJYpYbkH1Rp0rSj5_Wk+Ld6NBCE2Q_944SR-w@mail.gmail.com>
 <CANuEgP7nPwge_jBZ7ZUcxHEDm8o97ziHsEgoE9EZ4kksF9D5cA@mail.gmail.com>
 <BN6PR02MB31569B069FD636FF5DE576DBF3810@BN6PR02MB3156.namprd02.prod.outlook.com>
Message-ID: <CAA8JP9DEdF+Etn3-cCWkjYG+a-szr=dhSPgK3RBYS47GPY2dMA@mail.gmail.com>

Hi Corey and Seth,

This is going to be a grant-funded project, so my time frame is uncertain,
assuming we get funded.  For now I wanted to know what was possible and
what challenges there might be.  I'm sure later down the road I will be
back with questions.  I want to thank you for your help - it's been a huge
help.

Best,

Beth

On Fri, Jun 12, 2020 at 3:27 PM Corey Schmidt <Corey.Schmidt at uga.edu> wrote:

> Beth and Seth,
>
> Currently my program does not export CSV archival object records. Though
> it sounds like Seth's XSL might help with that. You could try seeing how
> Seth's script works and if you want to just export a bunch of EADs, my
> program could still help with that.
>
> Corey
> ------------------------------
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
> Seth Shaw <seth.shaw at unlv.edu>
> *Sent:* Friday, June 12, 2020 3:04 PM
> *To:* Archivesspace Users Group <
> archivesspace_users_group at lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Mukurtu question
>
> [EXTERNAL SENDER - PROCEED CAUTIOUSLY]
>
> I don't believe the AS API has a CSV export option, however, I have an XSL
> that can turn an EAD into a CSV of archival objects (using the c-levels; it
> goes up to 5 levels deep):
> https://github.com/seth-shaw-unlv/small-stuff/blob/master/ead-numbered-components_to_tsv.xsl.
> You would just need to add the collection level data separately.
>
> On Fri, Jun 12, 2020 at 11:25 AM Elizabeth Russell <
> elizabeth.russell1 at maine.edu> wrote:
>
> Hi Corey,
>
> This sounds very promising.  I just heard back from Mukurtu and they do
> not have a working API, so that aspect is moot.  However, they use a CSV
> template for import.  Would your program be able to export CSV archival
> object records?
>
> Best,
>
> Beth
>
> On Fri, Jun 12, 2020 at 2:20 PM Corey Schmidt <Corey.Schmidt at uga.edu>
> wrote:
>
> Beth,
>
> If you want to batch export records (EADs, MARCXML, Container labels, PDFs
> won't work on ASpace versions 2.6-2.7.1) from ArchivesSpace, I'm developing
> a program
> <https://github.com/uga-libraries/ASpace_Batch_Export-Cleanup-Upload> to
> do just that. All you need is your ArchivesSpace username, password, and
> API URL, which is usually just your ArchivesSpace URL with a :8089 tacked
> on the end (whoever hosts your ASpace should know). You can find the
> Windows version here:
> https://github.com/uga-libraries/ASpace_Batch_Export-Cleanup-Upload/releases/tag/v0.6.1
> - click the asbatch-v061.exe. Hopefully a Mac version will be coming
> soon.
>
> It does not batch import records into ArchivesSpace, as ASpace does that
> with background jobs already. If you want to export records one at a time,
> you can do that from the staff interface.
>
> As far as importing and exporting from Mukurtu, I'm not sure how that
> operates. My hope is the program I'm working on will expand to be
> interoperable with other systems, but that will take some time.
>
> Let me know if this is helpful and/or you have any questions.
>
> Corey
>
> Corey Schmidt
> ArchivesSpace Project Manager
> University of Georgia Special Collections Libraries
> *Email:* Corey.Schmidt at uga.edu
> ------------------------------
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
> Elizabeth Russell <elizabeth.russell1 at maine.edu>
> *Sent:* Friday, June 12, 2020 1:03 PM
> *To:* archivesspace_users_group at lyralists.lyrasis.org <
> archivesspace_users_group at lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] Mukurtu question
>
> [EXTERNAL SENDER - PROCEED CAUTIOUSLY]
>
> Hello Group,
>
> My institution is partnering with a Native American group to review
> potentially sensitive material we may have in our collections.  They use
> Mukurtu, a CMS developed for indigenous people, and is built on Drupal.
> The proposal is to import the collection records to Mukurtu, they can
> review and add TK (traditional knowledge) labels.  Then the records will be
> added back to ASpace with the new information.
>
> My question is - does anyone know how or if I can import or export records
> to and from ASpace and Mukurtu, without using the API?  I'm not comfortable
> using APIs because I don't really know how to use them.
>
> Thank you,
>
> Beth
>
> --
> Beth Russell
> Archivist / Special Collections Librarian
>
> University of Maine, 5729 Raymond H. Fogler Library
> Orono, ME 04469-5729
> 207.581.1676
> elizabeth.russell1 at maine.edu
> http://www.library.umaine.edu/speccoll
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
> --
> Beth Russell
> Archivist / Special Collections Librarian
>
> University of Maine, 5729 Raymond H. Fogler Library
> Orono, ME 04469-5729
> 207.581.1676
> elizabeth.russell1 at maine.edu
> http://www.library.umaine.edu/speccoll
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Beth Russell
Archivist / Special Collections Librarian

University of Maine, 5729 Raymond H. Fogler Library
Orono, ME 04469-5729
207.581.1676
elizabeth.russell1 at maine.edu
http://www.library.umaine.edu/speccoll
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200612/7b2851db/attachment.html>

From christine.dibella at lyrasis.org  Wed Jun 17 09:32:24 2020
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Wed, 17 Jun 2020 13:32:24 +0000
Subject: [Archivesspace_Users_Group] FW: Archival Collecting Pandemic Survey
	Extension
In-Reply-To: <CH2PR22MB1816E44ED54532B49B07EB27919C0@CH2PR22MB1816.namprd22.prod.outlook.com>
References: <CH2PR22MB181615D9FF5131FC76D938E9919C0@CH2PR22MB1816.namprd22.prod.outlook.com>
 <CH2PR22MB1816E44ED54532B49B07EB27919C0@CH2PR22MB1816.namprd22.prod.outlook.com>
Message-ID: <MN2PR22MB18874850D507A181DEC9B9DFF19A0@MN2PR22MB1887.namprd22.prod.outlook.com>

>From our colleagues at LYRASIS. Please contact Katy Klettlinger (katy.klettlinger at lyrasis.org<mailto:katy.klettlinger at lyrasis.org>) if you have any questions.


From: Katy Klettlinger
Sent: Monday, June 15, 2020 1:27 PM
To: archivpres at lyralists.lyrasis.org<mailto:archivpres at lyralists.lyrasis.org>
Subject: Archival Collecting Pandemic Survey Extension

Hello everyone,

First, I wanted to say thank you for those that have taken our survey to determine archival collecting practices during the COVID-19 Pandemic thus far.  We have received many responses to better understand and support the needs of our community.

Since the input we have received has been valuable we have decided to extend our survey deadline to June 26, 2020 at 5:00 Eastern time.

Please discuss any special needs or concerns related to the pandemic with your colleagues before completing the survey, as we hope to have one survey representing a single institution, and not multiple surveys from a single site. The survey is available at https://www.surveymonkey.com/r/3T5V5JN. We estimate the survey will take 15 minutes to complete.

Confidentiality: Your responses are being collected and analyzed by LYRASIS, an independent, nonprofit, membership organization serving archives, libraries, and museums. They will be kept confidential. Only aggregate results will be reported. Please answer these questions to help us learn about your current practices and needs. To submit your answers, you must click on the "Submit Your Responses" button at the end of the survey form.

If you have any questions, please contact me at katy.klettlinger at lyrasis.org<mailto:katy.klettlinger at lyrasis.org>.

Thank you for your support of this important project; we look forward to sharing what we discover with the archival community.

Many thanks,

Katy

Katy L. W. Klettlinger, MLIS
Consultant & Member Outreach Librarian, Mid-Atlantic & Great Lakes
katy.klettlinger at lyrasis.org<mailto:katy.klettlinger at lyrasis.org>
Cell phone: 404-576-9099
Skype: Katy Klettlinger
www.lyrasis.org<http://scanmail.trustwave.com/?c=4062&d=5_iN1kjXojNr_FJpESYJgqo53kqZrtv4bUWkxzAs3g&s=712&u=http%3a%2f%2fwww%2elyrasis%2eorg%2f>








-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200617/8df86e67/attachment.html>

From Jessica.Crouch at lyrasis.org  Wed Jun 17 12:41:27 2020
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Wed, 17 Jun 2020 16:41:27 +0000
Subject: [Archivesspace_Users_Group] Call for speakers - ArchivesSpace 6th
	Annual Member Forum
Message-ID: <5C6227D2-4FD2-4E2F-82F9-816F787AA00C@lyrasis.org>

Dear ArchivesSpace Members,



ArchivesSpace will be holding its sixth Annual Member Forum virtually on August 3-7, 2020, from 12pm-3pm ET each day via Zoom.  Just as in previous years, this free event is a chance for ArchivesSpace members to come together to highlight the work they are doing in ArchivesSpace, show off new plugins or tools they?ve developed, and attend workshops and trainings on a variety of topics. As with our previous Annual Member Forums, it is being held in conjunction with the Society of American Archivists annual meeting, but it is not part of SAA and does not require registration for the SAA Annual Meeting.



Presentations and breakout discussions will be held on August 3-4, 2020, and all individuals from ArchivesSpace member institutions are welcome to attend some or all of the sessions on these days.  Small workshops covering specific elements of the ArchivesSpace application will be offered August 5-7, 2020.  These workshops will be limited to 25 participants per workshop.



The event wiki and registrations will be made available soon, but for now we are looking for presenters and discussion leaders for August 3-4, 2020. Anything related to ArchivesSpace is fair game. We are specifically interested in presentations or topics related to managing others using ArchivesSpace, how you or your institution have adapted your use of ArchivesSpace during COVID-19, and any plugin or tool you?ve developed that you?d like to show off.

There is a short Google form for proposals available at https://forms.gle/DsZNqe2cANy5mS4S7. Proposals will be reviewed on a rolling basis. The last day that proposals will be accepted is July 15, 2020, and all notifications will be made by July 22, 2020.

If you have any questions or other suggestions at this point, please feel free to email Jessica at jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>.

We look forward to ?seeing? you soon!
Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200617/d7f9dbba/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 29061 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200617/d7f9dbba/attachment.jpg>

From dawne_lucas at unc.edu  Thu Jun 18 08:12:59 2020
From: dawne_lucas at unc.edu (Lucas, Dawne Howard)
Date: Thu, 18 Jun 2020 12:12:59 +0000
Subject: [Archivesspace_Users_Group] Top container ranges
Message-ID: <BN7PR03MB358620C2485250B5D483E837969B0@BN7PR03MB3586.namprd03.prod.outlook.com>

Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into ArchivesSpace and are wondering how other institutions have handled top container ranges.



For example, we have finding aids coded like this:



<c02><did><container type="box" label="Box">3-4</container><unittitle>Photographs</unittitle></did></c02>



This imports into ASpace just fine (yay!), but of course also creates a top container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding to:



<c02><did><container type="box" label="Box">3</container><unittitle>Photographs</unittitle></did></c02>



<c02><did><container type="box" label="Box">4 </container><unittitle>Photographs</unittitle></did></c02>



For several reasons, this is not a viable solution for us. Have other institutions figured out a way to deal with this issue that does not include editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image001.png at 01D5F200.0D957C80]<https://library.unc.edu/wilson/>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/c9349756/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 8909C66936A54A598559DD23E6AE5CC2[189067716].png
Type: image/png
Size: 8588 bytes
Desc: 8909C66936A54A598559DD23E6AE5CC2[189067716].png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/c9349756/attachment.png>

From dawne_lucas at unc.edu  Thu Jun 18 08:44:14 2020
From: dawne_lucas at unc.edu (Lucas, Dawne Howard)
Date: Thu, 18 Jun 2020 12:44:14 +0000
Subject: [Archivesspace_Users_Group] Top container ranges
In-Reply-To: <BN7PR03MB358620C2485250B5D483E837969B0@BN7PR03MB3586.namprd03.prod.outlook.com>
References: <BN7PR03MB358620C2485250B5D483E837969B0@BN7PR03MB3586.namprd03.prod.outlook.com>
Message-ID: <BN7PR03MB3586127E3D90F50A58930B0F969B0@BN7PR03MB3586.namprd03.prod.outlook.com>

One quick-follow up: we?re not completely clueless about how we might do this, but appreciate hearing about the experience at other institutions. For those institutions that have done this, were there any drawbacks?

Thanks,

Dawne


From: Lucas, Dawne Howard<mailto:dawne_lucas at unc.edu>
Sent: Thursday, June 18, 2020 8:13 AM
To: Archivesspace Users Group<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into ArchivesSpace and are wondering how other institutions have handled top container ranges.



For example, we have finding aids coded like this:



<c02><did><container type="box" label="Box">3-4</container><unittitle>Photographs</unittitle></did></c02>



This imports into ASpace just fine (yay!), but of course also creates a top container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding to:



<c02><did><container type="box" label="Box">3</container><unittitle>Photographs</unittitle></did></c02>



<c02><did><container type="box" label="Box">4 </container><unittitle>Photographs</unittitle></did></c02>



For several reasons, this is not a viable solution for us. Have other institutions figured out a way to deal with this issue that does not include editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image001.png at 01D5F200.0D957C80]<https://library.unc.edu/wilson/>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/ba74efbd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 8909C66936A54A598559DD23E6AE5CC2[189069655].png
Type: image/png
Size: 8588 bytes
Desc: 8909C66936A54A598559DD23E6AE5CC2[189069655].png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/ba74efbd/attachment.png>

From dave_mayo at harvard.edu  Thu Jun 18 09:04:14 2020
From: dave_mayo at harvard.edu (Mayo, Dave)
Date: Thu, 18 Jun 2020 13:04:14 +0000
Subject: [Archivesspace_Users_Group] Top container ranges
Message-ID: <CC61910F-4534-47C6-B5D5-DF17A45BC7EC@harvard.edu>

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they?re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn?t mind going more into why that?s not a viable solution for you, it might help us provide better advice?

Either way, at 7000 finding aids, the solution would basically need to be automated ? if your box ranges are very regular (i.e. only single number or range, no ?3,4,7-10? or similar), it wouldn?t be too difficult ? split the range on ?-?, generate list of numbers, replace container with multiple containers.

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into ArchivesSpace and are wondering how other institutions have handled top container ranges.



For example, we have finding aids coded like this:



<c02><did><container type="box" label="Box">3-4</container><unittitle>Photographs</unittitle></did></c02>



This imports into ASpace just fine (yay!), but of course also creates a top container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding to:



<c02><did><container type="box" label="Box">3</container><unittitle>Photographs</unittitle></did></c02>



<c02><did><container type="box" label="Box">4 </container><unittitle>Photographs</unittitle></did></c02>



For several reasons, this is not a viable solution for us. Have other institutions figured out a way to deal with this issue that does not include editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image001.png at 01D5F200.0D957C80]<https://urldefense.proofpoint.com/v2/url?u=https-3A__library.unc.edu_wilson_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=tkJE1JdGvSoNb5i6NSRbF3z1n28dGeVJ4ogcFmpTpQo&s=e9r4LIAN87oWg7LLTrzui9bCYcCMX-8twYfh3y0I8tY&e=>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/a529ae55/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8589 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/a529ae55/attachment.png>

From dawne_lucas at unc.edu  Thu Jun 18 09:12:32 2020
From: dawne_lucas at unc.edu (Lucas, Dawne Howard)
Date: Thu, 18 Jun 2020 13:12:32 +0000
Subject: [Archivesspace_Users_Group] Top container ranges
In-Reply-To: <CC61910F-4534-47C6-B5D5-DF17A45BC7EC@harvard.edu>
References: <CC61910F-4534-47C6-B5D5-DF17A45BC7EC@harvard.edu>
Message-ID: <BN7PR03MB3586080D9386B1CD8CEA14E5969B0@BN7PR03MB3586.namprd03.prod.outlook.com>

Thanks, Dave.  I guess I should have specified that changing the EAD isn?t a viable solution for us unless it?s automated. We do not plan to edit individual finding aids manually except in cases where the ranges aren?t regular.

If you?ve done this at Harvard, have there been any drawbacks? Anything we should be looking to avoid?

Thanks again,

Dawne


From: Mayo, Dave<mailto:dave_mayo at harvard.edu>
Sent: Thursday, June 18, 2020 9:04 AM
To: Archivesspace Users Group<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they?re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn?t mind going more into why that?s not a viable solution for you, it might help us provide better advice?

Either way, at 7000 finding aids, the solution would basically need to be automated ? if your box ranges are very regular (i.e. only single number or range, no ?3,4,7-10? or similar), it wouldn?t be too difficult ? split the range on ?-?, generate list of numbers, replace container with multiple containers.
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into ArchivesSpace and are wondering how other institutions have handled top container ranges.



For example, we have finding aids coded like this:



<c02><did><container type="box" label="Box">3-4</container><unittitle>Photographs</unittitle></did></c02>



This imports into ASpace just fine (yay!), but of course also creates a top container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding to:



<c02><did><container type="box" label="Box">3</container><unittitle>Photographs</unittitle></did></c02>



<c02><did><container type="box" label="Box">4 </container><unittitle>Photographs</unittitle></did></c02>



For several reasons, this is not a viable solution for us. Have other institutions figured out a way to deal with this issue that does not include editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image001.png at 01D5F200.0D957C80]<https://urldefense.proofpoint.com/v2/url?u=https-3A__library.unc.edu_wilson_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=tkJE1JdGvSoNb5i6NSRbF3z1n28dGeVJ4ogcFmpTpQo&s=e9r4LIAN87oWg7LLTrzui9bCYcCMX-8twYfh3y0I8tY&e=>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/9ac4dc27/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8589 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/9ac4dc27/attachment.png>

From dave_mayo at harvard.edu  Thu Jun 18 09:22:57 2020
From: dave_mayo at harvard.edu (Mayo, Dave)
Date: Thu, 18 Jun 2020 13:22:57 +0000
Subject: [Archivesspace_Users_Group] Top container ranges
In-Reply-To: <BN7PR03MB3586080D9386B1CD8CEA14E5969B0@BN7PR03MB3586.namprd03.prod.outlook.com>
References: <CC61910F-4534-47C6-B5D5-DF17A45BC7EC@harvard.edu>
 <BN7PR03MB3586080D9386B1CD8CEA14E5969B0@BN7PR03MB3586.namprd03.prod.outlook.com>
Message-ID: <BBFFEDD9-5712-4240-8EB7-7262C615E827@harvard.edu>

So, with the caveat that we put a lot of resources (a bunch of archivists? time, a full year of a full time developer (me!)), we had very solid results; I think remediating issues prior to import is almost always worth the expense of significant effort, particularly over a large corpus.

My main advice would be to be very, very careful about changes ? version your EADs, compare before and after scripts run, and in general be very systematic about how you find, report, and correct changes.

I don?t know if you?ve seen it, but Kate Bowers and I did a write-up of what we did during our migration ? it has links to a number of open source tools I wrote for doing this kind of work.  They?re a bit involved to get running, but they definitely work at basically any scale out there, and I?m happy to help people get started with them.  https://journal.code4lib.org/articles/12239

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, June 18, 2020 at 9:12 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Thanks, Dave.  I guess I should have specified that changing the EAD isn?t a viable solution for us unless it?s automated. We do not plan to edit individual finding aids manually except in cases where the ranges aren?t regular.

If you?ve done this at Harvard, have there been any drawbacks? Anything we should be looking to avoid?

Thanks again,

Dawne


From: Mayo, Dave<mailto:dave_mayo at harvard.edu>
Sent: Thursday, June 18, 2020 9:04 AM
To: Archivesspace Users Group<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they?re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn?t mind going more into why that?s not a viable solution for you, it might help us provide better advice?

Either way, at 7000 finding aids, the solution would basically need to be automated ? if your box ranges are very regular (i.e. only single number or range, no ?3,4,7-10? or similar), it wouldn?t be too difficult ? split the range on ?-?, generate list of numbers, replace container with multiple containers.
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into ArchivesSpace and are wondering how other institutions have handled top container ranges.



For example, we have finding aids coded like this:



<c02><did><container type="box" label="Box">3-4</container><unittitle>Photographs</unittitle></did></c02>



This imports into ASpace just fine (yay!), but of course also creates a top container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding to:



<c02><did><container type="box" label="Box">3</container><unittitle>Photographs</unittitle></did></c02>



<c02><did><container type="box" label="Box">4 </container><unittitle>Photographs</unittitle></did></c02>



For several reasons, this is not a viable solution for us. Have other institutions figured out a way to deal with this issue that does not include editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image001.png at 01D5F200.0D957C80]<https://urldefense.proofpoint.com/v2/url?u=https-3A__library.unc.edu_wilson_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=tkJE1JdGvSoNb5i6NSRbF3z1n28dGeVJ4ogcFmpTpQo&s=e9r4LIAN87oWg7LLTrzui9bCYcCMX-8twYfh3y0I8tY&e=>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/4b1f8e84/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8590 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/4b1f8e84/attachment.png>

From dave_mayo at harvard.edu  Thu Jun 18 09:37:15 2020
From: dave_mayo at harvard.edu (Mayo, Dave)
Date: Thu, 18 Jun 2020 13:37:15 +0000
Subject: [Archivesspace_Users_Group] Top container ranges
In-Reply-To: <BBFFEDD9-5712-4240-8EB7-7262C615E827@harvard.edu>
References: <CC61910F-4534-47C6-B5D5-DF17A45BC7EC@harvard.edu>
 <BN7PR03MB3586080D9386B1CD8CEA14E5969B0@BN7PR03MB3586.namprd03.prod.outlook.com>
 <BBFFEDD9-5712-4240-8EB7-7262C615E827@harvard.edu>
Message-ID: <A18BB140-256F-401A-988C-57C870A84387@harvard.edu>

Also, specifically:


  1.  Using an XML database like eXist-db or BaseX with XPath/XQuery was invaluable when doing analysis of issues and of the impact of changes
  2.  One of the tools I wrote, the EAD Checker, is available online: https://eadchecker.lib.harvard.edu ? it doesn?t catch this specific issue, but it does catch a bunch of issues, some of which cause corrupted data rather than failure to import.

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Mayo, Dave" <dave_mayo at harvard.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, June 18, 2020 at 9:23 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

So, with the caveat that we put a lot of resources (a bunch of archivists? time, a full year of a full time developer (me!)), we had very solid results; I think remediating issues prior to import is almost always worth the expense of significant effort, particularly over a large corpus.

My main advice would be to be very, very careful about changes ? version your EADs, compare before and after scripts run, and in general be very systematic about how you find, report, and correct changes.

I don?t know if you?ve seen it, but Kate Bowers and I did a write-up of what we did during our migration ? it has links to a number of open source tools I wrote for doing this kind of work.  They?re a bit involved to get running, but they definitely work at basically any scale out there, and I?m happy to help people get started with them.  https://journal.code4lib.org/articles/12239<https://urldefense.proofpoint.com/v2/url?u=https-3A__journal.code4lib.org_articles_12239&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=MDvEtnIJJpOOfJzfDMsXF5u8QJ22oJqGB1UWDHD9Gmc&s=0ky2pQ2HoOxy34kpHGjThpBcFVj1ERUBf7LwbRZMMP4&e=>

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, June 18, 2020 at 9:12 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Thanks, Dave.  I guess I should have specified that changing the EAD isn?t a viable solution for us unless it?s automated. We do not plan to edit individual finding aids manually except in cases where the ranges aren?t regular.

If you?ve done this at Harvard, have there been any drawbacks? Anything we should be looking to avoid?

Thanks again,

Dawne


From: Mayo, Dave<mailto:dave_mayo at harvard.edu>
Sent: Thursday, June 18, 2020 9:04 AM
To: Archivesspace Users Group<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they?re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn?t mind going more into why that?s not a viable solution for you, it might help us provide better advice?

Either way, at 7000 finding aids, the solution would basically need to be automated ? if your box ranges are very regular (i.e. only single number or range, no ?3,4,7-10? or similar), it wouldn?t be too difficult ? split the range on ?-?, generate list of numbers, replace container with multiple containers.
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into ArchivesSpace and are wondering how other institutions have handled top container ranges.



For example, we have finding aids coded like this:



<c02><did><container type="box" label="Box">3-4</container><unittitle>Photographs</unittitle></did></c02>



This imports into ASpace just fine (yay!), but of course also creates a top container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding to:



<c02><did><container type="box" label="Box">3</container><unittitle>Photographs</unittitle></did></c02>



<c02><did><container type="box" label="Box">4 </container><unittitle>Photographs</unittitle></did></c02>



For several reasons, this is not a viable solution for us. Have other institutions figured out a way to deal with this issue that does not include editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image001.png at 01D5F200.0D957C80]<https://urldefense.proofpoint.com/v2/url?u=https-3A__library.unc.edu_wilson_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=tkJE1JdGvSoNb5i6NSRbF3z1n28dGeVJ4ogcFmpTpQo&s=e9r4LIAN87oWg7LLTrzui9bCYcCMX-8twYfh3y0I8tY&e=>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/8f6d3fb1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8591 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/8f6d3fb1/attachment.png>

From kate_bowers at harvard.edu  Thu Jun 18 09:55:08 2020
From: kate_bowers at harvard.edu (Bowers, Kate A.)
Date: Thu, 18 Jun 2020 13:55:08 +0000
Subject: [Archivesspace_Users_Group] Top container ranges
In-Reply-To: <A18BB140-256F-401A-988C-57C870A84387@harvard.edu>
References: <CC61910F-4534-47C6-B5D5-DF17A45BC7EC@harvard.edu>
 <BN7PR03MB3586080D9386B1CD8CEA14E5969B0@BN7PR03MB3586.namprd03.prod.outlook.com>
 <BBFFEDD9-5712-4240-8EB7-7262C615E827@harvard.edu>
 <A18BB140-256F-401A-988C-57C870A84387@harvard.edu>
Message-ID: <MN2PR07MB665326C6462CC8C06902C76D809B0@MN2PR07MB6653.namprd07.prod.outlook.com>

What Dave said.

From a practical standpoint, you have these options:

1.      Change the EAD pre-migration

2.      Change the data in Aspace

3.      Live with the data like that (your cost of cleaning v living with it may vary, but it is worth having the discussion. My repository had some issues we decided to live with and some we decided to fix.)

Option 1 works if you have consistency in the choices folks have made in finding aids. Unfortunately at Harvard, for some repositories text like ?Box 3-4? referred to a single box with the identifier 3-4, and not to ?Box 3 and Box 4?. Thus, we could not implement a single script that would work for all cases. We were also constrained by time and could not implement scripted solutions across sub-sets of our corpus. However?

Individual repositories did implement changes in their own ways. We had very few of these ?box range? type of finding aids, so I (OK, I know this is a really crude, sledgehammer type of method!)

?        Got the subset of finding aid that have this issue (granted, this can be some task in itself)

?        Put them in their own directory

?        Used regex find-and-replace (taking great care, of course to do no harm by accident) in either my favorite text editor or oXygen to find-and-replace all instances of the problem

?        Double-checked that they were all still valid

?        Spot-checked the results
Your mileage and access to a real programmer for stuff like this may vary.




From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Mayo, Dave
Sent: Thursday, June 18, 2020 9:37 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Also, specifically:


  1.  Using an XML database like eXist-db or BaseX with XPath/XQuery was invaluable when doing analysis of issues and of the impact of changes
  2.  One of the tools I wrote, the EAD Checker, is available online: https://eadchecker.lib.harvard.edu ? it doesn?t catch this specific issue, but it does catch a bunch of issues, some of which cause corrupted data rather than failure to import.

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Mayo, Dave" <dave_mayo at harvard.edu<mailto:dave_mayo at harvard.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 9:23 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

So, with the caveat that we put a lot of resources (a bunch of archivists? time, a full year of a full time developer (me!)), we had very solid results; I think remediating issues prior to import is almost always worth the expense of significant effort, particularly over a large corpus.

My main advice would be to be very, very careful about changes ? version your EADs, compare before and after scripts run, and in general be very systematic about how you find, report, and correct changes.

I don?t know if you?ve seen it, but Kate Bowers and I did a write-up of what we did during our migration ? it has links to a number of open source tools I wrote for doing this kind of work.  They?re a bit involved to get running, but they definitely work at basically any scale out there, and I?m happy to help people get started with them.  https://journal.code4lib.org/articles/12239<https://urldefense.proofpoint.com/v2/url?u=https-3A__journal.code4lib.org_articles_12239&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=MDvEtnIJJpOOfJzfDMsXF5u8QJ22oJqGB1UWDHD9Gmc&s=0ky2pQ2HoOxy34kpHGjThpBcFVj1ERUBf7LwbRZMMP4&e=>

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 9:12 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Thanks, Dave.  I guess I should have specified that changing the EAD isn?t a viable solution for us unless it?s automated. We do not plan to edit individual finding aids manually except in cases where the ranges aren?t regular.

If you?ve done this at Harvard, have there been any drawbacks? Anything we should be looking to avoid?

Thanks again,

Dawne


From: Mayo, Dave<mailto:dave_mayo at harvard.edu>
Sent: Thursday, June 18, 2020 9:04 AM
To: Archivesspace Users Group<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they?re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn?t mind going more into why that?s not a viable solution for you, it might help us provide better advice?

Either way, at 7000 finding aids, the solution would basically need to be automated ? if your box ranges are very regular (i.e. only single number or range, no ?3,4,7-10? or similar), it wouldn?t be too difficult ? split the range on ?-?, generate list of numbers, replace container with multiple containers.
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into ArchivesSpace and are wondering how other institutions have handled top container ranges.



For example, we have finding aids coded like this:



<c02><did><container type="box" label="Box">3-4</container><unittitle>Photographs</unittitle></did></c02>



This imports into ASpace just fine (yay!), but of course also creates a top container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding to:



<c02><did><container type="box" label="Box">3</container><unittitle>Photographs</unittitle></did></c02>



<c02><did><container type="box" label="Box">4 </container><unittitle>Photographs</unittitle></did></c02>



For several reasons, this is not a viable solution for us. Have other institutions figured out a way to deal with this issue that does not include editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image001.png at 01D5F200.0D957C80]<https://urldefense.proofpoint.com/v2/url?u=https-3A__library.unc.edu_wilson_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=tkJE1JdGvSoNb5i6NSRbF3z1n28dGeVJ4ogcFmpTpQo&s=e9r4LIAN87oWg7LLTrzui9bCYcCMX-8twYfh3y0I8tY&e=>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/123da85a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8591 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/123da85a/attachment.png>

From adrien_hilton at harvard.edu  Thu Jun 18 09:57:09 2020
From: adrien_hilton at harvard.edu (Hilton, Adrien)
Date: Thu, 18 Jun 2020 13:57:09 +0000
Subject: [Archivesspace_Users_Group] Top container ranges
In-Reply-To: <BBFFEDD9-5712-4240-8EB7-7262C615E827@harvard.edu>
References: <CC61910F-4534-47C6-B5D5-DF17A45BC7EC@harvard.edu>
 <BN7PR03MB3586080D9386B1CD8CEA14E5969B0@BN7PR03MB3586.namprd03.prod.outlook.com>
 <BBFFEDD9-5712-4240-8EB7-7262C615E827@harvard.edu>
Message-ID: <MN2PR07MB7229CF1E9145F2750A185EAF889B0@MN2PR07MB7229.namprd07.prod.outlook.com>

Hi Dawne,

I believe Yale created a script to break out container ranges: https://github.com/YaleArchivesSpace/xslt-files/blob/master/EAD_expand_top_container_ranges_prior_to_import.xsl

Best wishes,
Adrien

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Mayo, Dave
Sent: Thursday, June 18, 2020 9:23 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

So, with the caveat that we put a lot of resources (a bunch of archivists? time, a full year of a full time developer (me!)), we had very solid results; I think remediating issues prior to import is almost always worth the expense of significant effort, particularly over a large corpus.

My main advice would be to be very, very careful about changes ? version your EADs, compare before and after scripts run, and in general be very systematic about how you find, report, and correct changes.

I don?t know if you?ve seen it, but Kate Bowers and I did a write-up of what we did during our migration ? it has links to a number of open source tools I wrote for doing this kind of work.  They?re a bit involved to get running, but they definitely work at basically any scale out there, and I?m happy to help people get started with them.  https://journal.code4lib.org/articles/12239<https://urldefense.proofpoint.com/v2/url?u=https-3A__journal.code4lib.org_articles_12239&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=o7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU&m=vS6XDcZB0h_br-T8Gq3jqXX33ieGP-JCFkbS1dAbEHg&s=rQ8EQDYEp71yWvgaKUN296_jqyoIDw4gUtTneg1gC6w&e=>

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 9:12 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Thanks, Dave.  I guess I should have specified that changing the EAD isn?t a viable solution for us unless it?s automated. We do not plan to edit individual finding aids manually except in cases where the ranges aren?t regular.

If you?ve done this at Harvard, have there been any drawbacks? Anything we should be looking to avoid?

Thanks again,

Dawne


From: Mayo, Dave<mailto:dave_mayo at harvard.edu>
Sent: Thursday, June 18, 2020 9:04 AM
To: Archivesspace Users Group<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they?re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn?t mind going more into why that?s not a viable solution for you, it might help us provide better advice?

Either way, at 7000 finding aids, the solution would basically need to be automated ? if your box ranges are very regular (i.e. only single number or range, no ?3,4,7-10? or similar), it wouldn?t be too difficult ? split the range on ?-?, generate list of numbers, replace container with multiple containers.
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into ArchivesSpace and are wondering how other institutions have handled top container ranges.



For example, we have finding aids coded like this:



<c02><did><container type="box" label="Box">3-4</container><unittitle>Photographs</unittitle></did></c02>



This imports into ASpace just fine (yay!), but of course also creates a top container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding to:



<c02><did><container type="box" label="Box">3</container><unittitle>Photographs</unittitle></did></c02>



<c02><did><container type="box" label="Box">4 </container><unittitle>Photographs</unittitle></did></c02>



For several reasons, this is not a viable solution for us. Have other institutions figured out a way to deal with this issue that does not include editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image001.png at 01D5F200.0D957C80]<https://urldefense.proofpoint.com/v2/url?u=https-3A__library.unc.edu_wilson_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=tkJE1JdGvSoNb5i6NSRbF3z1n28dGeVJ4ogcFmpTpQo&s=e9r4LIAN87oWg7LLTrzui9bCYcCMX-8twYfh3y0I8tY&e=>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/bc7289c4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8590 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/bc7289c4/attachment.png>

From jsharp at hplct.org  Thu Jun 18 11:06:43 2020
From: jsharp at hplct.org (Sharp, Jennifer)
Date: Thu, 18 Jun 2020 15:06:43 +0000
Subject: [Archivesspace_Users_Group] Partially deleted repository
Message-ID: <MN2PR15MB27355499AC62622BBA1284A0DF9B0@MN2PR15MB2735.namprd15.prod.outlook.com>

Hi all,

Last year when we were considering joining ArchivesSpace, our IT department created a test repository for me. When we joined, they created our "real" repository, which I am still using. When I go to Manage Repositories (signed in as Admin), the test repository is still listed, but I am unable to view or edit it. I get a Record Not Found message. There is one, incomplete, finding aid in the test repository, that is still accessible via the public interface. Is there a way I can gain access to the test repository, or at least get rid of the incomplete finding aid?

Thanks,
Jennifer

---
Jennifer Sharp, MSI
Archivist, Hartford History Center
Hartford Public Library
jsharp at hplct.org<mailto:jsharp at hplct.org>
(o: 860.695.6332 Wed. only, currently)
c: 860.929.6915

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/1fd6416a/attachment.html>

From Jessica.Crouch at lyrasis.org  Thu Jun 18 16:04:26 2020
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Thu, 18 Jun 2020 20:04:26 +0000
Subject: [Archivesspace_Users_Group] Take a break with ArchivesSpace on
	Friday cancelled this week
Message-ID: <6A076B5D-058B-45C0-8043-65CA448DF734@lyrasis.org>

Dear ArchivesSpace Users,



LYRASIS will be observing Juneteenth tomorrow and staff will not be available for our standing Friday afternoon break.  We will resume our Friday breaks with ArchivesSpace next Friday, June 26th.



Thank you to everyone who joined us last week for a great chat.  We look forward to seeing you again next Friday.


Best,
Jessica

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/5d8415cc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 29072 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/5d8415cc/attachment.jpg>

From jsuszczynski at library.rochester.edu  Thu Jun 18 17:52:47 2020
From: jsuszczynski at library.rochester.edu (Suszczynski, Jeffrey)
Date: Thu, 18 Jun 2020 21:52:47 +0000
Subject: [Archivesspace_Users_Group] Editing display columns for Collection
	Management in AS
Message-ID: <MN2PR07MB623882F5B2EB2AD119C60367889B0@MN2PR07MB6238.namprd07.prod.outlook.com>

Hello, everyone -

We are trying to modify the columns that display in Collection Management (Browse ==> Collection Management ... We've looked in various places within the web admin interface, as well as the most often-edited configuration files on our AS server, but thus far have not been able to find where these columns are set.  For reference, here is a screen shot from our web admin interface:

[cid:image003.jpg at 01D64599.4674C960]

Does anyone know where we might make changes to this display?  Hopefully it's something simple that we overlooked - thanks in advance!

Jeff

Jeff Suszczynski
Web Developer, River Campus Libraries
University of Rochester


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/2edfc00c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 9162 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200618/2edfc00c/attachment.jpg>

From dawne_lucas at unc.edu  Fri Jun 19 07:58:20 2020
From: dawne_lucas at unc.edu (Lucas, Dawne Howard)
Date: Fri, 19 Jun 2020 11:58:20 +0000
Subject: [Archivesspace_Users_Group] Top container ranges
In-Reply-To: <MN2PR07MB665326C6462CC8C06902C76D809B0@MN2PR07MB6653.namprd07.prod.outlook.com>
References: <CC61910F-4534-47C6-B5D5-DF17A45BC7EC@harvard.edu>
 <BN7PR03MB3586080D9386B1CD8CEA14E5969B0@BN7PR03MB3586.namprd03.prod.outlook.com>
 <BBFFEDD9-5712-4240-8EB7-7262C615E827@harvard.edu>
 <A18BB140-256F-401A-988C-57C870A84387@harvard.edu>,
 <MN2PR07MB665326C6462CC8C06902C76D809B0@MN2PR07MB6653.namprd07.prod.outlook.com>
Message-ID: <BN7PR03MB3586307A674C34F9D86DFDBF96980@BN7PR03MB3586.namprd03.prod.outlook.com>

Thank you to everyone for the responses!

Best,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image001.png at 01D5F200.0D957C80]<https://library.unc.edu/wilson/>


From: Bowers, Kate A.<mailto:kate_bowers at harvard.edu>
Sent: Thursday, June 18, 2020 9:55 AM
To: Archivesspace Users Group<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

What Dave said.

>From a practical standpoint, you have these options:

  1.  Change the EAD pre-migration
  2.  Change the data in Aspace
  3.  Live with the data like that (your cost of cleaning v living with it may vary, but it is worth having the discussion. My repository had some issues we decided to live with and some we decided to fix.)

Option 1 works if you have consistency in the choices folks have made in finding aids. Unfortunately at Harvard, for some repositories text like ?Box 3-4? referred to a single box with the identifier 3-4, and not to ?Box 3 and Box 4?. Thus, we could not implement a single script that would work for all cases. We were also constrained by time and could not implement scripted solutions across sub-sets of our corpus. However?

Individual repositories did implement changes in their own ways. We had very few of these ?box range? type of finding aids, so I (OK, I know this is a really crude, sledgehammer type of method!)

  *   Got the subset of finding aid that have this issue (granted, this can be some task in itself)
  *   Put them in their own directory
  *   Used regex find-and-replace (taking great care, of course to do no harm by accident) in either my favorite text editor or oXygen to find-and-replace all instances of the problem
  *   Double-checked that they were all still valid
  *   Spot-checked the results
Your mileage and access to a real programmer for stuff like this may vary.




From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Mayo, Dave
Sent: Thursday, June 18, 2020 9:37 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Also, specifically:


  1.  Using an XML database like eXist-db or BaseX with XPath/XQuery was invaluable when doing analysis of issues and of the impact of changes
  2.  One of the tools I wrote, the EAD Checker, is available online: https://eadchecker.lib.harvard.edu ? it doesn?t catch this specific issue, but it does catch a bunch of issues, some of which cause corrupted data rather than failure to import.

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Mayo, Dave" <dave_mayo at harvard.edu<mailto:dave_mayo at harvard.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 9:23 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

So, with the caveat that we put a lot of resources (a bunch of archivists? time, a full year of a full time developer (me!)), we had very solid results; I think remediating issues prior to import is almost always worth the expense of significant effort, particularly over a large corpus.

My main advice would be to be very, very careful about changes ? version your EADs, compare before and after scripts run, and in general be very systematic about how you find, report, and correct changes.

I don?t know if you?ve seen it, but Kate Bowers and I did a write-up of what we did during our migration ? it has links to a number of open source tools I wrote for doing this kind of work.  They?re a bit involved to get running, but they definitely work at basically any scale out there, and I?m happy to help people get started with them.  https://journal.code4lib.org/articles/12239<https://urldefense.proofpoint.com/v2/url?u=https-3A__journal.code4lib.org_articles_12239&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=MDvEtnIJJpOOfJzfDMsXF5u8QJ22oJqGB1UWDHD9Gmc&s=0ky2pQ2HoOxy34kpHGjThpBcFVj1ERUBf7LwbRZMMP4&e=>

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 9:12 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Thanks, Dave.  I guess I should have specified that changing the EAD isn?t a viable solution for us unless it?s automated. We do not plan to edit individual finding aids manually except in cases where the ranges aren?t regular.

If you?ve done this at Harvard, have there been any drawbacks? Anything we should be looking to avoid?

Thanks again,

Dawne


From: Mayo, Dave<mailto:dave_mayo at harvard.edu>
Sent: Thursday, June 18, 2020 9:04 AM
To: Archivesspace Users Group<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they?re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn?t mind going more into why that?s not a viable solution for you, it might help us provide better advice?

Either way, at 7000 finding aids, the solution would basically need to be automated ? if your box ranges are very regular (i.e. only single number or range, no ?3,4,7-10? or similar), it wouldn?t be too difficult ? split the range on ?-?, generate list of numbers, replace container with multiple containers.
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into ArchivesSpace and are wondering how other institutions have handled top container ranges.



For example, we have finding aids coded like this:



<c02><did><container type="box" label="Box">3-4</container><unittitle>Photographs</unittitle></did></c02>



This imports into ASpace just fine (yay!), but of course also creates a top container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding to:



<c02><did><container type="box" label="Box">3</container><unittitle>Photographs</unittitle></did></c02>



<c02><did><container type="box" label="Box">4 </container><unittitle>Photographs</unittitle></did></c02>



For several reasons, this is not a viable solution for us. Have other institutions figured out a way to deal with this issue that does not include editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image001.png at 01D5F200.0D957C80]<https://urldefense.proofpoint.com/v2/url?u=https-3A__library.unc.edu_wilson_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=tkJE1JdGvSoNb5i6NSRbF3z1n28dGeVJ4ogcFmpTpQo&s=e9r4LIAN87oWg7LLTrzui9bCYcCMX-8twYfh3y0I8tY&e=>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200619/348b2ea1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8591 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200619/348b2ea1/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 8909C66936A54A598559DD23E6AE5CC2[189099678].png
Type: image/png
Size: 8588 bytes
Desc: 8909C66936A54A598559DD23E6AE5CC2[189099678].png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200619/348b2ea1/attachment-0001.png>

From andrew.morrison at bodleian.ox.ac.uk  Fri Jun 19 09:01:33 2020
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Fri, 19 Jun 2020 14:01:33 +0100
Subject: [Archivesspace_Users_Group] Top container ranges
In-Reply-To: <MN2PR07MB7229CF1E9145F2750A185EAF889B0@MN2PR07MB7229.namprd07.prod.outlook.com>
References: <CC61910F-4534-47C6-B5D5-DF17A45BC7EC@harvard.edu>
 <BN7PR03MB3586080D9386B1CD8CEA14E5969B0@BN7PR03MB3586.namprd03.prod.outlook.com>
 <BBFFEDD9-5712-4240-8EB7-7262C615E827@harvard.edu>
 <MN2PR07MB7229CF1E9145F2750A185EAF889B0@MN2PR07MB7229.namprd07.prod.outlook.com>
Message-ID: <7ac7aebc-d96c-e7b3-f8e9-1e44f7772962@bodleian.ox.ac.uk>

Just for completeness, another option is to create your own customized 
version of the EAD importer, by subclassing the EADConverter class 
<https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb> 
in a backend plugin. Then you'd just have another option in the 
drop-down in the import job form, and no need to pre-process.

But that would require both Ruby skills and an understanding of the 
ArchivesSpace data model for containers. I'd say even a complete novice 
with XSLT would find it easier to learning enough to tweak the Yale 
example that Adrien has given below. And it produces EAD you can view, 
validate and import on a test system to check the effects. We do both, 
but only use the plugin when changing the EAD has no effect (e.g. to 
alter how agents get roles, or the rules for whether a certain note is 
published.)

Andrew.


On 18/06/2020 14:57, Hilton, Adrien wrote:
>
> Hi Dawne,
>
> I believe Yale created a script to break out container ranges: 
> https://github.com/YaleArchivesSpace/xslt-files/blob/master/EAD_expand_top_container_ranges_prior_to_import.xsl
>
> Best wishes,
>
> Adrien
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org 
> <archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf 
> Of *Mayo, Dave
> *Sent:* Thursday, June 18, 2020 9:23 AM
> *To:* Archivesspace Users Group 
> <archivesspace_users_group at lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Top container ranges
>
> So, with the caveat that we put a lot of resources (a bunch of 
> archivists? time, a full year of a full time developer (me!)), we had 
> very solid results; I think remediating issues prior to import is 
> almost always worth the expense of significant effort, particularly 
> over a large corpus.
>
> My main advice would be to be very, very careful about changes ? 
> version your EADs, compare before and after scripts run, and in 
> general be very systematic about how you find, report, and correct 
> changes.
>
> I don?t know if you?ve seen it, but Kate Bowers and I did a write-up 
> of what we did during our migration ? it has links to a number of open 
> source tools I wrote for doing this kind of work.? They?re a bit 
> involved to get running, but they definitely work at basically any 
> scale out there, and I?m happy to help people get started with them. 
> https://journal.code4lib.org/articles/12239 
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__journal.code4lib.org_articles_12239&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=o7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU&m=vS6XDcZB0h_br-T8Gq3jqXX33ieGP-JCFkbS1dAbEHg&s=rQ8EQDYEp71yWvgaKUN296_jqyoIDw4gUtTneg1gC6w&e=>
>
> --
>
> Dave Mayo?(he/him)
>
> Senior Digital Library Software Engineer
> Harvard University > HUIT > LTS
>
> *From: *<archivesspace_users_group-bounces at lyralists.lyrasis.org 
> <mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on 
> behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu 
> <mailto:dawne_lucas at unc.edu>>
> *Reply-To: *Archivesspace Users Group 
> <archivesspace_users_group at lyralists.lyrasis.org 
> <mailto:archivesspace_users_group at lyralists.lyrasis.org>>
> *Date: *Thursday, June 18, 2020 at 9:12 AM
> *To: *Archivesspace Users Group 
> <archivesspace_users_group at lyralists.lyrasis.org 
> <mailto:archivesspace_users_group at lyralists.lyrasis.org>>
> *Subject: *Re: [Archivesspace_Users_Group] Top container ranges
>
> Thanks, Dave.? I guess I should have specified that changing the EAD 
> isn?t a viable solution for us /unless/ it?s automated. We do not plan 
> to edit individual finding aids manually except in cases where the 
> ranges aren?t regular.
>
> If you?ve done this at Harvard, have there been any drawbacks? 
> Anything we should be looking to avoid?
>
> Thanks again,
>
> Dawne
>
> *From: *Mayo, Dave <mailto:dave_mayo at harvard.edu>
> *Sent: *Thursday, June 18, 2020 9:04 AM
> *To: *Archivesspace Users Group 
> <mailto:archivesspace_users_group at lyralists.lyrasis.org>
> *Subject: *Re: [Archivesspace_Users_Group] Top container ranges
>
> The two options I see here are essentially:
>
> 1. Change the EAD
>
> 2. Change the containers after they?re ingested.
>
> Of the two, changing the EAD seems _/easier/_ to me; if you wouldn?t 
> mind going more into why that?s not a viable solution for you, it 
> might help us provide better advice?
>
>
> Either way, at 7000 finding aids, the solution would basically need to 
> be automated ? if your box ranges are very regular (i.e. only single 
> number or range, no ?3,4,7-10? or similar), it wouldn?t be too 
> difficult ? split the range on ?-?, generate list of numbers, replace 
> container with multiple containers.
>
> --
>
> Dave Mayo?(he/him)
>
> Senior Digital Library Software Engineer
> Harvard University > HUIT > LTS
>
> *From: *<archivesspace_users_group-bounces at lyralists.lyrasis.org 
> <mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on 
> behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu 
> <mailto:dawne_lucas at unc.edu>>
> *Reply-To: *Archivesspace Users Group 
> <archivesspace_users_group at lyralists.lyrasis.org 
> <mailto:archivesspace_users_group at lyralists.lyrasis.org>>
> *Date: *Thursday, June 18, 2020 at 8:13 AM
> *To: *Archivesspace Users Group 
> <archivesspace_users_group at lyralists.lyrasis.org 
> <mailto:archivesspace_users_group at lyralists.lyrasis.org>>
> *Subject: *[Archivesspace_Users_Group] Top container ranges
>
> Hi all,
>
> We are formulating a plan to import our 7000+ EAD finding aids into 
> ArchivesSpace and are wondering how other institutions have handled 
> top container ranges.
>
> For example, we have finding aids coded like this:
>
> <c02><did><container type="box" 
> label="Box">3-4</container><unittitle>Photographs</unittitle></did></c02>
>
> This imports into ASpace just fine (yay!), but of course also creates 
> a top container for Box 3-4 instead of Box 3 and Box 4 (boo!). We 
> assume this will be an issue later when we integrate with Aeon.
>
> The most obvious solution to this problem appears to be to change the 
> encoding to:
>
> <c02><did><container type="box" 
> label="Box">3</container><unittitle>Photographs</unittitle></did></c02>
>
> <c02><did><container type="box" label="Box">4 
> </container><unittitle>Photographs</unittitle></did></c02>
>
> For several reasons, this is not a viable solution for us. Have other 
> institutions figured out a way to deal with this issue that does not 
> include editing the EAD in individual finding aids?
>
> Thanks for your help,
>
> Dawne
>
> --
>
> *Dawne Howard Lucas (she/her/hers)*
>
> Technical Services Archivist
>
> Wilson Special Collections Library
>
> 200 South Road, CB #3926
>
> Chapel Hill, NC 27515
>
> The University of North Carolina at Chapel Hill
>
> P919-966-1776E dawne_lucas at unc.edu <mailto:dawne_lucas at unc.edu>
>
> cid:image001.png at 01D5F200.0D957C80 
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__library.unc.edu_wilson_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=tkJE1JdGvSoNb5i6NSRbF3z1n28dGeVJ4ogcFmpTpQo&s=e9r4LIAN87oWg7LLTrzui9bCYcCMX-8twYfh3y0I8tY&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/20200619/f38cf2d5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8590 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200619/f38cf2d5/attachment.png>

From andrew.morrison at bodleian.ox.ac.uk  Fri Jun 19 09:33:27 2020
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Fri, 19 Jun 2020 14:33:27 +0100
Subject: [Archivesspace_Users_Group] Editing display columns for
 Collection Management in AS
In-Reply-To: <MN2PR07MB623882F5B2EB2AD119C60367889B0@MN2PR07MB6238.namprd07.prod.outlook.com>
References: <MN2PR07MB623882F5B2EB2AD119C60367889B0@MN2PR07MB6238.namprd07.prod.outlook.com>
Message-ID: <66ec6f80-3e41-b4c7-a95e-9568777c1d6e@bodleian.ox.ac.uk>

The collection management columns are set up here:

https://github.com/archivesspace/archivesspace/blob/master/common/config/preference_defaults.rb#L91-L97

But that is not a file you can edit in a production instance of 
ArchivesSpace. It sets the defaults which can then be overridden. 
However, the staff interface does not include collection management 
columns in its UI for doing so.

If you have an urgent need to change the columns, you could probably use 
the backend API to override the defaults. I've never tried it myself, 
but it looks like you'd need to find the ID number of the preference 
record for the repository you want to change, download its JSON data 
structure, add those seven collection management browse columns 
reconfigured however you wish, and send it back. But you could only add 
the following: processing_funding_source, processors, publish 
(true/false), audit_info (created/last-modified).

Otherwise, you could raise an issue 
<https://archivesspace.atlassian.net/projects/ANW/issues/?filter=allopenissues> 
requesting future versions of ArchivesSpace either have the ability to 
customize collection management columns via the staff interface, or to 
change the defaults to include what you think is missing.

Andrew.


On 18/06/2020 22:52, Suszczynski, Jeffrey wrote:
>
> Hello, everyone ?
>
> We are trying to modify the columns that display in Collection 
> Management (Browse ? Collection Management ? We?ve looked in various 
> places within the web admin interface, as well as the most 
> often-edited configuration files on our AS server, but thus far have 
> not been able to find where these columns are set. ?For reference, 
> here is a screen shot from our web admin interface:
>
> Does anyone know where we might make changes to this display?? 
> Hopefully it?s something simple that we overlooked ? thanks in advance!
>
> Jeff
>
> Jeff Suszczynski
>
> Web Developer, River Campus Libraries
>
> University of Rochester
>
>
> _______________________________________________
> 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/20200619/46cf43d8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 9162 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200619/46cf43d8/attachment.jpg>

From blake.carver at lyrasis.org  Fri Jun 19 09:56:05 2020
From: blake.carver at lyrasis.org (Blake Carver)
Date: Fri, 19 Jun 2020 13:56:05 +0000
Subject: [Archivesspace_Users_Group] Partially deleted repository
In-Reply-To: <MN2PR15MB27355499AC62622BBA1284A0DF9B0@MN2PR15MB2735.namprd15.prod.outlook.com>
References: <MN2PR15MB27355499AC62622BBA1284A0DF9B0@MN2PR15MB2735.namprd15.prod.outlook.com>
Message-ID: <DM6PR22MB23094976EF40C33D0D154D0A9F980@DM6PR22MB2309.namprd22.prod.outlook.com>


I'm not 100% sure I follow... but... it sounds like something went bad in that repo. There's probably some errors in the archivesspace.out error log that could help pinpoint the problem.

You might want to start by forcing a full reindex first, sometimes that'll clear up strange problems like this. If that doesn't do the trick, set the loglevel to DEBUG and take a look for errors in the logs.
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Sharp, Jennifer <jsharp at hplct.org>
Sent: Thursday, June 18, 2020 11:06 AM
To: 'Archivesspace Users Group' <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Partially deleted repository


Hi all,



Last year when we were considering joining ArchivesSpace, our IT department created a test repository for me. When we joined, they created our ?real? repository, which I am still using. When I go to Manage Repositories (signed in as Admin), the test repository is still listed, but I am unable to view or edit it. I get a Record Not Found message. There is one, incomplete, finding aid in the test repository, that is still accessible via the public interface. Is there a way I can gain access to the test repository, or at least get rid of the incomplete finding aid?



Thanks,

Jennifer



---

Jennifer Sharp, MSI

Archivist, Hartford History Center

Hartford Public Library

jsharp at hplct.org<mailto:jsharp at hplct.org>

(o: 860.695.6332 Wed. only, currently)

c: 860.929.6915


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200619/181ab1d9/attachment.html>

From jsuszczynski at library.rochester.edu  Fri Jun 19 10:22:30 2020
From: jsuszczynski at library.rochester.edu (Suszczynski, Jeffrey)
Date: Fri, 19 Jun 2020 14:22:30 +0000
Subject: [Archivesspace_Users_Group] [EXTERNAL] Re: Editing display
 columns for Collection Management in AS
In-Reply-To: <66ec6f80-3e41-b4c7-a95e-9568777c1d6e@bodleian.ox.ac.uk>
References: <MN2PR07MB623882F5B2EB2AD119C60367889B0@MN2PR07MB6238.namprd07.prod.outlook.com>,
 <66ec6f80-3e41-b4c7-a95e-9568777c1d6e@bodleian.ox.ac.uk>
Message-ID: <MN2PR07MB62385F67F76B6DBFDF36835088980@MN2PR07MB6238.namprd07.prod.outlook.com>

Thank you, Andrew - this is most helpful!  I may investigate the API, depending on what I hear back from our staff, but will certainly add an issue to have the ability to customize those columns.

Thanks again, much appreciated!
jeff

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Andrew Morrison <andrew.morrison at bodleian.ox.ac.uk>
Sent: Friday, June 19, 2020 9:33 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] Editing display columns for Collection Management in AS


The collection management columns are set up here:

https://github.com/archivesspace/archivesspace/blob/master/common/config/preference_defaults.rb#L91-L97<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_archivesspace_blob_master_common_config_preference-5Fdefaults.rb-23L91-2DL97&d=DwMD-g&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=5Lyy5Q6URKF-FYd-MMPgRcVtIpCrHnHsWhGjyxojRgbFJAQGHSSkwsPgEHCArFy1&m=rxG2AMBrz8KrkCgaDqKAK_Lb1VzYpyDut2zYdfYnY6o&s=MscH_gPEnqnGcDJAuj7oY5Et20M71mlOmYcQQcChHjU&e=>

But that is not a file you can edit in a production instance of ArchivesSpace. It sets the defaults which can then be overridden. However, the staff interface does not include collection management columns in its UI for doing so.

If you have an urgent need to change the columns, you could probably use the backend API to override the defaults. I've never tried it myself, but it looks like you'd need to find the ID number of the preference record for the repository you want to change, download its JSON data structure, add those seven collection management browse columns reconfigured however you wish, and send it back. But you could only add the following: processing_funding_source, processors, publish (true/false), audit_info (created/last-modified).

Otherwise, you could raise an issue<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_projects_ANW_issues_-3Ffilter-3Dallopenissues&d=DwMD-g&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=5Lyy5Q6URKF-FYd-MMPgRcVtIpCrHnHsWhGjyxojRgbFJAQGHSSkwsPgEHCArFy1&m=rxG2AMBrz8KrkCgaDqKAK_Lb1VzYpyDut2zYdfYnY6o&s=H9CAdF-3FnZ8Yt8JCgqYorex8DLlI2qtFWUl0WPoqgI&e=> requesting future versions of ArchivesSpace either have the ability to customize collection management columns via the staff interface, or to change the defaults to include what you think is missing.

Andrew.


On 18/06/2020 22:52, Suszczynski, Jeffrey wrote:

Hello, everyone ?



We are trying to modify the columns that display in Collection Management (Browse ==> Collection Management ? We?ve looked in various places within the web admin interface, as well as the most often-edited configuration files on our AS server, but thus far have not been able to find where these columns are set.  For reference, here is a screen shot from our web admin interface:



[cid:part2.33012B9E.DD62A8D3 at bodleian.ox.ac.uk]



Does anyone know where we might make changes to this display?  Hopefully it?s something simple that we overlooked ? thanks in advance!



Jeff



Jeff Suszczynski

Web Developer, River Campus Libraries

University of Rochester







_______________________________________________
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=DwMD-g&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=5Lyy5Q6URKF-FYd-MMPgRcVtIpCrHnHsWhGjyxojRgbFJAQGHSSkwsPgEHCArFy1&m=rxG2AMBrz8KrkCgaDqKAK_Lb1VzYpyDut2zYdfYnY6o&s=3S00OBgaKiyn5A5xK9L7z8HarN15ECbfnuxPMc4fYEI&e=>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200619/6566e187/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 9162 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200619/6566e187/attachment.jpg>

From andrew.morrison at bodleian.ox.ac.uk  Fri Jun 19 13:46:08 2020
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Fri, 19 Jun 2020 18:46:08 +0100
Subject: [Archivesspace_Users_Group] Partially deleted repository
In-Reply-To: <DM6PR22MB23094976EF40C33D0D154D0A9F980@DM6PR22MB2309.namprd22.prod.outlook.com>
References: <MN2PR15MB27355499AC62622BBA1284A0DF9B0@MN2PR15MB2735.namprd15.prod.outlook.com>
 <DM6PR22MB23094976EF40C33D0D154D0A9F980@DM6PR22MB2309.namprd22.prod.outlook.com>
Message-ID: <47f3c675-8f0c-5920-97cc-714b13ca5c79@bodleian.ox.ac.uk>

On a development system, deleting a repository via the staff interface 
causes the indexer to log errors continually when it tries to process 
resource records within, because it can no longer resolve the parent 
repository. Shutting down all services and doing a full re-index stops 
the errors, but it may be different on a production system. I have 
submitted a possible fix 
<https://github.com/archivesspace/archivesspace/pull/1929> for potential 
inclusion in a future release of ArchivesSpace.


Andrew.



On 19/06/2020 14:56, Blake Carver wrote:
>
> I'm not 100% sure I follow... but... it sounds like something went bad 
> in that repo. There's probably some errors in the archivesspace.out 
> error log that could help pinpoint the problem.
>
> You might want to start by forcing a full reindex first, sometimes 
> that'll clear up strange problems like this. If that doesn't do the 
> trick, set the loglevel to DEBUG and take a look for errors in the logs.
> ------------------------------------------------------------------------
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org 
> <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of 
> Sharp, Jennifer <jsharp at hplct.org>
> *Sent:* Thursday, June 18, 2020 11:06 AM
> *To:* 'Archivesspace Users Group' 
> <archivesspace_users_group at lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] Partially deleted repository
>
> Hi all,
>
> Last year when we were considering joining ArchivesSpace, our IT 
> department created a test repository for me. When we joined, they 
> created our ?real? repository, which I am still using. When I go to 
> Manage Repositories (signed in as Admin), the test repository is still 
> listed, but I am unable to view or edit it. I get a Record Not Found 
> message. There is one, incomplete, finding aid in the test repository, 
> that is still accessible via the public interface. Is there a way I 
> can gain access to the test repository, or at least get rid of the 
> incomplete finding aid?
>
> Thanks,
>
> Jennifer
>
> ---
>
> Jennifer Sharp, MSI
>
> Archivist, Hartford History Center
>
> Hartford Public Library
>
> jsharp at hplct.org <mailto:jsharp at hplct.org>
>
> (o: 860.695.6332 Wed. only, currently)
>
> c: 860.929.6915
>
>
> _______________________________________________
> 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/20200619/11f46599/attachment.html>

From jsharp at hplct.org  Fri Jun 19 16:35:33 2020
From: jsharp at hplct.org (Sharp, Jennifer)
Date: Fri, 19 Jun 2020 20:35:33 +0000
Subject: [Archivesspace_Users_Group] Partially deleted repository
In-Reply-To: <47f3c675-8f0c-5920-97cc-714b13ca5c79@bodleian.ox.ac.uk>
References: <MN2PR15MB27355499AC62622BBA1284A0DF9B0@MN2PR15MB2735.namprd15.prod.outlook.com>
 <DM6PR22MB23094976EF40C33D0D154D0A9F980@DM6PR22MB2309.namprd22.prod.outlook.com>
 <47f3c675-8f0c-5920-97cc-714b13ca5c79@bodleian.ox.ac.uk>
Message-ID: <MN2PR15MB2735D17C95EC780D12EAC4F1DF980@MN2PR15MB2735.namprd15.prod.outlook.com>

Thanks, Blake and Andrew. I wrote to IT earlier asking them to do a re-index. We'll see what happens!

Jennifer

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Andrew Morrison
Sent: Friday, June 19, 2020 1:46 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Partially deleted repository


On a development system, deleting a repository via the staff interface causes the indexer to log errors continually when it tries to process resource records within, because it can no longer resolve the parent repository. Shutting down all services and doing a full re-index stops the errors, but it may be different on a production system. I have submitted a possible fix<https://github.com/archivesspace/archivesspace/pull/1929> for potential inclusion in a future release of ArchivesSpace.



Andrew.




On 19/06/2020 14:56, Blake Carver wrote:

I'm not 100% sure I follow... but... it sounds like something went bad in that repo. There's probably some errors in the archivesspace.out error log that could help pinpoint the problem.

You might want to start by forcing a full reindex first, sometimes that'll clear up strange problems like this. If that doesn't do the trick, set the loglevel to DEBUG and take a look for errors in the logs.
________________________________
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><mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Sharp, Jennifer <jsharp at hplct.org><mailto:jsharp at hplct.org>
Sent: Thursday, June 18, 2020 11:06 AM
To: 'Archivesspace Users Group' <archivesspace_users_group at lyralists.lyrasis.org><mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Partially deleted repository


Hi all,



Last year when we were considering joining ArchivesSpace, our IT department created a test repository for me. When we joined, they created our "real" repository, which I am still using. When I go to Manage Repositories (signed in as Admin), the test repository is still listed, but I am unable to view or edit it. I get a Record Not Found message. There is one, incomplete, finding aid in the test repository, that is still accessible via the public interface. Is there a way I can gain access to the test repository, or at least get rid of the incomplete finding aid?



Thanks,

Jennifer



---

Jennifer Sharp, MSI

Archivist, Hartford History Center

Hartford Public Library

jsharp at hplct.org<mailto:jsharp at hplct.org>

(o: 860.695.6332 Wed. only, currently)

c: 860.929.6915





_______________________________________________

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

CAUTION: This email originated from outside of the organization. Do not click links, open attachments, or provide sensitive information unless you recognize the sender and know the content/source is safe.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200619/6858ddf7/attachment.html>

From Jessica.Crouch at lyrasis.org  Mon Jun 22 10:10:28 2020
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Mon, 22 Jun 2020 14:10:28 +0000
Subject: [Archivesspace_Users_Group] Webinar Announcement: Is It Roy E.
 Harrington or Roy S. Harrington?: How to Make Technology Work for You In an
 ArchivesSpace Data Cleanup Project
Message-ID: <336EBC79-0516-419B-A861-DE9DA06A74C8@lyrasis.org>

Dear ArchivesSpace Users,

ArchivesSpace will be offering another webinar focusing on ArchivesSpace data cleanup projects that can be accomplished in a work from home environment on Wednesday, July 8, at 2pm ET. Most of us are doing our jobs under much different conditions than usual. As a browser-based system you can access from anywhere, ArchivesSpace is a tool that can be used when working remotely and many ArchivesSpace users are finding themselves executing large scale data cleanup projects that have only recently been prioritized.

Title:  Is It Roy E. Harrington or Roy S. Harrington?: How to Make Technology Work for You In an ArchivesSpace Data Cleanup Project
When: July 8, 2020
Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00pm PT)
Where: Zoom
Registration: https://lyrasis.zoom.us/webinar/register/WN_T5x0GFR8QHicozJwCsm05Q<https://urldefense.proofpoint.com/v2/url?u=https-3A__lyrasis.zoom.us_webinar_register_WN-5FT5x0GFR8QHicozJwCsm05Q&d=DwMGaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=_iPtfI-oh6gC_Z6tmJI1y6Av--PwfhAF74rQK6DKyO4&m=rkbdEOey751wPdeeiUaVeHfOfTPgjCT1n8tjVawFJks&s=5stg63T_ua3Z9Cnm95lhMKrTuY25DerdLU61CuIVDSY&e=>
In order to provide a secure webinar experience and ensure adequate space in our Zoom environment, registration is now required for our webinars.  Our webinars continue to be free and open to anyone using or interested in ArchivesSpace.
Webinar description:
This webinar will be recorded and made available on the ArchivesSpace YouTube channel.
Three processing archivists from the Rockefeller Archive Center will discuss collaborative approaches to mass data cleanup in ArchivesSpace. Presenters will share how they planned, reassessed, and executed various automated and manual processes for enhancing the quality of their institution?s descriptive data. This data includes agent records, dates, and access restriction notes. This discussion is based off of the RAC ArchivesSpace Cleanup blog series<https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.rockarch.org_archivesspace-2Dclean-2Dup-2Dan-2Doutline&d=DwMGaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=_iPtfI-oh6gC_Z6tmJI1y6Av--PwfhAF74rQK6DKyO4&m=rkbdEOey751wPdeeiUaVeHfOfTPgjCT1n8tjVawFJks&s=JIymM-sIL0iKj421Nbo-4zA_l-JTWQUbMHdmXt-vxvc&e=>.
Webinar presenters:
Amy Berish is an Archivist at the Rockefeller Archive Center where she works as a member of the Processing team. Aside from processing incoming collections, she also contributes to various digital projects. Amy holds a Masters in Library and Information Science from the University of Pittsburgh.

Katie Martin is an Assistant Archivist at the Rockefeller Archive Center where she processes collections of the Ford Foundation and works on projects with the digital team. She earned degrees in History and American Studies from Purdue University and received her MLS with a specialization in archives and records management from Indiana University.

Darren Young is an Assistant Archivist at the Rockefeller Archive Center where he processes collections of the Ford Foundation and collaborates with the digital team on select projects. He earned a BA degree with majors in English Literature and History at the University of Connecticut and received his MLIS with a concentration in Archives Management from Simmons College (now Simmons University).

Who should attend:

While this webinar will focus on projects that can be undertaken in a work from home environment, this webinar will be useful to any archivist focusing on data cleanup in ArchivesSpace, those needing to export data out of ArchivesSpace and archivists working with legacy data.

Questions?

Contact Jessica at jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org> if you have questions about this webinar or our other online events.


Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200622/081e44a5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 8536 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200622/081e44a5/attachment-0001.jpg>

From ltang5 at msu.edu  Mon Jun 22 12:12:12 2020
From: ltang5 at msu.edu (Tang, Lydia)
Date: Mon, 22 Jun 2020 16:12:12 +0000
Subject: [Archivesspace_Users_Group] Draft Collection Organization
 Usability Report call for comments
Message-ID: <A031AAFD-6CC3-414C-B821-FFAE2CC54FDD@msu.edu>

Hello, everyone!
This is a reminder to please provide the User Advisory Council?s Usability Subteam<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Farchivesspace.atlassian.net%2Fwiki%2Fspaces%2FAC%2Fpages%2F893714474%2FUsability__%3B!!HXCxUKc!mJrlJt0SkEeF4zUdDbfjRjqoNEvnjC-5osf6c1PmgMXUl_JoEVG59iLubkFUKN7Vvw%24&data=01%7C01%7Cltang5%40msu.edu%7C985ce7db9e044261b5c608d80e273c51%7C22177130642f41d9921174237ad5687d%7C0&sdata=GnaIQyk2UMl5C4Lh%2Fyl97hnOrRlf3CgoXpjpRZ1rdO8%3D&reserved=0> with feedback on our draft report<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1laL3pkQKCJ83RXu2OzOFQe_h6BLdxzOAiw-agMauf9U%2Fedit%3Fusp%3Dsharing__%3B!!HXCxUKc!mJrlJt0SkEeF4zUdDbfjRjqoNEvnjC-5osf6c1PmgMXUl_JoEVG59iLubkGZWGso-w%24&data=01%7C01%7Cltang5%40msu.edu%7C985ce7db9e044261b5c608d80e273c51%7C22177130642f41d9921174237ad5687d%7C0&sdata=2DEjbS4hvmJNe%2FRNH%2BAd92iuVAwXVfLBQgVU3EMO9ss%3D&reserved=0> on the Collection Organization view of the PUI. To help gather feedback, we?ve created an informal survey<https://forms.gle/4BEmfCVb2851G9ZF9>. Please provide your feedback by the end of this month!
Thanks for your help and feedback!
Lydia Tang, Kate Blalack, Lori Dedeyan, Brittany Newberry, Julia Novakovic, and Althea Topek
Usability Subteam

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Tang, Lydia" <ltang5 at msu.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, June 11, 2020 at 12:48 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Draft Collection Organization Usability Report call for comments

Hello, everyone!
In the interest of continuing to evolve ArchivesSpace?s public user interface to be as user-friendly as possible, User Advisory Council?s Usability Subteam<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Farchivesspace.atlassian.net%2Fwiki%2Fspaces%2FAC%2Fpages%2F893714474%2FUsability__%3B!!HXCxUKc!mJrlJt0SkEeF4zUdDbfjRjqoNEvnjC-5osf6c1PmgMXUl_JoEVG59iLubkFUKN7Vvw%24&data=01%7C01%7Cltang5%40msu.edu%7C985ce7db9e044261b5c608d80e273c51%7C22177130642f41d9921174237ad5687d%7C0&sdata=GnaIQyk2UMl5C4Lh%2Fyl97hnOrRlf3CgoXpjpRZ1rdO8%3D&reserved=0> has prepared this draft report<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1laL3pkQKCJ83RXu2OzOFQe_h6BLdxzOAiw-agMauf9U%2Fedit%3Fusp%3Dsharing__%3B!!HXCxUKc!mJrlJt0SkEeF4zUdDbfjRjqoNEvnjC-5osf6c1PmgMXUl_JoEVG59iLubkGZWGso-w%24&data=01%7C01%7Cltang5%40msu.edu%7C985ce7db9e044261b5c608d80e273c51%7C22177130642f41d9921174237ad5687d%7C0&sdata=2DEjbS4hvmJNe%2FRNH%2BAd92iuVAwXVfLBQgVU3EMO9ss%3D&reserved=0> which identifies common themes from user-submitted feature request tickets, existing usability studies, and compiles examples of customizations that repositories have taken to address these topics. We hope to hold a webinar or open call in the future to continue to gather community feedback on these ideas. There are many possible paths forward, so the goal is to build consensus on a desired direction to continue to evolve the Collection Organization view of the PUI.

We welcome your feedback and suggestions. Please feel free to comment in this doc or email me at ltang5 at msu.edu<mailto:ltang5 at msu.edu> by the end of this month.

Thanks for your help and feedback!

Lydia Tang, Kate Blalack, Lori Dedeyan, Brittanyt Newberry, Julia Novakovic, and Althea Topek

Usability Subteam



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200622/75d7bc7a/attachment.html>

From jhack at mcdaniel.edu  Mon Jun 22 14:09:12 2020
From: jhack at mcdaniel.edu (Janet Hack)
Date: Mon, 22 Jun 2020 18:09:12 +0000
Subject: [Archivesspace_Users_Group] Adding a link to a logo in ArchivesSpace
Message-ID: <MN2PR04MB566142B731FD114D655C2EE5CE970@MN2PR04MB5661.namprd04.prod.outlook.com>

I would like to add a link to our main Archives website (which is not ArchivesSpace). I would prefer to add the link to the ASpace header, either to the logo or the branding name. I have looked through the online documentation but have not yet found out how to do this. I can change the logo, but I can't make it link anywhere.

Any suggestions would be greatly appreciated.

  - Janet

-----------------
Janet Hack
Science and Online Technologies Librarian
Hoover Library | McDaniel College
2 College Hill | Westminster, MD 21157-4390
410-857-2283 | jhack at mcdaniel.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200622/57f4c530/attachment.html>

From blake.carver at lyrasis.org  Mon Jun 22 14:47:13 2020
From: blake.carver at lyrasis.org (Blake Carver)
Date: Mon, 22 Jun 2020 18:47:13 +0000
Subject: [Archivesspace_Users_Group] Adding a link to a logo in
	ArchivesSpace
In-Reply-To: <MN2PR04MB566142B731FD114D655C2EE5CE970@MN2PR04MB5661.namprd04.prod.outlook.com>
References: <MN2PR04MB566142B731FD114D655C2EE5CE970@MN2PR04MB5661.namprd04.prod.outlook.com>
Message-ID: <DM6PR22MB2309B36A7FCC2C0BD196A8999F970@DM6PR22MB2309.namprd22.prod.outlook.com>

You should be able to change up the " public/views/shared/_header.html.erb "

https://github.com/archivesspace/archivesspace/blob/master/public/app/views/shared/_header.html.erb#L14

Something like

<div class="col-sm-3 hidden-xs"><a href="https://mcdaniel.edu"><img class="logo" src="<%= asset_path(AppConfig[:pui_branding_img]) %>" alt="Back to McDaniel College Home" /></a></div>
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Janet Hack <jhack at mcdaniel.edu>
Sent: Monday, June 22, 2020 2:09 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Adding a link to a logo in ArchivesSpace

I would like to add a link to our main Archives website (which is not ArchivesSpace). I would prefer to add the link to the ASpace header, either to the logo or the branding name. I have looked through the online documentation but have not yet found out how to do this. I can change the logo, but I can't make it link anywhere.

Any suggestions would be greatly appreciated.

  - Janet

-----------------
Janet Hack
Science and Online Technologies Librarian
Hoover Library | McDaniel College
2 College Hill | Westminster, MD 21157-4390
410-857-2283 | jhack at mcdaniel.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200622/e04619b5/attachment.html>

From jhack at mcdaniel.edu  Mon Jun 22 14:54:40 2020
From: jhack at mcdaniel.edu (Janet Hack)
Date: Mon, 22 Jun 2020 18:54:40 +0000
Subject: [Archivesspace_Users_Group] Adding a link to a logo
	in	ArchivesSpace
In-Reply-To: <DM6PR22MB2309B36A7FCC2C0BD196A8999F970@DM6PR22MB2309.namprd22.prod.outlook.com>
References: <MN2PR04MB566142B731FD114D655C2EE5CE970@MN2PR04MB5661.namprd04.prod.outlook.com>,
 <DM6PR22MB2309B36A7FCC2C0BD196A8999F970@DM6PR22MB2309.namprd22.prod.outlook.com>
Message-ID: <MN2PR04MB5661FC86FACDA078D3D16F42CE970@MN2PR04MB5661.namprd04.prod.outlook.com>

Thank you for the quick response.

I don't see a "public" directory in our archivesspace directory. I am attaching a screenshot of the directory structure that I see.

Could this mean that I don't have permission to edit that directory, in which case I would need to contact my IT department to see if they will allow me access?

Thanks again,

  - Janet

-----------------
Janet Hack
Science and Online Technologies Librarian
Hoover Library | McDaniel College
2 College Hill | Westminster, MD 21157-4390
410-857-2283 | jhack at mcdaniel.edu
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Blake Carver <blake.carver at lyrasis.org>
Sent: Monday, June 22, 2020 2:47 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Adding a link to a logo in ArchivesSpace


CAUTION: This email originated from a non-McDaniel address. Do not click links or open attachments unless you recognize the sender and know the content is safe.

You should be able to change up the " public/views/shared/_header.html.erb "

https://github.com/archivesspace/archivesspace/blob/master/public/app/views/shared/_header.html.erb#L14

Something like

<div class="col-sm-3 hidden-xs"><a href="https://mcdaniel.edu"><img class="logo" src="<%= asset_path(AppConfig[:pui_branding_img]) %>" alt="Back to McDaniel College Home" /></a></div>
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Janet Hack <jhack at mcdaniel.edu>
Sent: Monday, June 22, 2020 2:09 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Adding a link to a logo in ArchivesSpace

I would like to add a link to our main Archives website (which is not ArchivesSpace). I would prefer to add the link to the ASpace header, either to the logo or the branding name. I have looked through the online documentation but have not yet found out how to do this. I can change the logo, but I can't make it link anywhere.

Any suggestions would be greatly appreciated.

  - Janet

-----------------
Janet Hack
Science and Online Technologies Librarian
Hoover Library | McDaniel College
2 College Hill | Westminster, MD 21157-4390
410-857-2283 | jhack at mcdaniel.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200622/66266e3d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: archivesspace.png
Type: image/png
Size: 23316 bytes
Desc: archivesspace.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200622/66266e3d/attachment.png>

From blake.carver at lyrasis.org  Mon Jun 22 15:03:41 2020
From: blake.carver at lyrasis.org (Blake Carver)
Date: Mon, 22 Jun 2020 19:03:41 +0000
Subject: [Archivesspace_Users_Group] Adding a link to a
	logo	in	ArchivesSpace
In-Reply-To: <MN2PR04MB5661FC86FACDA078D3D16F42CE970@MN2PR04MB5661.namprd04.prod.outlook.com>
References: <MN2PR04MB566142B731FD114D655C2EE5CE970@MN2PR04MB5661.namprd04.prod.outlook.com>,
 <DM6PR22MB2309B36A7FCC2C0BD196A8999F970@DM6PR22MB2309.namprd22.prod.outlook.com>,
 <MN2PR04MB5661FC86FACDA078D3D16F42CE970@MN2PR04MB5661.namprd04.prod.outlook.com>
Message-ID: <DM6PR22MB2309C49077B4DDCB73671B829F970@DM6PR22MB2309.namprd22.prod.outlook.com>

Try
./plugins/local/public/views/shared/_header.html.erb



________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Janet Hack <jhack at mcdaniel.edu>
Sent: Monday, June 22, 2020 2:54 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Adding a link to a logo in ArchivesSpace

Thank you for the quick response.

I don't see a "public" directory in our archivesspace directory. I am attaching a screenshot of the directory structure that I see.

Could this mean that I don't have permission to edit that directory, in which case I would need to contact my IT department to see if they will allow me access?

Thanks again,

  - Janet

-----------------
Janet Hack
Science and Online Technologies Librarian
Hoover Library | McDaniel College
2 College Hill | Westminster, MD 21157-4390
410-857-2283 | jhack at mcdaniel.edu
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Blake Carver <blake.carver at lyrasis.org>
Sent: Monday, June 22, 2020 2:47 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Adding a link to a logo in ArchivesSpace


CAUTION: This email originated from a non-McDaniel address. Do not click links or open attachments unless you recognize the sender and know the content is safe.

You should be able to change up the " public/views/shared/_header.html.erb "

https://github.com/archivesspace/archivesspace/blob/master/public/app/views/shared/_header.html.erb#L14

Something like

<div class="col-sm-3 hidden-xs"><a href="https://mcdaniel.edu"><img class="logo" src="<%= asset_path(AppConfig[:pui_branding_img]) %>" alt="Back to McDaniel College Home" /></a></div>
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Janet Hack <jhack at mcdaniel.edu>
Sent: Monday, June 22, 2020 2:09 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Adding a link to a logo in ArchivesSpace

I would like to add a link to our main Archives website (which is not ArchivesSpace). I would prefer to add the link to the ASpace header, either to the logo or the branding name. I have looked through the online documentation but have not yet found out how to do this. I can change the logo, but I can't make it link anywhere.

Any suggestions would be greatly appreciated.

  - Janet

-----------------
Janet Hack
Science and Online Technologies Librarian
Hoover Library | McDaniel College
2 College Hill | Westminster, MD 21157-4390
410-857-2283 | jhack at mcdaniel.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200622/49a2c8e5/attachment.html>

From jhack at mcdaniel.edu  Mon Jun 22 15:56:44 2020
From: jhack at mcdaniel.edu (Janet Hack)
Date: Mon, 22 Jun 2020 19:56:44 +0000
Subject: [Archivesspace_Users_Group] Adding a link to
	a	logo	in	ArchivesSpace
In-Reply-To: <DM6PR22MB2309C49077B4DDCB73671B829F970@DM6PR22MB2309.namprd22.prod.outlook.com>
References: <MN2PR04MB566142B731FD114D655C2EE5CE970@MN2PR04MB5661.namprd04.prod.outlook.com>,
 <DM6PR22MB2309B36A7FCC2C0BD196A8999F970@DM6PR22MB2309.namprd22.prod.outlook.com>,
 <MN2PR04MB5661FC86FACDA078D3D16F42CE970@MN2PR04MB5661.namprd04.prod.outlook.com>,
 <DM6PR22MB2309C49077B4DDCB73671B829F970@DM6PR22MB2309.namprd22.prod.outlook.com>
Message-ID: <MN2PR04MB5661C5299E943382182B3D44CE970@MN2PR04MB5661.namprd04.prod.outlook.com>

That looks like it is getting me in the right direction. Thanks.

   - Janet

-----------------
Janet Hack
Science and Online Technologies Librarian
Hoover Library | McDaniel College
2 College Hill | Westminster, MD 21157-4390
410-857-2283 | jhack at mcdaniel.edu
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Blake Carver <blake.carver at lyrasis.org>
Sent: Monday, June 22, 2020 3:03 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Adding a link to a logo in ArchivesSpace


CAUTION: This email originated from a non-McDaniel address. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Try
./plugins/local/public/views/shared/_header.html.erb



________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Janet Hack <jhack at mcdaniel.edu>
Sent: Monday, June 22, 2020 2:54 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Adding a link to a logo in ArchivesSpace

Thank you for the quick response.

I don't see a "public" directory in our archivesspace directory. I am attaching a screenshot of the directory structure that I see.

Could this mean that I don't have permission to edit that directory, in which case I would need to contact my IT department to see if they will allow me access?

Thanks again,

  - Janet

-----------------
Janet Hack
Science and Online Technologies Librarian
Hoover Library | McDaniel College
2 College Hill | Westminster, MD 21157-4390
410-857-2283 | jhack at mcdaniel.edu
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Blake Carver <blake.carver at lyrasis.org>
Sent: Monday, June 22, 2020 2:47 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Adding a link to a logo in ArchivesSpace


CAUTION: This email originated from a non-McDaniel address. Do not click links or open attachments unless you recognize the sender and know the content is safe.

You should be able to change up the " public/views/shared/_header.html.erb "

https://github.com/archivesspace/archivesspace/blob/master/public/app/views/shared/_header.html.erb#L14

Something like

<div class="col-sm-3 hidden-xs"><a href="https://mcdaniel.edu"><img class="logo" src="<%= asset_path(AppConfig[:pui_branding_img]) %>" alt="Back to McDaniel College Home" /></a></div>
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Janet Hack <jhack at mcdaniel.edu>
Sent: Monday, June 22, 2020 2:09 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Adding a link to a logo in ArchivesSpace

I would like to add a link to our main Archives website (which is not ArchivesSpace). I would prefer to add the link to the ASpace header, either to the logo or the branding name. I have looked through the online documentation but have not yet found out how to do this. I can change the logo, but I can't make it link anywhere.

Any suggestions would be greatly appreciated.

  - Janet

-----------------
Janet Hack
Science and Online Technologies Librarian
Hoover Library | McDaniel College
2 College Hill | Westminster, MD 21157-4390
410-857-2283 | jhack at mcdaniel.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200622/c3cb2048/attachment.html>

From reesj at mail.nlm.nih.gov  Mon Jun 22 16:44:38 2020
From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E])
Date: Mon, 22 Jun 2020 20:44:38 +0000
Subject: [Archivesspace_Users_Group] Top container ranges
In-Reply-To: <BN7PR03MB3586307A674C34F9D86DFDBF96980@BN7PR03MB3586.namprd03.prod.outlook.com>
References: <CC61910F-4534-47C6-B5D5-DF17A45BC7EC@harvard.edu>
 <BN7PR03MB3586080D9386B1CD8CEA14E5969B0@BN7PR03MB3586.namprd03.prod.outlook.com>
 <BBFFEDD9-5712-4240-8EB7-7262C615E827@harvard.edu>
 <A18BB140-256F-401A-988C-57C870A84387@harvard.edu>,
 <MN2PR07MB665326C6462CC8C06902C76D809B0@MN2PR07MB6653.namprd07.prod.outlook.com>
 <BN7PR03MB3586307A674C34F9D86DFDBF96980@BN7PR03MB3586.namprd03.prod.outlook.com>
Message-ID: <DM6PR09MB58161535A5EF7A9CA42BDE26C8970@DM6PR09MB5816.namprd09.prod.outlook.com>

Hi Dawne,

I'm doing pretty much what Kate laid out to edit source EAD, for all sorts of different container conventions. You can see my ever-growing punch list at https://github.com/John-Rees/aspace-migrations/issues?q=is%3Aopen+is%3Aissue+milestone%3Amigrations

I use a variety of regex and xsls to solve various problems.

John


John P. Rees
Archivist and Digital Resources Manager
History of Medicine Division
National Library of Medicine
301-827-4510
Teleworking M-F 8:00AM - 4:30PM each day until further notice


From: Lucas, Dawne Howard <dawne_lucas at unc.edu>
Sent: Friday, June 19, 2020 6:58 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Thank you to everyone for the responses!

Best,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image002.png at 01D648AC.08659C60]<https://library.unc.edu/wilson/>


From: Bowers, Kate A.<mailto:kate_bowers at harvard.edu>
Sent: Thursday, June 18, 2020 9:55 AM
To: Archivesspace Users Group<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

What Dave said.

>From a practical standpoint, you have these options:

  1.  Change the EAD pre-migration
  2.  Change the data in Aspace
  3.  Live with the data like that (your cost of cleaning v living with it may vary, but it is worth having the discussion. My repository had some issues we decided to live with and some we decided to fix.)

Option 1 works if you have consistency in the choices folks have made in finding aids. Unfortunately at Harvard, for some repositories text like "Box 3-4" referred to a single box with the identifier 3-4, and not to "Box 3 and Box 4". Thus, we could not implement a single script that would work for all cases. We were also constrained by time and could not implement scripted solutions across sub-sets of our corpus. However...

Individual repositories did implement changes in their own ways. We had very few of these "box range" type of finding aids, so I (OK, I know this is a really crude, sledgehammer type of method!)

  *   Got the subset of finding aid that have this issue (granted, this can be some task in itself)
  *   Put them in their own directory
  *   Used regex find-and-replace (taking great care, of course to do no harm by accident) in either my favorite text editor or oXygen to find-and-replace all instances of the problem
  *   Double-checked that they were all still valid
  *   Spot-checked the results
Your mileage and access to a real programmer for stuff like this may vary.




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<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Mayo, Dave
Sent: Thursday, June 18, 2020 9:37 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Also, specifically:


  1.  Using an XML database like eXist-db or BaseX with XPath/XQuery was invaluable when doing analysis of issues and of the impact of changes
  2.  One of the tools I wrote, the EAD Checker, is available online: https://eadchecker.lib.harvard.edu - it doesn't catch this specific issue, but it does catch a bunch of issues, some of which cause corrupted data rather than failure to import.

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Mayo, Dave" <dave_mayo at harvard.edu<mailto:dave_mayo at harvard.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 9:23 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

So, with the caveat that we put a lot of resources (a bunch of archivists' time, a full year of a full time developer (me!)), we had very solid results; I think remediating issues prior to import is almost always worth the expense of significant effort, particularly over a large corpus.

My main advice would be to be very, very careful about changes - version your EADs, compare before and after scripts run, and in general be very systematic about how you find, report, and correct changes.

I don't know if you've seen it, but Kate Bowers and I did a write-up of what we did during our migration - it has links to a number of open source tools I wrote for doing this kind of work.  They're a bit involved to get running, but they definitely work at basically any scale out there, and I'm happy to help people get started with them.  https://journal.code4lib.org/articles/12239<https://urldefense.proofpoint.com/v2/url?u=https-3A__journal.code4lib.org_articles_12239&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=MDvEtnIJJpOOfJzfDMsXF5u8QJ22oJqGB1UWDHD9Gmc&s=0ky2pQ2HoOxy34kpHGjThpBcFVj1ERUBf7LwbRZMMP4&e=>

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 9:12 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Thanks, Dave.  I guess I should have specified that changing the EAD isn't a viable solution for us unless it's automated. We do not plan to edit individual finding aids manually except in cases where the ranges aren't regular.

If you've done this at Harvard, have there been any drawbacks? Anything we should be looking to avoid?

Thanks again,

Dawne


From: Mayo, Dave<mailto:dave_mayo at harvard.edu>
Sent: Thursday, June 18, 2020 9:04 AM
To: Archivesspace Users Group<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they're ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn't mind going more into why that's not a viable solution for you, it might help us provide better advice?

Either way, at 7000 finding aids, the solution would basically need to be automated - if your box ranges are very regular (i.e. only single number or range, no "3,4,7-10" or similar), it wouldn't be too difficult - split the range on '-', generate list of numbers, replace container with multiple containers.
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Lucas, Dawne Howard" <dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into ArchivesSpace and are wondering how other institutions have handled top container ranges.



For example, we have finding aids coded like this:



<c02><did><container type="box" label="Box">3-4</container><unittitle>Photographs</unittitle></did></c02>



This imports into ASpace just fine (yay!), but of course also creates a top container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding to:



<c02><did><container type="box" label="Box">3</container><unittitle>Photographs</unittitle></did></c02>



<c02><did><container type="box" label="Box">4 </container><unittitle>Photographs</unittitle></did></c02>



For several reasons, this is not a viable solution for us. Have other institutions figured out a way to deal with this issue that does not include editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lucas at unc.edu<mailto:dawne_lucas at unc.edu>

[cid:image001.png at 01D5F200.0D957C80]<https://urldefense.proofpoint.com/v2/url?u=https-3A__library.unc.edu_wilson_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=tkJE1JdGvSoNb5i6NSRbF3z1n28dGeVJ4ogcFmpTpQo&s=e9r4LIAN87oWg7LLTrzui9bCYcCMX-8twYfh3y0I8tY&e=>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200622/2f8e698e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 8588 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200622/2f8e698e/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 8591 bytes
Desc: image003.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200622/2f8e698e/attachment-0001.png>

From Jessica.Crouch at lyrasis.org  Tue Jun 23 09:58:35 2020
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Tue, 23 Jun 2020 13:58:35 +0000
Subject: [Archivesspace_Users_Group] Open call tomorrow on how ArchivesSpace
 can amplify and support efforts around antiracism and inclusion
Message-ID: <6BDC7A6B-8E2E-430E-B765-6FFB6D775476@lyrasis.org>

Dear ArchivesSpace Users,



Please join us for our next community call tomorrow, June 24th at 2-3pm ET (11-noon PT), via Zoom. This open call will be devoted to a discussion of ways ArchivesSpace can support and amplify efforts around antiracism and inclusion, and how ArchivesSpace itself can be more inclusive.  We also want to consider how we can incorporate these considerations more organically into our ongoing programming and our users' experience of ArchivesSpace.



We've come up with a few ideas. What we want most is to hear your ideas.


The running list for discussion is at https://docs.google.com/document/d/1b-GlCSObflqZufIiN4dJ__hlppwPloHXzytsUEVlZp4/edit?usp=sharing. Please feel free to add to or comment on this list in advance of the call or simply join us on the 24th with your thoughts, questions, and suggestions.


In order to better facilitate this conversation, an anonymous chat feature will be offered during the call.  The call will not be recorded.


Whether you can be at the call or not, please reach out to us at ArchivesSpaceHome at lyrasis.org at any time. We welcome your participation in any form.


Here are the details to join the call:


Join from PC, Mac, Linux, iOS or Android

https://lyrasis.zoom.us/j/96142471315?pwd=d1JhV3FUdTFzOVhEcnB2UWdxd2Fkdz09

Meeting ID: 961 4247 1315

Password: 807993



One tap mobile

+19292056099,,96142471315# US (New York)

+13017158592,,96142471315# US (Germantown)



Dial by your location

Meeting ID: 961 4247 1315

Find your local number: https://lyrasis.zoom.us/u/aXaScvS60

International numbers available: https://zoom.us/zoomconference?m=-CnZdNUzB4VhAipYXVQs3X1IOX8LOfFC


We seek to provide a welcoming, inclusive, and safe community experience for everyone and adhere to Code4Lib?s CodeofConduct4Lib. The full text of the code of conduct is available at: http://bit.ly/coc4lib.



Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200623/296bab1d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 29062 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200623/296bab1d/attachment.jpg>

From Jessica.Crouch at lyrasis.org  Thu Jun 25 13:15:48 2020
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Thu, 25 Jun 2020 17:15:48 +0000
Subject: [Archivesspace_Users_Group] Take a break with ArchivesSpace on
	Fridays
In-Reply-To: <69AD5D49-2C12-450D-9763-D88A59297611@lyrasis.org>
References: <D815E633-2930-485F-83D9-C2715CCE9F8C@lyrasis.org>
 <4C151ED1-3A98-4217-908A-55C7BA8ED233@lyrasis.org>
 <939F1E31-3ECB-44AD-93A6-6634E8BFF8F7@lyrasis.org>
 <C715180D-A70F-4DFB-8473-AD53F8136486@lyrasis.org>
 <C07A34DF-74FF-481C-A336-A923E6C76FC0@lyrasis.org>
 <512F3C3D-C506-4E11-B5FB-4B9EBF4775B0@lyrasis.org>
 <614B918C-6F58-4D55-89F5-18680C71701B@lyrasis.org>
 <F0569015-EC75-4C21-96D7-6B8B024647CA@lyrasis.org>
 <C56994B7-A96D-4DF3-9CB7-1D932B101927@lyrasis.org>
 <69AD5D49-2C12-450D-9763-D88A59297611@lyrasis.org>
Message-ID: <43C3FEA3-953D-4C61-BE1D-862242BE1B4A@lyrasis.org>

Dear ArchivesSpace Users,


We?ll be resuming our casual Friday open calls via zoom at 12pm ET tomorrow. With no set agenda or presentation for these calls, this forum is an opportunity to connect, chat and recharge. Use this as a time to get help or talk about ArchivesSpace (or anything else) in an informal setting or just have a beverage with other ArchivesSpace users during this stressful time.



Most of us are doing our jobs under much different conditions than usual. As a browser based system you can access from anywhere, the ArchivesSpace application may offer a sense of archival normalcy as we each adjust. And with a welcoming and robust member community all over the world, ArchivesSpace can also offer camaraderie when many of us may feel isolated from our colleagues or the professional communities we interact with regularly.



We look forward to seeing everyone again tomorrow.


When: Fridays
Time: 12:00 p.m. ? 1:00 p.m. ET (9:00 a.m. ? 10:00 a.m. PT)
Where: Zoom

Join the call via the information below:


Join Zoom Meeting

https://lyrasis.zoom.us/j/281962467



Meeting ID: 281 962 467



One tap mobile

+19292056099,,281962467# US (New York)

+13126266799,,281962467# US (Chicago)



Dial by your location

        +1 929 205 6099 US (New York)

        +1 312 626 6799 US (Chicago)

        +1 301 715 8592 US

        +1 346 248 7799 US (Houston)

        +1 669 900 6833 US (San Jose)

        +1 253 215 8782 US

        888 475 4499 US Toll-free

        877 853 5257 US Toll-free

Meeting ID: 281 962 467

Find your local number: https://lyrasis.zoom.us/u/awkFNWPxh

We seek to provide a welcoming, fun, and safe community experience for everyone and adhere to Code4Lib?s CodeofConduct4Lib. The full text of the code of conduct is available at: http://bit.ly/coc4lib.

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200625/0f16c78a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 29072 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200625/0f16c78a/attachment.jpg>

From Jessica.Crouch at lyrasis.org  Thu Jun 25 14:31:23 2020
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Thu, 25 Jun 2020 18:31:23 +0000
Subject: [Archivesspace_Users_Group] Notes from yesterday's open call
 tomorrow on how ArchivesSpace can amplify and support efforts around
 antiracism and inclusion
Message-ID: <E103F1DA-40A2-4D40-8B8C-583CA5652FC9@lyrasis.org>

Dear ArchivesSpace Users,



Thank you to everyone who attended our open call yesterday discussing ways ArchivesSpace can support and amplify efforts around antiracism and inclusion, and how ArchivesSpace itself can be more inclusive.  We really appreciated the discussion and the many ideas that were offered. If you were unable to attend the call, notes from the call that include the ideas and the slides can be found at:  https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1362296880/2020-6-24+Meeting+notes+-+Open+call+on+how+ArchivesSpace+can+amplify+and+support+efforts+around+antiracism+and+inclusion.



Some ideas that have emerged from these discussions might be relatively simple to implement, while others would require significant community discussion and collaboration, including involvement of the ArchivesSpace Governance Board. We will be circulating a survey soon to solicit comments on the ideas so far. This survey will not be intended as a way to vote or decide on any particular initiative but rather to generate more feedback from the community and help shape some paths forward.



Please reach out to us at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org> at any time with comments or suggestions. We welcome your participation in any form. We look forward to continuing to come together to better support and amplify this very important work across our community.



Best,

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200625/37244bb8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 29061 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200625/37244bb8/attachment.jpg>

From knoxa at uncw.edu  Thu Jun 25 14:45:00 2020
From: knoxa at uncw.edu (Knox, Ashley M.)
Date: Thu, 25 Jun 2020 18:45:00 +0000
Subject: [Archivesspace_Users_Group] human readable URLs -- translation
	missing resource
Message-ID: <CY4PR06MB3286EBCE8AB104AC5C5C0848DC920@CY4PR06MB3286.namprd06.prod.outlook.com>

When implementing human readable URLs, did anyone see this in the staff interface beside the new field labels?

'translation missing resource: public_url' and 'translation missing resource: slug'

It should only say public_url and slug.

Thank you for any tips.

Of the available options, we changed these two items from false to true.

use_human_readable_URLs - determines whether the options for creating human-readable URLs are shown in the staff interface<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fwiki%2Fspaces%2FArchivesSpaceUserManual%2Fpages%2F894828545%2FGlossary&data=01%7C01%7Cknoxa%40uncw.edu%7Cb61d7cec811b4490dc1108d817937a5e%7C2213678197534c75af2868a078871ebf%7C1&sdata=lr%2BlDiKpmlWSNbf%2BNQfrjs9ZMv456vjYaj9sykgpCjE%3D&reserved=0> and whether the URL shown in the public user interface for a record is the human-readable URL. (In order to prevent broken links, if this option was turned on at one time and then was turned off, the slugs created during that time remain in the records and the associated URLs will still work, but they will not be visible or editable through the staff interface. Only if the slugs are removed from the records will those URLs cease to work.)

auto_generate_slugs_with_id - by default, auto-generated slugs are based on the name or title in the record. If you choose this option, records with meaningful identifiers (like accessions and resources) will have slugs based on those IDs. Within this configuration there are two additional options.



Ashley Knox
Digital Initiatives Librarian
Randall Library
University of North Carolina Wilmington
knoxa at uncw.edu<mailto:knoxa at uncw.edu>
http://library.uncw.edu<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flibrary.uncw.edu%2F&data=01%7C01%7Cknoxa%40uncw.edu%7Caaea34565f8b4a39607c08d688608ce1%7C2213678197534c75af2868a078871ebf%7C1&sdata=aRhVgXWgwdJlJOfuBYOP3WNbHoTSgORkJqFFZUHLGIE%3D&reserved=0>
http://digitalcollections.uncw.edu<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdigitalcollections.uncw.edu&data=01%7C01%7Cknoxa%40uncw.edu%7Caaea34565f8b4a39607c08d688608ce1%7C2213678197534c75af2868a078871ebf%7C1&sdata=FWqWw29Sqtnu6xGB77IrgKaz7guhzKGCcvKcBZYGx4U%3D&reserved=0>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200625/c0e63673/attachment.html>

From Jessica.Crouch at lyrasis.org  Fri Jun 26 09:55:43 2020
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Fri, 26 Jun 2020 13:55:43 +0000
Subject: [Archivesspace_Users_Group] Webinar Announcement: Integrating
 ArchivesSpace with Drupal and Islandora at University of Nevada,
 Las Vegas Libraries
Message-ID: <9B5DB20F-708C-4ECC-9547-0D719B48B336@lyrasis.org>

Dear ArchivesSpace Users,
The next webinar in the Integrations with ArchivesSpace series will be Wednesday, July 15, at 2pm ET.  Each webinar in this series highlights an integration with another application used in archives that ArchivesSpace members have worked on or requested.
Our ninth webinar in this series will discuss integration with Drupal 8 and Islandora at the University of Nevada, Las Vegas.
When: July 15, 2020
Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? noon PT)
Where: Zoom
Registration: https://lyrasis.zoom.us/webinar/register/WN_9yfEhfHqR5exk5YUazX1hA
In order to provide a secure webinar experience and ensure adequate space in our Zoom environment, registration is now required for our webinars.  Our webinars continue to be free and open to anyone using or interested in ArchivesSpace.
Webinar description:
This webinar will be recorded and made available on the ArchivesSpace YouTube channel.

Seth Shaw will present an ArchivesSpace integration with Drupal 8. Drupal is a popular Content Management System widely used for building websites and is the foundational component of the popular Islandora 8 repository software. The ArchivesSpace Drupal module (https://www.drupal.org/project/archivesspace) allows Drupal and Islandora-based websites to present archival descriptions harvested from the ArchivesSpace API. This integration allows special collections and archives to build a single integrated interface combining both archival description from ArchivesSpace and digital objects in an Islandora 8 repository. This webinar will demonstrate how the integration works and how it can be used with Islandora 8. It will also demonstrate how it is being used at the UNLV Special Collections and Archives in their forthcoming repository site.
Webinar Presenter:
Seth Shaw is an Application Developer for UNLV Libraries dedicated to Special Collections and Archives. Previously, he was the Electronic Records Archivist for Duke University and an Assistant Professor of Archival Studies at Clayton State University. He has been developing IT solutions for special collections and archives, off and on, since his days as an undergraduate student.
Who should attend:

Anyone interested in learning more about using ArchivesSpace with both Drupal and Islandora, integrating Drupal and ArchivesSpace or who has already developed an integration for working with Islandora and ArchivesSpace.
Questions?
Contact Jessica at jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org> if you have questions about this webinar or the Integrations with ArchivesSpace webinar series.

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200626/e9be4f6b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 29061 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200626/e9be4f6b/attachment.jpg>

From alancaster at cals.org  Fri Jun 26 14:57:56 2020
From: alancaster at cals.org (Anna Lancaster)
Date: Fri, 26 Jun 2020 18:57:56 +0000
Subject: [Archivesspace_Users_Group] Reorder Mode
Message-ID: <SA0PR20MB3376D00499506851ED8B5BCDA3930@SA0PR20MB3376.namprd20.prod.outlook.com>

I'm having trouble with reordering. It seems to get hung up and eventually I have to close the record.  Has anyone had a solution for this?

Anna

ANNA LANCASTER
Audio Video Archival Assistant

CENTRAL ARKANSAS LIBRARY SYSTEM
ROBERTS LIBRARY  100 Rock Street, Little Rock, AR 72201
OFFICE  501.320.5718 |  WEB  www.cals.org<https://cals.org/>

[cid:image001.png at 01D64BC1.CA616480]


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200626/3ee13c98/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 13112 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200626/3ee13c98/attachment.png>

From christine.dibella at lyrasis.org  Fri Jun 26 16:25:41 2020
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Fri, 26 Jun 2020 20:25:41 +0000
Subject: [Archivesspace_Users_Group] release candidate available -
	ArchivesSpace v2.8.0-rc1
Message-ID: <MN2PR22MB1887CEFD074D24D6D6451C83F1930@MN2PR22MB1887.namprd22.prod.outlook.com>

Hello ArchivesSpace members,

The ArchivesSpace team is pleased to announce a release candidate, v2.8.0-rc1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.8.0-rc1 or test it out without downloading at http://test.archivesspace.org/staff  (username admin /password admin). We encourage you to download and try it out with your own local setup and/or data for the most accurate results.

This release candidate contains program-led and community pull requests that provide feature enhancements, bug fixes, infrastructure improvements, and documentation updates. Some items of note include the ability to merge top containers, new browse, search, and sort preferences in the staff interface, some improvements to search and display in the public interface, and additional display and faceting options in the background jobs area, as well as bug fixes and accessibility improvements. Fans of the popular Harvard import plugin will be pleased to see that incorporating its functionality into out-of-the-box ArchivesSpace is also part of this release, courtesy of our work with the plugin's original developer, Bobbi Fox.

Thanks to the many community members who made contributions to this release, including both individual archives staff and developers, as well as our Development Prioritization sub-team, Testing sub-team, and Core Committers Group.

Please try this release candidate out over the next few days and let us know at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org> by July 8 if you notice any problems with the specific areas addressed in this release, or if anything that was working before no longer is. The results of testing will determine the specific timeframe for the release itself.

Please get in touch if you have any questions. Thanks as always for your feedback and support.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200626/3144efd3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200626/3144efd3/attachment.jpg>

From jpwilkin at illinois.edu  Tue Jun 30 09:50:44 2020
From: jpwilkin at illinois.edu (John Wilkin)
Date: Tue, 30 Jun 2020 08:50:44 -0500
Subject: [Archivesspace_Users_Group] new members for ArchivesSpace
	governance groups
Message-ID: <CANgQ8c_RpVaM8GF9+km-vjszoqM4oaE9iYXMuK_riBQ1c0=zaA@mail.gmail.com>

Dear ArchivesSpace members,



On behalf of the Governance Board I am pleased to announce the following
new members for our ArchivesSpace governance groups.



*Governance Board (elected to three-year terms running July 1, 2020-June
30, 2023)*

   - Gordon Daines, Brigham Young University - Large level representative
   - Annie Benefiel, Grand Valley State University - Medium level
   representative
   - Nick Zmijewski, Industrial Archives and Library - Very Small level
   representative

*Technical Advisory Council (appointed to terms running from July 1,
2020-June 30, 2022)*

?       Andrew Morrison, University of Oxford

?       Elizabeth Roke, Emory University

?       Rachel Searcy, New York University

?       Saron Tran, University of Kansas

*User Advisory Council (appointed to terms running from July 1, 2020-June
30, 2022)*

?       Joanne Archer, University of Maryland

?       Elizabeth Beckman, George Mason University

?       Regina Carra, American Folk Art Museum

?       Bailey Hoffner, University of Oklahoma

?       Margaret Turman Kidd, Virginia Commonwealth University

?       Matthew Neely, University of Oxford

?       Cory Nimer, Brigham Young University

Please join me in welcoming these members to our governance groups and
thanking them for their willingness to serve the ArchivesSpace community in
this way.



Thank you to this year?s Nominating Committee for its work in putting
together a slate of excellent candidates for the openings on our groups and
to all who participated in the process. Our community is enriched by the
many different ways people contribute their talents.


Yours sincerely,

John Wilkin



-- 

John P. Wilkin
Juanita J. and Robert E. Simpson Dean of Libraries and University Librarian
University of Illinois at Urbana-Champaign
230 Library, MC-522
1408 W. Gregory Drive
Urbana, IL 61801

jpwilkin at illinois.edu
217-333-0790
Assistant: Lucretia Williams | lawillia at illinois.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200630/223d80f2/attachment.html>

From Jessica.Crouch at lyrasis.org  Tue Jun 30 13:23:34 2020
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Tue, 30 Jun 2020 17:23:34 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace Update - June 2020
Message-ID: <0CB48CC1-8698-442F-B2A5-356FEC3637A2@lyrasis.org>


[cid:image001.jpg at 01D64EE1.A7A14320]



Development

The ArchivesSpace team is pleased to announce a release candidate, v2.8.0-rc1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.8.0-rc1 or test it out without downloading at http://test.archivesspace.org/staff  (username admin /password admin). We encourage you to download and try it out with your own local setup and/or data for the most accurate results.

The release candidate contains program-led and community pull requests that provide feature enhancements, bug fixes, infrastructure improvements, and documentation updates. Some items of note include the ability to merge top containers, new browse, search, and sort preferences in the staff interface, some improvements to search and display in the public interface, and additional display and faceting options in the background jobs area, as well as bug fixes and accessibility improvements. Fans of the popular Harvard import plugin will be pleased to see that incorporating its functionality into out-of-the-box ArchivesSpace is also part of this release, courtesy of our work with the plugin?s original developer, Bobbi Fox.

Thanks to the many community members who made contributions to this release, including both individual archives staff and developers, as well as our Development Prioritization sub-team, Testing sub-team, and Core Committers Group.

Please try this release candidate out over the next few days and let us know at ArchivesSpaceHome at lyrasis.org by July 8 if you notice any problems with the specific areas addressed in this release, or if anything that was working before no longer is. The results of testing will determine the specific timeframe for the release itself.


Call for Speakers for the 6th Annual ArchivesSpace Member Forum

ArchivesSpace will be holding its sixth Annual Member Forum virtually on August 3-7, 2020, from 12pm-3pm ET each day via Zoom.  Just as in previous years, this free event is a chance for ArchivesSpace members to come together to highlight the work they are doing in ArchivesSpace, show off new plugins or tools they?ve developed, and attend workshops and trainings on a variety of topics. As with our previous Annual Member Forums, it is being held in conjunction with the Society of American Archivists annual meeting, but it is not part of SAA and does not require registration for the SAA Annual Meeting.



Presentations and breakout discussions will be held on August 3-4, 2020, and all individuals from ArchivesSpace member institutions are welcome to attend some or all of the sessions on these days.  Small workshops covering specific elements of the ArchivesSpace application will be offered August 5-7, 2020.  These workshops will be limited to 25 participants per workshop.



The event wiki and registrations will be made available soon, but for now we are looking for presenters and discussion leaders for August 3-4, 2020. Anything related to ArchivesSpace is fair game. We are specifically interested in presentations or topics related to managing others using ArchivesSpace, how you or your institution have adapted your use of ArchivesSpace during COVID-19, and any plugin or tool you?ve developed that you?d like to show off.

There is a short Google form for proposals available at https://forms.gle/DsZNqe2cANy5mS4S7. Proposals will be reviewed on a rolling basis. The last day that proposals will be accepted is July 15, 2020, and all notifications will be made by July 22, 2020.

If you have any questions or other suggestions at this point, please feel free to email Jessica at jessica.crouch at lyrasis.org.



Upcoming Webinar - Is It Roy E. Harrington or Roy S. Harrington?: How to Make Technology Work for You In an ArchivesSpace Data Cleanup Project

ArchivesSpace will be offering another webinar focusing on ArchivesSpace data cleanup projects that can be accomplished in a work from home environment on Wednesday, July 8, at 2pm ET. Most of us are doing our jobs under much different conditions than usual. As a browser-based system you can access from anywhere, ArchivesSpace is a tool that can be used when working remotely and many ArchivesSpace users are finding themselves executing large scale data cleanup projects that have only recently been prioritized.



When: July 8, 2020

Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00pm PT)

Where: Zoom
Registration: https://lyrasis.zoom.us/webinar/register/WN_T5x0GFR8QHicozJwCsm05Q<https://urldefense.proofpoint.com/v2/url?u=https-3A__lyrasis.zoom.us_webinar_register_WN-5FT5x0GFR8QHicozJwCsm05Q&d=DwMGaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=_iPtfI-oh6gC_Z6tmJI1y6Av--PwfhAF74rQK6DKyO4&m=rkbdEOey751wPdeeiUaVeHfOfTPgjCT1n8tjVawFJks&s=5stg63T_ua3Z9Cnm95lhMKrTuY25DerdLU61CuIVDSY&e=>



In order to provide a secure webinar experience and ensure adequate space in our Zoom environment, registration is now required for our webinars.  Our webinars continue to be free and open to anyone using or interested in ArchivesSpace.



Webinar description:



This webinar will be recorded and made available on the ArchivesSpace YouTube channel.

Three processing archivists from the Rockefeller Archive Center will discuss collaborative approaches to mass data cleanup in ArchivesSpace. Presenters will share how they planned, reassessed, and executed various automated and manual processes for enhancing the quality of their institution?s descriptive data. This data includes agent records, dates, and access restriction notes. This discussion is based off of the RAC ArchivesSpace Cleanup blog series<https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.rockarch.org_archivesspace-2Dclean-2Dup-2Dan-2Doutline&d=DwMGaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=_iPtfI-oh6gC_Z6tmJI1y6Av--PwfhAF74rQK6DKyO4&m=rkbdEOey751wPdeeiUaVeHfOfTPgjCT1n8tjVawFJks&s=JIymM-sIL0iKj421Nbo-4zA_l-JTWQUbMHdmXt-vxvc&e=>.



Webinar presenters:



Amy Berish is an Archivist at the Rockefeller Archive Center where she works as a member of the Processing team. Aside from processing incoming collections, she also contributes to various digital projects. Amy holds a Masters in Library and Information Science from the University of Pittsburgh.



Katie Martin is an Assistant Archivist at the Rockefeller Archive Center where she processes collections of the Ford Foundation and works on projects with the digital team. She earned degrees in History and American Studies from Purdue University and received her MLS with a specialization in archives and records management from Indiana University.



Darren Young is an Assistant Archivist at the Rockefeller Archive Center where he processes collections of the Ford Foundation and collaborates with the digital team on select projects. He earned a BA degree with majors in English Literature and History at the University of Connecticut and received his MLIS with a concentration in Archives Management from Simmons College (now Simmons University).



Who should attend:



While this webinar will focus on projects that can be undertaken in a work from home environment, this webinar will be useful to any archivist focusing on data cleanup in ArchivesSpace, those needing to export data out of ArchivesSpace and archivists working with legacy data.





Upcoming Webinar - Integrating ArchivesSpace with Drupal and Islandora at University of Nevada, Las Vegas Libraries


The next webinar in the Integrations with ArchivesSpace series will be Wednesday, July 15, at 2pm ET.


Each webinar in this series highlights an integration with another application used in archives that ArchivesSpace members have worked on or requested.



Our ninth webinar in this series will discuss integration with Drupal 8 and Islandora at the University of Nevada, Las Vegas.



When: July 15, 2020

Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? noon PT)

Where: Zoom

Registration: https://lyrasis.zoom.us/webinar/register/WN_9yfEhfHqR5exk5YUazX1hA
<https://lyrasis.zoom.us/webinar/register/WN_9yfEhfHqR5exk5YUazX1hA%0b>

In order to provide a secure webinar experience and ensure adequate space in our Zoom environment, registration is now required for our webinars.  Our webinars continue to be free and open to anyone using or interested in ArchivesSpace.



Webinar description:


This webinar will be recorded and made available on the ArchivesSpace YouTube channel.

Seth Shaw will present an ArchivesSpace integration with Drupal 8. Drupal is a popular Content Management System widely used for building websites and is the foundational component of the popular Islandora 8 repository software. The ArchivesSpace Drupal module (https://www.drupal.org/project/archivesspace) allows Drupal and Islandora-based websites to present archival descriptions harvested from the ArchivesSpace API. This integration allows special collections and archives to build a single integrated interface combining both archival description from ArchivesSpace and digital objects in an Islandora 8 repository. This webinar will demonstrate how the integration works and how it can be used with Islandora 8. It will also demonstrate how it is being used at the UNLV Special Collections and Archives in their forthcoming repository site.

Webinar Presenter:

Seth Shaw is an Application Developer for UNLV Libraries dedicated to Special Collections and Archives. Previously, he was the Electronic Records Archivist for Duke University and an Assistant Professor of Archival Studies at Clayton State University. He has been developing IT solutions for special collections and archives, off and on, since his days as an undergraduate student.


Who should attend:



Anyone interested in learning more about using ArchivesSpace with both Drupal and Islandora, integrating Drupal and ArchivesSpace or who has already developed an integration for working with Islandora and ArchivesSpace.



Notes Available from Our Open Call on How ArchivesSpace Can Amplify and Support Efforts around Antiracism and Inclusion


Thank you to everyone who attended our June 24 open call discussing ways ArchivesSpace can support and amplify efforts around antiracism and inclusion, and how ArchivesSpace itself can be more inclusive.


We really appreciated the discussion and the many ideas that were offered. If you were unable to attend the call, notes from the call that include the ideas and the slides can be found at:  https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1362296880/2020-6-24+Meeting+notes+-+Open+call+on+how+ArchivesSpace+can+amplify+and+support+efforts+around+antiracism+and+inclusion.



Some ideas that have emerged from these discussions might be relatively simple to implement, while others would require significant community discussion and collaboration, including involvement of the ArchivesSpace Governance Board. We will be circulating a survey soon to solicit comments on the ideas so far. This survey will not be intended as a way to vote or decide on any particular initiative but rather to generate more feedback from the community and help shape some paths forward.



Please reach out to us at ArchivesSpaceHome at lyrasis.org at any time with comments or suggestions. We welcome your participation in any form. We look forward to continuing to come together to better support and amplify this very important work across our community.


New Members on Our Governance Groups

Our nominations and elections process recently concluded and we welcome new members to our governance groups:

Governance Board (elected to three-year terms running July 1, 2020-June 30, 2023)

  *   Gordon Daines, Brigham Young University - Large level representative
  *   Annie Benefiel, Grand Valley State University - Medium level representative
  *   Nick Zmijewski, Industrial Archives and Library - Very Small level representative

Technical Advisory Council (appointed to terms running from July 1, 2020-June 30, 2022)

  *   Andrew Morrison, University of Oxford
  *   Elizabeth Roke, Emory University
  *   Rachel Searcy, New York University
  *   Saron Tran, University of Kansas

User Advisory Council (appointed to terms running from July 1, 2020-June 30, 2022)

?      Joanne Archer, University of Maryland

?      Elizabeth Beckman, George Mason University

?      Regina Carra, American Folk Art Museum

?      Bailey Hoffner, University of Oklahoma

?      Margaret Turman Kidd, Virginia Commonwealth University

?      Matthew Neely, University of Oxford

?      Cory Nimer, Brigham Young University

Thank you to these members for their willingness to serve the ArchivesSpace community in this way. We also thank this year?s Nominating Committee for its work in putting together a slate of excellent candidates for the openings on our groups and to all who participated in the process. Our community is enriched by the many different ways people contribute their talents.

Membership Update

We are excited to welcome our newest members to our community! Our new members since May 31 include:

  *   Indiana University East, (Richmond, IN)
  *   Indiana University Kokomo, (Kokomo, IN)
  *   Indiana University Northwest, (Gary, IN)
  *   Indiana University Southwest, (South Bend, IN)
  *   Indiana University South Bend, (New Albany, IN)
  *   Johnson County Community College, (Overland Park, KS)
  *   Judd Foundation, (Marfa, TX)

As of June 30, we have 424 General members, 21 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org> for more information.

________________________________

ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA?s Collection Management Tools Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists.


Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200630/23070fc4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 22469 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200630/23070fc4/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 29061 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200630/23070fc4/attachment-0001.jpg>

From KatieHall at rmc.edu  Tue Jun 30 16:27:03 2020
From: KatieHall at rmc.edu (Hall, Katie)
Date: Tue, 30 Jun 2020 20:27:03 +0000
Subject: [Archivesspace_Users_Group] Post to List
Message-ID: <BL0PR03MB4052E537DE782DB093B82775A76F0@BL0PR03MB4052.namprd03.prod.outlook.com>

Hope this works!

Thanks,


Katie Hall

Special Collections & Archives Associate

McGraw-Page Library

Randolph-Macon College

804-752-3203

KatieHall at rmc.edu<mailto:KatieHall at rmc.edu>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200630/4046cfe3/attachment.html>

From k-miller3 at northwestern.edu  Tue Jun 30 18:22:44 2020
From: k-miller3 at northwestern.edu (Karen Miller)
Date: Tue, 30 Jun 2020 22:22:44 +0000
Subject: [Archivesspace_Users_Group] help with API route for archival object
	notes
Message-ID: <CH2PR05MB701403973F699F2BBC3FE59DC56F0@CH2PR05MB7014.namprd05.prod.outlook.com>

Good morning, ArchivesSpace users.

I am a cataloger (*not* a developer) using the API to update ArchivesSpace. So far I've figured out how to add LCCNs to the authority_Id of Agent records and do a couple more updates that, in retrospect, were pretty simple.

The next task I'd like to tackle, however, just seems like maybe it can't be done. We've got a lot of notes with html tags in them and I would like to update those to valid tags. I can get the JSON for the notes in any particular archival object, but I don't know how to specify the route to the note to change it. The JSON looks like this:

'notes': [{'content': ['This is a note with a bad <i>tag</i>'],
            'jsonmodel_type': 'note_singlepart',
            'persistent_id': '75ba0ec57e374b8b154551a69b4c311f',
            'publish': True,
            'type': 'abstract'},
           {'jsonmodel_type': 'note_multipart',
            'persistent_id': '66afa07b3214260078123236bbe1ff27',
            'publish': True,
            'subnotes': [{'content': 'This is a dippy note.',
                          'jsonmodel_type': 'note_text',
                          'publish': True}],
            'type': 'scopecontent'}],

I got this using the route 'repositories/10/archival_objects/489763', but I don't know how to specify the note that I want in the JSON. For the agent authority_id I used the route ''/agents/people/<somenumber> and specified the field like this:

['names'][0]['authority_id']

I'm hoping this is an easy question for somebody with more experience with the API and (especially) with JSON than I. I'm a little afraid the answer is that it can't be done. Any advice will be appreciated!

Karen

Karen D. Miller
Monographic Cataloger/Metadata Specialist
Northwestern University Libraries
Northwestern University
1970 Campus Drive
Evanston, IL 60208
www.library.northwestern.edu
k-miller3 at northwestern.edu
874.467.3462

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200630/7073e5d8/attachment.html>

From james at hudmol.com  Tue Jun 30 19:35:05 2020
From: james at hudmol.com (James Bullen)
Date: Wed, 1 Jul 2020 09:35:05 +1000
Subject: [Archivesspace_Users_Group] help with API route for archival
 object notes
In-Reply-To: <CH2PR05MB701403973F699F2BBC3FE59DC56F0@CH2PR05MB7014.namprd05.prod.outlook.com>
References: <CH2PR05MB701403973F699F2BBC3FE59DC56F0@CH2PR05MB7014.namprd05.prod.outlook.com>
Message-ID: <F6B8EF46-545B-46FE-B0D7-70BAF247C84A@hudmol.com>


Hi Karen,

The general rule is that anything you can GET from a uri can be modified and POSTed back to update it.

So, GET the JSON for the archival_object as you are doing. Then modify the JSON (in this case the notes bit of it) to look how you want. Then POST it back to the same uri.

Notes are nested subrecords (as are dates and others). These don?t have a life of their own, they are really just repeating parts of the top level record that they are contained within.

Hope that helps..


Cheers,
James


> On Jul 1, 2020, at 8:22 AM, Karen Miller <k-miller3 at northwestern.edu> wrote:
> 
> Good morning, ArchivesSpace users.
>  
> I am a cataloger (*not* a developer) using the API to update ArchivesSpace. So far I?ve figured out how to add LCCNs to the authority_Id of Agent records and do a couple more updates that, in retrospect, were pretty simple. 
>  
> The next task I?d like to tackle, however, just seems like maybe it can?t be done. We?ve got a lot of notes with html tags in them and I would like to update those to valid tags. I can get the JSON for the notes in any particular archival object, but I don?t know how to specify the route to the note to change it. The JSON looks like this:
>  
> 'notes': [{'content': ['This is a note with a bad <i>tag</i>'],
>             'jsonmodel_type': 'note_singlepart',
>             'persistent_id': '75ba0ec57e374b8b154551a69b4c311f',
>             'publish': True,
>             'type': 'abstract'},
>            {'jsonmodel_type': 'note_multipart',
>             'persistent_id': '66afa07b3214260078123236bbe1ff27',
>             'publish': True,
>             'subnotes': [{'content': 'This is a dippy note.',
>                           'jsonmodel_type': 'note_text',
>                           'publish': True}],
>             'type': 'scopecontent'}],
>  
> I got this using the route ?repositories/10/archival_objects/489763?, but I don?t know how to specify the note that I want in the JSON. For the agent authority_id I used the route ??/agents/people/<somenumber> and specified the field like this:
>  
> ['names'][0]['authority_id']
>  
> I?m hoping this is an easy question for somebody with more experience with the API and (especially) with JSON than I. I?m a little afraid the answer is that it can?t be done. Any advice will be appreciated! 
>  
> Karen
>  
> Karen D. Miller
> Monographic Cataloger/Metadata Specialist
> Northwestern University Libraries
> Northwestern University
> 1970 Campus Drive
> Evanston, IL 60208
> www.library.northwestern.edu <http://www.library.northwestern.edu/>
> k-miller3 at northwestern.edu <mailto:k-miller3 at northwestern.edu>
> 874.467.3462
>  
> _______________________________________________
> 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 <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/20200701/284f705b/attachment.html>