[Archivesspace_Users_Group] question on fine-tuning reports

[Kevin Clair]

Good morning,

We have a handful of custom reports in ArchivesSpace. When I run them in the 
test instance on my local computer, they finish running in a matter of seconds 
or minutes; when I run them on our (hosted) production instance, they can take 
several hours to complete. Figuring out why this is the case is beyond my skill 
set; what sorts of factors should I be considering if I were to work with our 
hosting provider to solve this issue?

Thanks for any help you all can provide!  -k
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] merge Top Container functionality

[Kevin Clair]

Thanks, Christine! Will there be similar functionality for Container Profiles? 
Someone at our shop asked me about that the other day and I saw there's a 
ticket for it at https://archivesspace.atlassian.net/browse/ANW-550, but it 
looks like it hasn't been updated since last summer.  -k

On 6/4/19, 2:50 PM, "archivesspace_users_group-boun...@lyralists.lyrasis.org 
on behalf of Christine Di Bella" 
 wrote:

Hi Benn,

Merging Top Containers has been on our development roadmap, and we know it 
is of great interest to a number of people in the community, but until recently 
we had not been able to identify a developer to take this on. We've now 
determined that we will be able to work on this after some of the large 
projects related to agents and infrastructure that are currently in progress 
have been completed. We're aiming for this functionality to be available in the 
application later this year.

Christine

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



-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Benn 
Joseph
Sent: Tuesday, May 21, 2019 5:22 PM
To: Archivesspace Users Group 

Subject: [Archivesspace_Users_Group] merge Top Container functionality

Hi all,
I'm curious whether there are any updates re: the ability to merge Top 
Containers. It looks like ANW-462 deals specifically with this but I can't tell 
if there has been much activity on it lately:


https://archivesspace.atlassian.net/browse/ANW-462?atlOrigin=eyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9

Thanks!
--Benn

Benn Joseph
Head of Archival Processing
Northwestern University Libraries
Northwestern University
www.library.northwestern.edu
benn.jos...@northwestern.edu
847.467.6581



-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Tang, 
Lydia
Sent: Wednesday, January 16, 2019 12:18 PM
To: Archivesspace Users Group 

Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container 
Management Enhancements - Call for Community Input

I second the ability to merge containers!  
Lydia

From:  on behalf 
of Valerie Addonizio 
Reply-To: Archivesspace Users Group 

Date: Wednesday, January 16, 2019 at 1:17 PM
To: Archivesspace Users Group 

Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container 
Management Enhancements - Call for Community Input

I know that the comment period is closed, but this seemed like a logical 
place to ask whether the idea of container merging functionality was considered 
as part of this effort (I know it is not in the scope of work, but was it 
considered and not selected?) and whether other institutions are in need of 
such functionality?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Bowers, Kate A.
Sent: Thursday, December 20, 2018 4:16 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container 
Management Enhancements - Call for Community Input

Dear ArchivesSpace community:

Apologies for the length of this. I’ll try to address a lot of comments, 
but not all!  Please let me know if (as they may well do) my elaborations only 
elicit more questions!

In general, most of these proposals are derived from facing problems of 
scale. Harvard has 30 repositories and over 200 users of ArchivesSpace. Others 
have to do with managing “medium rare” materials’ locations and containers in 
ArchivesSpace.  (Medium-rare is a tongue-in-cheek term used to cover materials 
that might exist in multiple manifestations but that have archival or rare 
characteristics or treatment. Examples include entire libraries ingested into 
an archives, author’s own copies of their books, annotated books, or the record 
copy of serials or reports kept by institutional archives.)

 • Multi-field top container indicators
 Some commenters wondered if the multiple fields were to accommodate 
child containers. To clarify, the suggestion was to facilitate parsing top 
container identifiers.  As a few commenters have surmised, this is to cope with 
legacy numbers.  These are especially common on medium-rare materials.
 One suggestion was to use a sort algorithm that would obviate the need 
for separated fields for data. However, because there would be is more than one 
algorithm necessary over the installation, such a solution would require an 
added field to identify the algorithm and probably a third field retain a value 
derived by the algorithm to be sorted alphanumerically. Thus, the 

Re: [Archivesspace_Users_Group] Working with multiple ASpace strings

[Kevin Clair]

At Denver we have one less environment than Dartmouth, and our ArchivesSpace is 
hosted so our development environment tends to only gets its data synced with 
production when new releases come out, but otherwise we do what Joshua does.  -k

From:  on behalf of 
"Joshua D. Shaw" 
Reply-To: Archivesspace Group 
Date: Thursday, May 30, 2019 at 6:12 AM
To: Archivesspace Group 
Subject: Re: [Archivesspace_Users_Group] Working with multiple ASpace strings

We've got three (well four if you count my local dev) environments and follow a 
pretty strict process of data always goes from prod -> other environments via a 
db clone and code always pushes up via local->dev->pre-prod->prod with varying 
degrees of QA along the way. We also QA integrations the same way. I typically 
clone the production data before any QA process to ensure that the QA 
environment is as close to prod as possible. Long story short... we follow a 
hybrid of #1 & #3. Tests of code changes & representative data in QA and then 
full runs in production.

Hope that helps!
Joshua


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Rees, 
John (NIH/NLM) [E] 
Sent: Wednesday, May 29, 2019 11:43 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Working with multiple ASpace strings


Hi all,



This question isn’t aspace-centric, but for those of you that have multiple 
deployment strings (dev, qa, production) and that use the PUI, what is your 
best practice for entering new data or massaging existing data?



  1.  Do you test load/edit in QA then re-run the job in production?
  2.  Or do you load/edit in QA and replicate/auto-deploy to production? Can 
you just copy the database and re-index?
  3.  Not agonize over mistakes and just do it all in production?
  4.  Something else?



Do you worry about keeping the strings in synch?



Our old process was like #1, but we had separate systems for generating EAD and 
public facing search/discovery. With Aspace we are adding additional customers, 
more data types, less user command/control, etc. Is there a sweet spot for 
ensuring data integrity but have non-burdensome and flexible workflows?



John





John P. Rees

Archivist and Digital Resources Manager

History of Medicine Division

National Library of Medicine

301-827-4510










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

[Archivesspace_Users_Group] Survey of ArchivesSpace documentation writers

[Kevin Clair]

Hello!

The Documentation sub-team of the ArchivesSpace User Advisory Council is 
interested in the reasons why individual ArchivesSpace users are electing to 
write their own local documentation, either instead of or in addition to the 
local documentation available at https://docs.archivesspace.org. We have 
developed a brief survey of the ArchivesSpace membership in order to determine 
reasons for writing local documentation with the hope of improving the local 
documentation and making it easier to supplement that documentation with local 
practices.

The survey may be found at https://forms.gle/tTMjKvZyyfAxGCXN7. Responses in 
the next two to three weeks are appreciated. Please let me know if you have any 
questions!

cheers,
-Kevin Clair, for the ArchivesSpace UAC Documentation Sub-team
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Suppressed record search bug

[Kevin Clair]

We’re on 2.5.2 now. We upgraded because of that bug; that’s why I thought the 
problem could be with the event record instead of the resource.  -k

From:  on behalf of 
Blake Carver 
Reply-To: Archivesspace Group 
Date: Thursday, April 25, 2019 at 10:28 AM
To: Archivesspace Group 
Subject: Re: [Archivesspace_Users_Group] Suppressed record search bug

What version are you on? That looks similar to a bug that should've been fixed 
in 2.5.2.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Kevin 
Clair 
Sent: Thursday, April 25, 2019 12:08 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Suppressed record search bug


I should also say that the search that prompted this also returns a 
component_transfer event of records that were moved from the suppressed 
Resource to another Resource. So it may be that it’s an issue with suppressed 
records appearing in the “Found In” column of another record’s result summary, 
rather than with the suppressed record itself…  -k



From:  on behalf of 
Kevin Clair 
Reply-To: Archivesspace Group 
Date: Thursday, April 25, 2019 at 10:00 AM
To: Archivesspace Group 
Subject: [Archivesspace_Users_Group] Suppressed record search bug



Hello,



We recently discovered an issue with searching for records that are suppressed 
in the staff interface. In our instance, administrative users are able to do 
known-item searches for suppressed records without incident; if a user without 
administrative permissions performs the same search, they get thrown an error 
with the following stack trace:



I, [2019-04-25T09:47:26.038804 #18125]  INFO -- : Completed 500 Internal Server 
Error in 1163ms

F, [2019-04-25T09:47:26.041948 #18125] FATAL -- :

F, [2019-04-25T09:47:26.042069 #18125] FATAL -- : ActionView::Template::Error 
(undefined method `[]' for nil:NilClass):

F, [2019-04-25T09:47:26.042263 #18125] FATAL -- : 1: <% ancestors = 
context_ancestor(result) %>

2: <% if ancestors != nil && ancestors != [''] %>

3:   <% ancestors.reverse.each_with_index do |ancestor, i| %>

4: <%= 
resolve_readonly_link_to((get_ancestor_title(ancestor).html_safe), ancestor) %>

5: <% if i < ancestors.length - 1 %>

6:   <%= context_separator(result) %>

7: <% end %>

F, [2019-04-25T09:47:26.042340 #18125] FATAL -- :

F, [2019-04-25T09:47:26.042413 #18125] FATAL -- : 
app/helpers/search_helper.rb:198:in `get_ancestor_title'

app/views/search/_context.html.erb:4:in `block in 
_app_views_search__context_html_erb___234296763_2752'

app/views/search/_context.html.erb:3:in 
`_app_views_search__context_html_erb___234296763_2752'

app/helpers/application_helper.rb:289:in `render_aspace_partial'

app/views/search/_listing.html.erb:90:in `block in 
_app_views_search__listing_html_erb___1981573825_2748'

app/views/search/_listing.html.erb:52:in 
`_app_views_search__listing_html_erb___1981573825_2748'

app/helpers/application_helper.rb:289:in `render_aspace_partial'

app/views/search/_results.html.erb:23:in 
`_app_views_search__results_html_erb___1135689531_2744'

app/helpers/application_helper.rb:289:in `render_aspace_partial'

app/views/search/do_search.html.erb:16:in 
`_app_views_search_do_search_html_erb__585907251_2742'



Checking in to see if anyone else has noticed similar behavior and if there’s a 
bug report for this in Jira already. I did a quick search just now but couldn’t 
find anything that looked similar to this. thanks!  -k
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Suppressed record search bug

[Kevin Clair]

I should also say that the search that prompted this also returns a 
component_transfer event of records that were moved from the suppressed 
Resource to another Resource. So it may be that it’s an issue with suppressed 
records appearing in the “Found In” column of another record’s result summary, 
rather than with the suppressed record itself…  -k

From:  on behalf of 
Kevin Clair 
Reply-To: Archivesspace Group 
Date: Thursday, April 25, 2019 at 10:00 AM
To: Archivesspace Group 
Subject: [Archivesspace_Users_Group] Suppressed record search bug

Hello,

We recently discovered an issue with searching for records that are suppressed 
in the staff interface. In our instance, administrative users are able to do 
known-item searches for suppressed records without incident; if a user without 
administrative permissions performs the same search, they get thrown an error 
with the following stack trace:

I, [2019-04-25T09:47:26.038804 #18125]  INFO -- : Completed 500 Internal Server 
Error in 1163ms
F, [2019-04-25T09:47:26.041948 #18125] FATAL -- :
F, [2019-04-25T09:47:26.042069 #18125] FATAL -- : ActionView::Template::Error 
(undefined method `[]' for nil:NilClass):
F, [2019-04-25T09:47:26.042263 #18125] FATAL -- : 1: <% ancestors = 
context_ancestor(result) %>
2: <% if ancestors != nil && ancestors != [''] %>
3:   <% ancestors.reverse.each_with_index do |ancestor, i| %>
4: <%= 
resolve_readonly_link_to((get_ancestor_title(ancestor).html_safe), ancestor) %>
5: <% if i < ancestors.length - 1 %>
6:   <%= context_separator(result) %>
7: <% end %>
F, [2019-04-25T09:47:26.042340 #18125] FATAL -- :
F, [2019-04-25T09:47:26.042413 #18125] FATAL -- : 
app/helpers/search_helper.rb:198:in `get_ancestor_title'
app/views/search/_context.html.erb:4:in `block in 
_app_views_search__context_html_erb___234296763_2752'
app/views/search/_context.html.erb:3:in 
`_app_views_search__context_html_erb___234296763_2752'
app/helpers/application_helper.rb:289:in `render_aspace_partial'
app/views/search/_listing.html.erb:90:in `block in 
_app_views_search__listing_html_erb___1981573825_2748'
app/views/search/_listing.html.erb:52:in 
`_app_views_search__listing_html_erb___1981573825_2748'
app/helpers/application_helper.rb:289:in `render_aspace_partial'
app/views/search/_results.html.erb:23:in 
`_app_views_search__results_html_erb___1135689531_2744'
app/helpers/application_helper.rb:289:in `render_aspace_partial'
app/views/search/do_search.html.erb:16:in 
`_app_views_search_do_search_html_erb__585907251_2742'

Checking in to see if anyone else has noticed similar behavior and if there’s a 
bug report for this in Jira already. I did a quick search just now but couldn’t 
find anything that looked similar to this. thanks!  -k
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Suppressed record search bug

[Kevin Clair]

Hello,

We recently discovered an issue with searching for records that are suppressed 
in the staff interface. In our instance, administrative users are able to do 
known-item searches for suppressed records without incident; if a user without 
administrative permissions performs the same search, they get thrown an error 
with the following stack trace:

I, [2019-04-25T09:47:26.038804 #18125]  INFO -- : Completed 500 Internal Server 
Error in 1163ms
F, [2019-04-25T09:47:26.041948 #18125] FATAL -- :
F, [2019-04-25T09:47:26.042069 #18125] FATAL -- : ActionView::Template::Error 
(undefined method `[]' for nil:NilClass):
F, [2019-04-25T09:47:26.042263 #18125] FATAL -- : 1: <% ancestors = 
context_ancestor(result) %>
2: <% if ancestors != nil && ancestors != [''] %>
3:   <% ancestors.reverse.each_with_index do |ancestor, i| %>
4: <%= 
resolve_readonly_link_to((get_ancestor_title(ancestor).html_safe), ancestor) %>
5: <% if i < ancestors.length - 1 %>
6:   <%= context_separator(result) %>
7: <% end %>
F, [2019-04-25T09:47:26.042340 #18125] FATAL -- :
F, [2019-04-25T09:47:26.042413 #18125] FATAL -- : 
app/helpers/search_helper.rb:198:in `get_ancestor_title'
app/views/search/_context.html.erb:4:in `block in 
_app_views_search__context_html_erb___234296763_2752'
app/views/search/_context.html.erb:3:in 
`_app_views_search__context_html_erb___234296763_2752'
app/helpers/application_helper.rb:289:in `render_aspace_partial'
app/views/search/_listing.html.erb:90:in `block in 
_app_views_search__listing_html_erb___1981573825_2748'
app/views/search/_listing.html.erb:52:in 
`_app_views_search__listing_html_erb___1981573825_2748'
app/helpers/application_helper.rb:289:in `render_aspace_partial'
app/views/search/_results.html.erb:23:in 
`_app_views_search__results_html_erb___1135689531_2744'
app/helpers/application_helper.rb:289:in `render_aspace_partial'
app/views/search/do_search.html.erb:16:in 
`_app_views_search_do_search_html_erb__585907251_2742'

Checking in to see if anyone else has noticed similar behavior and if there’s a 
bug report for this in Jira already. I did a quick search just now but couldn’t 
find anything that looked similar to this. thanks!  -k
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] more punctuation issues with MARC exports

[Kevin Clair]

Hello,

We’re still encountering this MARC export error in 2.5.2; since today I had 
circled back to trying to figure out why it was happening, I thought I’d ping 
the list again to see if anyone else has encountered it.

I did a little bit more testing today and it seems like we only encounter the 
erratic punctuation if an agent is linked more than once in a resource, and if 
one of the links has the role of Subject. Multiple links punctuate normally in 
the MARC export if their roles are Creator and Source. This continues to be the 
case even with all of our plugins deactivated.

Happy to submit this as a bug report if others have encountered the issue. 
thanks!  -k

From:  on behalf of 
Kevin Clair 
Reply-To: Archivesspace Group 
Date: Tuesday, December 4, 2018 at 3:58 PM
To: Archivesspace Group 
Subject: [Archivesspace_Users_Group] more punctuation issues with MARC exports

Hello,

We’re testing 2.5.1 here at DU because it fixes some bugs our archivists have 
encountered, and in so doing I’ve found some strangeness with 110s and 610s in 
the MARC export. When we have resources where the same agent is a creator and a 
subject of the resource, the exporter will always append a comma to the name 
even if it’s a 610 and there’s no subfield E present, and will always append a 
period after the comma even if it’s a 110 and there is a subfield E present.

We have some MARC export customizations in our local plugins, but this error 
persists even if I turn the local plugins off in our configuration.

The error moves from agent to agent, e.g. if I change the creator from “Central 
City Opera House Association (Central City, Colo.)” to “Central City Opera 
Festival (Central City, Colo.),” the erratic punctuation in subfield A will 
move to the latter corporate name from the former.

Attached is example output (this is from our 2.5.1 instance with no active MARC 
customizations). I wanted to send a note to the list to see if anyone else has 
seen anything similar before I submit a JIRA ticket for it.

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

[Archivesspace_Users_Group] more punctuation issues with MARC exports

[Kevin Clair]

Hello,

We’re testing 2.5.1 here at DU because it fixes some bugs our archivists have 
encountered, and in so doing I’ve found some strangeness with 110s and 610s in 
the MARC export. When we have resources where the same agent is a creator and a 
subject of the resource, the exporter will always append a comma to the name 
even if it’s a 610 and there’s no subfield E present, and will always append a 
period after the comma even if it’s a 110 and there is a subfield E present.

We have some MARC export customizations in our local plugins, but this error 
persists even if I turn the local plugins off in our configuration.

The error moves from agent to agent, e.g. if I change the creator from “Central 
City Opera House Association (Central City, Colo.)” to “Central City Opera 
Festival (Central City, Colo.),” the erratic punctuation in subfield A will 
move to the latter corporate name from the former.

Attached is example output (this is from our 2.5.1 instance with no active MARC 
customizations). I wanted to send a note to the list to see if anyone else has 
seen anything similar before I submit a JIRA ticket for it.

thanks!  -k


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

Re: [Archivesspace_Users_Group] Alma Integration

[Kevin Clair]

Definitely interested!  -k

Get Outlook for iOS

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Belair, 
Andrea 
Sent: Wednesday, October 31, 2018 7:47:10 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Alma Integration

Hello,
I'd be interested. I'm at Union College.
Thanks,
Andrea

On Wed, Oct 31, 2018 at 9:45 AM Hilton, Adrien 
mailto:adrien_hil...@harvard.edu>> wrote:
Hi All,

At Houghton Library, part of the Harvard Library, we too are interested in 
ArchivesSpace/Alma integration.

In terms of functionality for resource description, we looked a bit at the 
Denver plug-in and like the type of data exchange it offers between the 
ArchivesSpace resource record and the Alma Bib and Holdings records using the 
MMS ID. We could also envision the exchange working the other way, starting 
from the Alma record and looking to ArchivesSpace for a resource record with 
that MMS ID (in a locally specified field), creating a resource if non-existent 
or updating if existent.

We would also like to think through subject and agent access points and keeping 
those up-to-date in both systems (using URIs), and optimally, up-to-date with 
the authority file (functionality that Alma currently offers).

Lastly, exchanging and maintaining container inventories and barcodes 
(instances in ArchivesSpace and item records in Alma) across the systems is 
another area of functionality we’d like to explore.

We’d like to host a conference call for interested parties. Can folks respond 
if they are interested in taking part? If there’s enough momentum, I’ll send 
around a Doodle poll with some available times.

Best wishes,
Adrien, Susan, and Vernica
Houghton Library

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Chad Mills
Sent: Wednesday, October 24, 2018 2:30 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Alma Integration

Hi all,

Attached is the reference architecture and test/sample implementation 
architecture we developed at Rutgers.  We have not implemented this yet.

Best,
Chad

From: Chad Mills
Sent: Friday, October 12, 2018 8:43 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: RE: [Archivesspace_Users_Group] Alma Integration

Hi,

We are interested!  At Rutgers earlier this year we developed a reference 
architecture for our Special Collections.  We tested the reference architecture 
by creating an implementation architecture using Alma, Primo, ArchiveSpace and 
a generic repository framework.  In June we migrated to Alma so we will be 
looking to integrate ArchiveSpace with Alma in the near future using our the 
reference architecture as a blue print.  I’ll see if I can share that reference 
architecture with the group.

Best,
Chad

-
Chad Mills
Digital Library Architect
Rutgers University Libraries
Phone: 848.932.5924
Cell: 732.309.8538
-


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Megan Firestone
Sent: Wednesday, October 10, 2018 1:34 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Alma Integration

Hi,

We us Alma as our library ILS here, so we have been looking at the possibility 
of integrating Alma and ArchivesSpace.  I was curious if anyone else is 
interested in this type of integration and if there is any work being done?

Thanks!
Megan

--
Megan M. Firestone
Archivist and Public Services Librarian
Munday Library
St. Edward's University
3001 S. Congress Ave.
Austin, TX 78704
512.428.1047
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Andrea Belair
Archives and Special Collections Librarian
Union College
807 Union Street
Schenectady, NY 12308
518-388-6871
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Alma Integration

[Kevin Clair]

For us, we want to be able to:


  *   create holdings and items in Alma, from ArchivesSpace, using existing Top 
Container metadata;
  *   compare MARC records for a Resource between the two systems, and push 
to/pull from Alma as needed to keep metadata in sync; and
  *   compare item-level metadata between the two systems, and eventually to 
push to/pull from Alma as needed to keep inventory records in sync

In general we want to keep archival description work in ArchivesSpace and use 
the APIs to update Alma, instead of having to train archivists on metadata 
management in two different systems. This way only the folks who do manuscripts 
and special collections cataloging need to work with the Alma metadata editor 
directly.

I'd be interested to hear others' ideas!  -k

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Megan 
Firestone 
Sent: Wednesday, October 17, 2018 9:27:21 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Alma Integration

Hi,

It's exciting to see so many interested.  To help develop the conversation, 
what type of functionality would you like to see in an integration between Alma 
and ArchivesSpace?

Best,
Megan

On Wed, Oct 17, 2018 at 9:57 AM Chad Mills 
mailto:chad.mi...@rutgers.edu>> wrote:

Hi,



We are interested!  At Rutgers earlier this year we developed a reference 
architecture for our Special Collections.  We tested the reference architecture 
by creating an implementation architecture using Alma, Primo, ArchiveSpace and 
a generic repository framework.  In June we migrated to Alma so we will be 
looking to integrate ArchiveSpace with Alma in the near future using our the 
reference architecture as a blue print.  I’ll see if I can share that reference 
architecture with the group.



Best,

Chad



-
Chad Mills
Digital Library Architect
Rutgers University Libraries
Phone: 848.932.5924
Cell: 732.309.8538
-





From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org]
 On Behalf Of Megan Firestone
Sent: Wednesday, October 10, 2018 1:34 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Alma Integration



Hi,



We us Alma as our library ILS here, so we have been looking at the possibility 
of integrating Alma and ArchivesSpace.  I was curious if anyone else is 
interested in this type of integration and if there is any work being done?



Thanks!

Megan

--

Megan M. Firestone
Archivist and Public Services Librarian
Munday Library
St. Edward's University
3001 S. Congress Ave.
Austin, TX 78704
512.428.1047

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


--
Megan M. Firestone
Archivist and Public Services Librarian
Munday Library
St. Edward's University
3001 S. Congress Ave.
Austin, TX 78704
512.428.1047
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Alma Integration

[Kevin Clair]

To elaborate on that plugin: At Denver we create MARC records for each 
collection once it’s ready to be published and sent to the catalog. To automate 
that, we dedicated one of the user-defined string fields to the Alma MMS ID, 
which is the hook that its Bibliographic API uses. The plugin asks you to 
provide a Resource as input. From there it checks if that Resource has an MMS 
ID provided in the user-defined fields. If no, it asks if you’d like to create 
one (using the ArchivesSpace MARC export); if yes, it looks for any holdings 
records attached to the MARC record with that MMS ID, and provides you the 
option to create new holdings records if you wish.

A lot of the code in the plugin is hard-coded for the way we have Alma set up 
at DU. I’m working on setting some of those things (holdings codes, etc.) up as 
configurable options so that other Alma users can implement this without having 
to get into too much of the actual plugin code to set it up for their instance. 
It also doesn’t do anything with item records, which is the next major feature 
I want to build into it.

I’m happy to answer other questions about this!  -k

From:  on behalf of 
Adam Jazairi 
Reply-To: Archivesspace Group 
Date: Wednesday, October 10, 2018 at 11:52 AM
To: Archivesspace Group 
Subject: Re: [Archivesspace_Users_Group] Alma Integration

Hi Megan,

We're also interested in such an integration, but we haven't started working on 
it yet. The University of Denver Libraries recently released a plugin that 
might be of interest: https://github.com/duspeccoll/alma_integrations

Adam

On Wed, Oct 10, 2018 at 1:34 PM Megan Firestone 
mailto:mbla...@stedwards.edu>> wrote:
Hi,

We us Alma as our library ILS here, so we have been looking at the possibility 
of integrating Alma and ArchivesSpace.  I was curious if anyone else is 
interested in this type of integration and if there is any work being done?

Thanks!
Megan

--
Megan M. Firestone
Archivist and Public Services Librarian
Munday Library
St. Edward's University
3001 S. Congress Ave.
Austin, TX 78704
512.428.1047
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Adam Jazairi
Digital Repository Services
Boston College Libraries
(617) 552-1404
adam.jaza...@bc.edu
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] arranging Digital Object records for archived websites

[Kevin Clair]

Hello list,

I’m curious if any ArchivesSpace institutions, particularly those using the 
PUI, can share their strategies for arranging archived websites into a 
collection or record group in ArchivesSpace. I’ve looked at a couple of plugins 
for representing Archive-It crawls as Digital Objects [1] [2]; what I’m 
interested in is to what, exactly, those Digital Objects are getting linked in 
the staff interface. We have a couple of thoughts for how we might do this at 
Denver but I’d be interested to hear others’ thoughts.

thanks!  -k

[1] 
https://github.com/NYULibraries/Archivesspace-DO-Plugin/wiki/Archive-It-Integration
[2] https://github.com/bentley-historical-library/bhl_aspace_archive_it



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

Re: [Archivesspace_Users_Group] Agent suggestions in 2.4.1

[Kevin Clair]

We had this problem at Denver and resolved it by installing the and_search 
plugin (https://github.com/hudmol/and_search) to change Solr's default Boolean 
operator to 'and'. I think (but am not 100% certain) that this is the default 
in 2.5.0.  -k

[https://avatars2.githubusercontent.com/u/1821448?s=400=4]

GitHub - hudmol/and_search: An ArchivesSpace plugin that 
...
github.com
GitHub is where people build software. More than 28 million people use GitHub 
to discover, fork, and contribute to over 85 million projects.




From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Lara 
Friedman-Shedlov 
Sent: Wednesday, September 12, 2018 8:34:21 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Agent suggestions in 2.4.1

Yes, that's the same issue.  We've been having it here at the University of 
Minnesota as well. Reindexing did not solve the issue.

On Wed, Sep 12, 2018 at 9:30 AM Blake Carver 
mailto:blake.car...@lyrasis.org>> wrote:
Is this the same issue?

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


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Olivia S Solis mailto:livso...@utexas.edu>>
Sent: Wednesday, September 12, 2018 9:54:33 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Agent suggestions in 2.4.1

Hello all,

We have been having a problem with the auto-complete suggestions for linked 
agents in our upgrade from 1.5.3 to 2.4.1. 2.4.1 does not always present 
relevant suggestions. For example, we have an existing corporate agent, "Texas 
Federation of Music Clubs." When I try to add the agent, it presents the 
following:

[Screen Shot 2018-08-31 at 2.41.48 PM.png]

So it is pulling suggestions from the family agents. Similarly, we have an 
agent person "Smith, Liz, 1923-2017." It does not present her as an option 
unless we type ", " after her name. Someone who wants to add her, though, won't 
necessarily know that she's got a date addition. Again it pulls from family 
agents.
[Screen Shot 2018-09-12 at 8.44.48 AM.png]
[Screen Shot 2018-09-12 at 8.44.59 AM.png]

This what the suggestions looked like in 1.5.3 for us:
[Screen Shot 2018-08-31 at 3.49.41 PM.png]
[image.png]

Has anyone else had a problem with this? Trying to figure out if this is an 
issue with 2.4.1 or with our data. Perhaps we've got something configured 
incorrectly in our settings?

We've already tried re-indexing, but that did not help.

Any suggestions would be great!

Thanks,
Olivia

--
Olivia Solis, MSIS
Metadata Coordinator
Dolph Briscoe Center for American History
The University of Texas at Austin
2300 Red River St. Stop D1100
Austin TX, 78712-1426
(512) 232-8013
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
_

Lara D. Friedman-Shedlov(She/Her/Hers)
Kautz Family YMCA Archives | University of 
Minnesota Libraries
l...@umn.edu |  612.626.7972 |

[www.facebook.com/IHRCA]  
[https://twitter.com/yarchives] 

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

Re: [Archivesspace_Users_Group] PUI request button - are you using it? if so, how?

[Kevin Clair]

Hello,



We have our request button configured to send an e-mail to our Special 
Collections reference desk, from which it’s easier to pipe the requests into 
our reference tracking system (we use LibAnswers). I’d say for every actual 
reference question we get through that link, we get another four or five spam 
e-mails. That may be because we haven’t been actively marketing the PUI to 
students and researchers yet, so more robots know about the PUI than people.  -k


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Christine Di Bella 
Sent: Wednesday, August 22, 2018 8:14:23 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] PUI request button - are you using it? if 
so, how?


Hi all,



I’ve been getting questions here and there about how people are setting up and 
using the Request functionality in the ArchivesSpace public interface. Since 
this is more on the individual institution implementation side of things, I’d 
like to put the question out to the group. Are you using it? Have you 
customized it at all? Do you link out to a shared organizational email smtp or 
sendmail server from your ArchivesSpace server or install that functionality on 
the ArchivesSpace server itself?



(And if you’re not using the ArchivesSpace request functionality itself, but 
linking/integrating to something else that performs that function, I’m sure 
that would be of interest too.)



Thanks in advance,

Christine



Christine Di Bella

ArchivesSpace Program Manager

christine.dibe...@lyrasis.org

800.999.8558 x2905

678-235-2905

cdibella13 (Skype)



[ASpaceOrgHomeMedium]


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

[Archivesspace_Users_Group] support for agent name forms in RTL scripts

[Kevin Clair]

Hello,

Has there been any consideration given to the possibility of encoding name 
forms for Agents in right-to-left scripts? This is something we would get some 
use out of at DU, since we have a number of Hebrew and Arabic personal names in 
our collections. I searched through the list archives and the current JIRA 
tickets but couldn’t find anything along these lines.

Not a high-priority request for us, I was just curious if anyone else had 
requested it.

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

[Archivesspace_Users_Group] jQuery plugin question

[Kevin Clair]

Hello! If there’s anyone on the list who has experience with extending the 
behavior of the jQuery functions in ArchivesSpace, would you mind pinging me 
off-list? I have a plugin question. A jQuandary, if you will. thanks!  -k
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ArchivesSpace integrations with Alma

[Kevin Clair]

Hello,

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

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

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

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

[Archivesspace_Users_Group] memory issues with reports in v2.3.0

[Kevin Clair]

Hello,

I was curious if anyone else on the list had noticed that reports (and possibly 
other background jobs) are consuming more memory in v2.3.0 than in previous 
versions of ArchivesSpace. We’ve noticed that reports that worked for us in 
2.2.1 are throwing “GC overhead limit exceeded” errors since we upgraded.

We don’t use any of the default reports; every report we have in our instance 
is here: https://github.com/duspeccoll/archivesspace_reports. I’m sharing the 
link in case it’s a problem with our reports, and there are ways I could write 
them to be more efficient.

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

[Archivesspace_Users_Group] incompatible encodings error on the v2.2.2 public site

[Kevin Clair]

Hello,

We upgraded to version 2.2.2 last night, and since then we've received the 
following error message when attempting to view some collections in the PUI:

Jan 18, 2018 9:25:21 AM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: F, [2018-01-18T09:25:21.858975 #8903] FATAL -- : 
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5] ActionView::Template::Error (incompat
ible encodings: UTF-8 and ASCII-8BIT):

Jan 18, 2018 9:25:21 AM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: F, [2018-01-18T09:25:21.859788 #8903] FATAL -- : 
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5] 38:   
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5] 39:  
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5] 40:  <%= flash_messages %>
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5] 41:  <%= yield %>
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5] 42:  
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5] 43:
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5] 44:  

Re: [Archivesspace_Users_Group] LCNAF mapping -- AuthorityID & Sort Name

[Kevin Clair]

We have a plugin that verifies that an authority ID assigned to an Agent exists 
(though not yet necessarily that they represent the same Agent); it works on 
this principle: https://github.com/duspeccoll/verify_agent

-k

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, January 09, 2018 12:07 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] LCNAF mapping -- AuthorityID & Sort 
Name


I don’t think the URI should be stored as a separate field in the DB ( in 
names_* tables ).
Presumably, the resolver URL part of the string is linked to the source, so it 
should probably be linked to the source and concatenated with UUID to make a 
URI for display. If the resolver for a source changes, then it’s going to 
change for all names from that source.  name_source is an enumeration value. So 
probably add an AppConfig array for resolvers, indexed by name_source value. 
Probably want to do the same thing for subject resolvers.

Concatenation could be done when building JSON model so this would be a display 
field, but not editable.

Not clear in those plugin mappings if Source value was meant to be “naf” or the 
string “Library of Congress Name Authority File” , but this value should be 
reconciled with name_source enums, which would mean value = “naf” , and change 
current translation to “Library of Congress Name Authority File”  from “NACO 
Authority File” .


— Steve Majewski



On Jan 8, 2018, at 4:11 PM, Rees, John (NIH/NLM) [E] 
> wrote:

How about adding to the core a separate URI field for the full string?


John P. Rees
Archivist and Digital Resources Manager
History of Medicine Division
National Library of Medicine
301-827-4510



From: Brian Thomas [mailto:btho...@tsl.texas.gov]
Sent: Monday, January 08, 2018 1:02 PM
To: 'Archivesspace Users Group' 
>
Subject: Re: [Archivesspace_Users_Group] LCNAF mapping -- AuthorityID & Sort 
Name

Thank you for your continued work with this plug-in. I like the sort name idea.

But…I am concerned about directly embedding a URI when we have the authority 
number as the UUID. I doubt the authority id will change, but it is always 
possible that the URI information preceding or trailing the authority ID will 
be modified for some reason.  I used to think URIs were persistent, but lately 
I’ve come across systematic changes with websites that invalidate good urls and 
require manual intervention to get working.

My thought process is that: if we just key off the authority UUID, with the 
appropriate source specified from the drop-down menu, the underlying code can 
compile and potentially create the authority URL from the latest known URI 
structure for synchronization/ead export. That way, if a change becomes 
necessary, one part of the application gets changed instead having to batch 
alter potentially thousands of cells in a database.

Just my two cents.

Brian Thomas
Electronic Records Specialist
Texas State Library and Archives Commission
1201 Brazos Street
Austin, TX 78701
PH: (512) 475-3374
e-mail: btho...@tsl.texas.gov
tsl.texas.gov




From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Lapka, Francis
Sent: Monday, January 8, 2018 10:30 AM
To: Archivesspace Users Group 
>
Subject: [Archivesspace_Users_Group] LCNAF mapping -- AuthorityID & Sort Name

In April 2017, I asked for thoughts on changes that Yale would like to see in 
the AS LCNAF plugin (see below).

We are now working with Lyrasis to implement some of these changes. Where 
appropriate, some changes may be made in the AS core code for MARC mapping 
(e.g., in mapping dates of existence). Other changes that Yale would like to 
see may be implemented in a local variation of the LCNAF plugin.

For two of Yale’s desired changes, it’s unclear whether the modification should 
be made to the core code or as a local modification of the plugin.


  1.  AuthorityID: For imports from LC, Yale would like to populate the 
AuthorityID field with the URI for the entity rather than the MARC 010 value. 
For example, 
http://id.loc.gov/authorities/names/n79060712
 instead of n79060712. We assume the URI will be more useful, lending 

Re: [Archivesspace_Users_Group] Processing notes

[Kevin Clair]

Three main reasons, in descending order of importance:


1.   At the top of the record so easy to see at a glance

2.   Easier to query in a report

3.   More ephemeral, so less inclined to go to the trouble of navigating 
subforms to enter that information

-k

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Christie Peterson
Sent: Tuesday, January 02, 2018 2:37 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Processing notes

Thanks for the quick response, Kevin. Is there any particular reason why you 
use that note field, instead of the Collection Management subrecord, for that 
purpose?

Christie

On Tue, Jan 2, 2018 at 4:34 PM Kevin Clair 
<kevin.cl...@du.edu<mailto:kevin.cl...@du.edu>> wrote:
Hi Christie,

At the University of Denver we use it in both Resource and Archival Object 
records as a note to other archivists indicating processing or cataloging tasks 
that were left unfinished for one reason or another, or other administrative 
things that we don’t want published in the PUI. The idea is that if the actions 
listed in the Repository Processing Note get taken, we remove the text that’s 
there.

We have a report that pulls the information from that field for review that we 
run periodically when setting processing priorities: 
https://github.com/duspeccoll/archivesspace_reports/tree/master/resources/resource_processing_notes_report

-k

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>]
 On Behalf Of Christie Peterson
Sent: Tuesday, January 02, 2018 2:28 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Processing notes

Hello,

Can anyone on this list speak to what was intended to go in the "Repository 
Processing Note" text field for Resources, which the tooltip tells me does not 
appear in any exports or reports?

Can anyone give me a use case for why they populate this field in addition to 
(or instead of?) an unpublished "Processing Information" note?

Thanks,

Christie Peterson
--
❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️
Christie S. Peterson
Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996<tel:(413)%20585-2996>
cpeter...@smith.edu<mailto:cpeter...@smith.edu>

pronouns: she/her/hers
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org<mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
--
❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️
Christie S. Peterson
Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeter...@smith.edu<mailto:cpeter...@smith.edu>

pronouns: she/her/hers
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Linking related accessions below collection level

[Kevin Clair]

Hello,

We would also be interested in this; it's one of the features we lost in 
migrating from our last system (besides batch editing) that gets requested the 
most. We're currently capturing this information in the Disposition Note of 
each Accession record, but we would definitely like to link to accessioned 
materials more directly than just at the Resource level.  -k

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Jordon Steele
Sent: Tuesday, November 28, 2017 9:57 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Linking related accessions below 
collection level

Hi all,

We have an interest in linking archival objects (i.e. the levels below 
collection level) in resource records back to the accessions they came from. 
The situation that precipitated discussion about this possibility was that we 
have one series of materials that is associated with multiple accession records.

Unless I'm missing something, the only way one can currently link to accessions 
from resource records is at the collection level. There is no "Related 
accessions" feature at levels below that.

The way we're doing this now is creating an accruals note at the appropriate 
level and typing the accession number into the free text field, but having a 
direct link between the two would be handy. For born-digital collections, we 
are also linking the original containers from which the digital content came to 
the appropriate level in the resource record using the instance module.

I'm wondering if others in the community have discussed or considered this 
before.

Thanks!

Best,

Jordon

Jordon Steele
Hodson Curator of the University Archives
Special Collections
The Sheridan Libraries
Johns Hopkins University
3400 N Charles St
Baltimore, MD 21218
410-516-5493
jste...@jhu.edu

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

[Archivesspace_Users_Group] memory issues with v2.2.1

[Kevin Clair]

Hello,

Has anyone on the list who has upgraded to version 2.2.1 noticed ArchivesSpace 
maxing out their system's CPU or memory usage? We upgraded on Wednesday and 
have had to restart our server twice today due to Java heap space errors. It 
doesn't appear to be running an index, and I can't see anything else in the 
logs that might be prompting this.

Thanks for any help!  -k
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

[Kevin Clair]

We’ve been able to receive the e-mail confirmations ArchivesSpace sends, both 
with my personal e-mail and with LibAnswers. It’s only when it tries to render 
request_received_email.html that it throws the error.  -k

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Custer, Mark
Sent: Thursday, September 21, 2017 3:31 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" 
after requesting material via ArchivesSpace


All,



I wish that I could offer technical advice on how to get things set up, but 
unfortunately I'm of no use in this case.  I do know that this feature used to 
be configured on our Test Corpus site, though, and that it functioned as 
expected at that time.



Here's what a message would look like that's sent to a patron (as you can see, 
it doesn’t include ALL of the data, like what the staff would receive), and 
they shouldn’t see an error message when requesting after everything has been 
configured to allow email requesting:



Thank you for your request
Record Requested
Title: Watercolor of Brassie fly nymph (fishing fly)
URL: 
http://aspace.hudmol.com:7310/repositories/14/digital_objects/4375<https://urldefense.proofpoint.com/v2/url?u=http-3A__aspace.hudmol.com-3A7310_repositories_14_digital-5Fobjects_4375=DwMCaQ=-dg2m7zWuuDZ0MUcV7Sdqw=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo=hES0nr_7CQRdsaxxcbpbcujfoSJVVVtSbikTnQDfBMQ=fEcKFYM5n4pdR51TDuNa_20WsC4Rr2r-cKOf4FBNyuk=>
Your Details
Name: m
Email: mark.cus...@yale.edu<mailto:mark.cus...@yale.edu>
Date:
Notes for Staff:



I don’t believe that the email that was sent to staff ever had a specialized 
template, like this one, however.  It was just meant to be a proof of concept 
showing how all of the request data could be sent in an email message in order 
to fulfill the user story about allowing researchers to make requests directly 
from the PUI.



Hopefully others will be able to weigh in soon with more detailed instructions 
how to get this configured properly.  I seem to remember that with the Gmail 
account that we used for testing, Gmail had to be told to allow the use of 
unsecured apps (though I’m not sure why exactly that was or might be).



Just so that I’m clear, though… Lydia, Kevin: it sounds like you have it 
configured to receive emails okay, but the emails to whomever requested the 
material is not being sent/received.  Is that correct?



Mark







-Original Message-
From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Kevin Clair
Sent: Thursday, 21 September, 2017 5:15 PM
To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" 
after requesting material via ArchivesSpace



We see similar behavior, and have turned off requesting on the public site 
because of it. The e-mail requests go through but the users see the error page 
instead of a confirmation. From the logs:







INFO: I, [2017-09-21T15:08:03.838360 #4548]  INFO -- : 
[5c583ccc-1669-40c4-9f90-81f09fac562b] Started POST "/fill_request" for 
192.168.123.1 at 2017-09-21 15:08:03 -0600







[the e-mail successfully sends here; log output omitted]







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log



INFO: I, [2017-09-21T15:08:09.740133 #4548]  INFO -- : 
[5c583ccc-1669-40c4-9f90-81f09fac562b] Completed 500 Internal Server Error in 
5862ms







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log



INFO: F, [2017-09-21T15:08:09.791554 #4548] FATAL -- : 
[5c583ccc-1669-40c4-9f90-81f09fac562b]







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log



INFO: F, [2017-09-21T15:08:09.797765 #4548] FATAL -- : 
[5c583ccc-1669-40c4-9f90-81f09fac562b] ActionView::Template::Error (undefined 
method `app_prefix' for #<#:0x59036603>):







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log



INFO: F, [2017-09-21T15:08:09.809421 #4548] FATAL -- : 
[5c583ccc-1669-40c4-9f90-81f09fac562b] 4:   Record Requested



[5c583ccc-1669-40c4-9f90-81f09fac562b] 5:   Title: <%= 
@request.title %>



[5c583ccc-1669-40c4-9f90-81f09fac562b] 6:   <% url = 
"#{AppConfig[:public_proxy_url].sub(/\/^/, 
'')}#{@request.request_uri}<mailto:%7d#{@request.request_uri}>" %>



[5c583ccc-1669-40c4-9f90-81f09fac562b] 7:   URL: <%= 
link_to url, app_prefix(url) %>



[5c583ccc-1669-40c4-9f90-81f09fac562b] 8: 



[5c583ccc-1669-40c4-9f90-8

Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

[Kevin Clair]

We see similar behavior, and have turned off requesting on the public site 
because of it. The e-mail requests go through but the users see the error page 
instead of a confirmation. From the logs:

INFO: I, [2017-09-21T15:08:03.838360 #4548]  INFO -- : 
[5c583ccc-1669-40c4-9f90-81f09fac562b] Started POST "/fill_request" for 
192.168.123.1 at 2017-09-21 15:08:03 -0600

[the e-mail successfully sends here; log output omitted]

Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: I, [2017-09-21T15:08:09.740133 #4548]  INFO -- : 
[5c583ccc-1669-40c4-9f90-81f09fac562b] Completed 500 Internal Server Error in 
5862ms

Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: F, [2017-09-21T15:08:09.791554 #4548] FATAL -- : 
[5c583ccc-1669-40c4-9f90-81f09fac562b]   

Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: F, [2017-09-21T15:08:09.797765 #4548] FATAL -- : 
[5c583ccc-1669-40c4-9f90-81f09fac562b] ActionView::Template::Error (undefined 
method `app_prefix' for #<#:0x59036603>):

Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: F, [2017-09-21T15:08:09.809421 #4548] FATAL -- : 
[5c583ccc-1669-40c4-9f90-81f09fac562b] 4:   Record Requested
[5c583ccc-1669-40c4-9f90-81f09fac562b] 5:   Title: <%= 
@request.title %>
[5c583ccc-1669-40c4-9f90-81f09fac562b] 6:   <% url = 
"#{AppConfig[:public_proxy_url].sub(/\/^/, '')}#{@request.request_uri}" %>
[5c583ccc-1669-40c4-9f90-81f09fac562b] 7:   URL: <%= 
link_to url, app_prefix(url) %>
[5c583ccc-1669-40c4-9f90-81f09fac562b] 8: 
[5c583ccc-1669-40c4-9f90-81f09fac562b] 9: 
[5c583ccc-1669-40c4-9f90-81f09fac562b]10: 

Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: F, [2017-09-21T15:08:09.810141 #4548] FATAL -- : 
[5c583ccc-1669-40c4-9f90-81f09fac562b]   

Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: F, [2017-09-21T15:08:09.810661 #4548] FATAL -- : 
[5c583ccc-1669-40c4-9f90-81f09fac562b] 
app/views/request_mailer/request_received_email.html.erb:7:in 
`_app_views_request_mailer_request_received_email_html_erb___227123848_2378'
[5c583ccc-1669-40c4-9f90-81f09fac562b] app/mailers/request_mailer.rb:7:in 
`request_received_email'
[5c583ccc-1669-40c4-9f90-81f09fac562b] 
app/controllers/requests_controller.rb:11:in `make_request'

-k

-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Tang, Lydia
Sent: Thursday, September 21, 2017 1:19 PM
To: 'archivesspace_users_group@lyralists.lyrasis.org'
Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after 
requesting material via ArchivesSpace

Hello, we recently upgraded from 2.1.1 from 1.5.3.  With our users taking 
advantage of the request feature through our PUI, they have received this 
“We’re sorry something went wrong” message after submitting their request.  Is 
this normal?  Is there a tweak we need to fill in order to gracefully conclude 
the request and return to the PUI?
Thanks!
Lydia
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] no indexer_pui_state files in backup.sh output

[Kevin Clair]

Hello,

I’ve noticed with the 2.* releases that when running scripts/backup.sh, the 
indexer_pui_state files aren’t included in the output, only the indexer_state 
files. Is that an issue I should submit to JIRA or am I missing something?

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

[Archivesspace_Users_Group] PUI search result question

[Kevin Clair]

Hello,

We upgraded to 2.1.1 about a week or two ago, and one of the issues our 
archivists noticed related to the new PUI is that collections show up very far 
down in the search results, relative to the staff interface. As an example, a 
keyword search for “peter dominick” in the staff interface returns the 
collection of his papers as the very first hit; at 
http://duarchives.coalliance.org, it doesn’t show up until page seven.

Is that something I can configure in the PUI settings in the config.rb file? 
For reference purposes it’s hard to have to scroll through multiple pages of 
results to land on the result for the collection. thanks!  -k
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Internal server error on public 'fill_request' page

[Kevin Clair]

Hello,

I'm working on getting e-mail requests set up in our new PUI, and have been 
encountering the following errors in the logs when ArchivesSpace attempts to 
display the request success page (key errors in bold):

Aug 23, 2017 12:42:10 PM 
org.eclipse.jetty.server.handler.ContextHandler$Context log
INFO: I, [2017-08-23T12:42:10.718672 #20482]  INFO -- : 
[c90e77e0-4387-4281-b38e-a533031ca293] Completed 500 Internal Server Error in 
8505ms

Aug 23, 2017 12:42:10 PM 
org.eclipse.jetty.server.handler.ContextHandler$Context log
INFO: F, [2017-08-23T12:42:10.752777 #20482] FATAL -- : 
[c90e77e0-4387-4281-b38e-a533031ca293]

Aug 23, 2017 12:42:10 PM 
org.eclipse.jetty.server.handler.ContextHandler$Context log
INFO: F, [2017-08-23T12:42:10.753720 #20482] FATAL -- : 
[c90e77e0-4387-4281-b38e-a533031ca293] ActionView::Template::Error (undefined 
method `app_prefix' for #<#:0x5ff8ec0>):

Aug 23, 2017 12:42:10 PM 
org.eclipse.jetty.server.handler.ContextHandler$Context log
INFO: F, [2017-08-23T12:42:10.764493 #20482] FATAL -- : 
[c90e77e0-4387-4281-b38e-a533031ca293] 4:   Record Requested
[c90e77e0-4387-4281-b38e-a533031ca293] 5:   Title: <%= 
@request.title %>
[c90e77e0-4387-4281-b38e-a533031ca293] 6:   <% url = 
"#{AppConfig[:public_proxy_url].sub(/\/^/, '')}#{@request.request_uri}" %>
[c90e77e0-4387-4281-b38e-a533031ca293] 7:   URL: <%= 
link_to url, app_prefix(url) %>
[c90e77e0-4387-4281-b38e-a533031ca293] 8: 
[c90e77e0-4387-4281-b38e-a533031ca293] 9:
[c90e77e0-4387-4281-b38e-a533031ca293]10: 

Aug 23, 2017 12:42:10 PM 
org.eclipse.jetty.server.handler.ContextHandler$Context log
INFO: F, [2017-08-23T12:42:10.766101 #20482] FATAL -- : 
[c90e77e0-4387-4281-b38e-a533031ca293]

Aug 23, 2017 12:42:10 PM 
org.eclipse.jetty.server.handler.ContextHandler$Context log
INFO: F, [2017-08-23T12:42:10.774380 #20482] FATAL -- : 
[c90e77e0-4387-4281-b38e-a533031ca293] 
app/views/request_mailer/request_received_email.html.erb:7:in 
`_app_views_request_mailer_request_received_email_html_erb__2099221818_2268'
[c90e77e0-4387-4281-b38e-a533031ca293] app/mailers/request_mailer.rb:7:in 
`request_received_email'
[c90e77e0-4387-4281-b38e-a533031ca293] 
app/controllers/requests_controller.rb:11:in `make_request'

Has anyone else encountered anything like this? I tried to fix it using a 
plugin to replace "app_prefix(url)" with some other link but I couldn't get the 
plugin to override the original page. Thanks in advance for any help provided!  
-k
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] RC 2.1 indexing slow

[Kevin Clair]

Hello,

I don't have any tips for speeding it up, but I've also noticed this on our 
development system, with all the same configuration settings as with previous 
2.* release candidates. Indexes that used to complete overnight for us take an 
entire day or more on 2.1.0-RC1.  -k

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Vandermillen, Michael
Sent: Wednesday, July 05, 2017 9:21 AM
To: Archivesspace Users Group (archivesspace_users_group@lyralists.lyrasis.org)
Subject: [Archivesspace_Users_Group] RC 2.1 indexing slow

Hi,
I'm finding indexing in rc2.1 to be very slow, much slower than 2.0. It starts 
off very fast with agents and subjects, but as soon it starts with resources, 
digital & archival objects, it's crawling. (I ran the db migr. script, deleted 
old solr index, and am running with plenty of memory - 24 g).

I know we have 2 solr indexes with 2x, but like I said, this is substantially 
slower than 2.0. Anyone else experiencing this? Any thoughts on tweaking the 
config? Apologies if I'm overlooking something obvious :)

Thanks-

Michael

Michael Vandermillen
Digital Library Software Engineer
Library Technology Services, Harvard University IT

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

[Archivesspace_Users_Group] creating one's own job types?

[Kevin Clair]

Hello,

Is it possible to create custom job types in addition to the four that ship 
with ArchivesSpace? I’ve been trying to re-write some batch download scripts I 
use as plugins, and some of them seem like they would make more sense as 
background jobs, but I couldn’t find documentation on how to do that anywhere 
and wasn’t sure if it’s a thing I can do.

Any advice would be appreciated, thanks!  -k
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Importing container profiles?

[Kevin Clair]

Hello,

Attached is a quick JSON dump of all the container profiles we have in Denver’s 
ArchivesSpace instance so far. You’ll probably want to have someone take out 
all the created/last modified data if you use this, and I’m not 100% sure the 
dimensions are exactly accurate (I rounded up to the nearest quarter inch), but 
it covers most of the Gaylord boxes we buy in bulk. Titles include 
human-readable names as well as the Gaylord product code.

We added these one by one through the staff interface, so I’m not sure if 
there’s a non-API method we could have used to do it in a batch.  -k

From:  on behalf of 
Celia Caust-Ellenbogen 
Reply-To: Archivesspace Group 
Date: Tuesday, October 18, 2016 at 8:45 AM
To: Archivesspace Group 
Subject: [Archivesspace_Users_Group] Importing container profiles?

Hello,

We've just migrated to v.1.5.1, so we need to create a whole bunch of container 
profiles. I know others have been in this exact same situation, and most of our 
boxes are the same as at every other repository.

  *   Does anyone have a list/spreadsheet/etc of container profiles they're 
willing to share, so I don't have to look up dimensions on a vendor website (or 
worse, head into the stacks with a yardstick)?
  *   Is there no way to import multiple container profiles at once from the 
ASpace staff interface? Or is the only way with the API?
Thanks,
Celia

--
Celia Caust-Ellenbogen
Friends Historical Library of Swarthmore 
College
610-328-8498
ccaus...@swarthmore.edu



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

Re: [Archivesspace_Users_Group] Question: where to change text from the PDF finding aids

[Kevin Clair]

Hi Kari,

It’s in the EAD serializer Ruby script, row 715: 
https://github.com/archivesspace/archivesspace/blob/f14f2e67f72281bffa4422c2fb5a355630573211/backend/app/exporters/serializers/ead.rb

I’d be interested to hear if it’s possible to change that text or remove it by 
editing the XSLT; we ended up doing it by editing that Ruby script directly via 
plugin.  -k

From:  on behalf of 
Kari R Smith 
Reply-To: Archivesspace Group 
Date: Tuesday, September 6, 2016 at 1:11 PM
To: Archivesspace Group 
Subject: [Archivesspace_Users_Group] Question: where to change text from the 
PDF finding aids

Hello - We've been successful with making some modifications to the 
as-ead-pdf.xsl stylesheet for printing to PDF.  However, we cannot figure out 
where in teh xsl file to change the text that displays on the cover sheet "This 
finding aid was produced using ArchivesSpace on September 06, 2016."

Can someone point me to where this text is located so we can modify it?

thanks!

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

Re: [Archivesspace_Users_Group] child records all export with c tags in EAD

[Kevin Clair]

Hello,

There’s a flag in the EAD export to turn numbered  tags on; is that checked 
when you run the export? I think ArchivesSpace defaults to ‘false’ for that 
option.

If you’re exporting through the API you can turn it on by appending 
‘numbered_cs=true’ to the end of the URL in the GET request.  -k

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Cobourn, Alston
Sent: Thursday, August 18, 2016 3:39 PM
To: 'Archivesspace Users Group'
Subject: [Archivesspace_Users_Group] child records all export with c tags in EAD

I’m exporting EAD to be added to a statewide consortial site for finding aids.  
All of the child records export as  tags in the EAD instead of hierarchical 
tags (c01, c02) regardless of how they are nested or the level of description 
they are marked as.

Is there any plan to change this?
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group