Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2

2021-04-23 Thread Brian Hoffman
Hi Cory,

It might be possible to eliminate the issue with the staff interface by setting 
an environment variable. For example:

BUNDLE_WITH="default" ./archivesspace.sh start

I think the issue with the public app is different and is going to require a 
follow-up release next week.

I am also curious to know what plugins you are using? Did you copy them over 
from your production install?

Brian


From:  on behalf of 
Cory Nimer 
Reply-To: Archivesspace Users Group 

Date: Friday, April 23, 2021 at 3:04 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2

We are currently running Java 1.8.0_282.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Blake 
Carver
Sent: Friday, April 23, 2021 10:53 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2

What's the JAVA version on there?

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Cory Nimer mailto:cory_ni...@byu.edu>>
Sent: Friday, April 23, 2021 12:42 PM
To: Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>; 
Archivesspace Users Group 
(archivesspace_users_group@lyralists.lyrasis.org)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2


Christine,



Here are the basic specs for our testing server according to our IT staff:



RHEL 8.3

4 procs

5GB RAM



For what it's worth, the error I posted that says there is a missing ruby gem 
is what I see if I go to the staff interface. If I go to the PUI, it will show 
a different missing ruby gem (sassc-2.4.0). Not sure if other pages might 
reveal other missing gems. Christine mentioned that others had seen a similar 
issue but the gem mentioned was different, so maybe they were looking at a 
different page. In any case it seems that somehow this build of ArchivesSpace 
is missing some required ruby gems.



If you need other information about the server, please let me know.



Best,



Cory



From: Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>
Sent: Friday, April 23, 2021 9:17 AM
To: Cory Nimer mailto:cory_ni...@byu.edu>>; Archivesspace 
Users Group 
(archivesspace_users_group@lyralists.lyrasis.org)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2



Hello Cory,



We're investigating a gem-related issue where the second release candidate is 
not running correctly on some kinds of servers. (We encountered something 
similar on a Windows server yesterday, though the gem mentioned was different.) 
Would you please post the specs of your server here or email them to me 
directly?



There was an issue that affected all Rails applications between the release of 
our first release candidate and our second one that required us to do some 
unplanned upgrades, though we were hopeful that the impact would be limited for 
3.0 since Rails came out with a fix for their issue during that timeframe. We 
definitely want to hear from people if they are experiencing issues installing 
RC2.



Thanks for your help,

Christine





From: Cory Nimer mailto:cory_ni...@byu.edu>>
Sent: Friday, April 23, 2021 10:18 AM
To: Archivesspace Users Group 
(archivesspace_users_group@lyralists.lyrasis.org)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>;
 Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>
Subject: RE: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2



Christine,



When installing the release candidate our IT staff reports that they are 
encountering an error, as described below:



I'm trying to get archivesspace v 3.0.0-RC2 running on our staging server. 
Everything seemed to install ok, and the server seems to start up ok (based on 
the log output), but when I try to bring up the public or staff website I get 
an error. I'm wondering if you could post something on the listserv or point me 
in the right direction to do it.



I upgraded from v2.8.1 and followed the upgrade directions here: 
https://archivesspace.github.io/tech-docs/administration/upgrading.html



Here's the error I get when I try to bring up the staff website 
(https://asadminstg.lib.byu.edu):



Internal Server Error (500)
Request Method: GET
Request URL: http://asadminstg.lib.byu.edu/
Could not find 

Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2

2021-04-23 Thread Cory Nimer
Brian,

We are currently running the following plugins:

AppConfig[:plugins] = ['local', 'byu-branding', 'user_defined_in_basic', 
'contentdm-get-metadata', 'archivesspace_export_service', 'tree_component_id', 
'aspace_sitemap']

Our IT staff did try running the release candidate without the plugins, though, 
and they reported that this did not change the errors they were receiving. At 
this point they have decided to stop testing on our end until the next release 
candidate, given the current installation issues.

Thanks for your help,

Cory

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Brian 
Hoffman
Sent: Friday, April 23, 2021 1:52 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2

Hi Cory,

It might be possible to eliminate the issue with the staff interface by setting 
an environment variable. For example:

BUNDLE_WITH="default" ./archivesspace.sh start

I think the issue with the public app is different and is going to require a 
follow-up release next week.

I am also curious to know what plugins you are using? Did you copy them over 
from your production install?

Brian


From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Cory Nimer mailto:cory_ni...@byu.edu>>
Reply-To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Friday, April 23, 2021 at 3:04 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2

We are currently running Java 1.8.0_282.

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Blake Carver
Sent: Friday, April 23, 2021 10:53 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2

What's the JAVA version on there?

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Cory Nimer mailto:cory_ni...@byu.edu>>
Sent: Friday, April 23, 2021 12:42 PM
To: Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>; 
Archivesspace Users Group 
(archivesspace_users_group@lyralists.lyrasis.org)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2


Christine,



Here are the basic specs for our testing server according to our IT staff:



RHEL 8.3

4 procs

5GB RAM



For what it's worth, the error I posted that says there is a missing ruby gem 
is what I see if I go to the staff interface. If I go to the PUI, it will show 
a different missing ruby gem (sassc-2.4.0). Not sure if other pages might 
reveal other missing gems. Christine mentioned that others had seen a similar 
issue but the gem mentioned was different, so maybe they were looking at a 
different page. In any case it seems that somehow this build of ArchivesSpace 
is missing some required ruby gems.



If you need other information about the server, please let me know.



Best,



Cory



From: Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>
Sent: Friday, April 23, 2021 9:17 AM
To: Cory Nimer mailto:cory_ni...@byu.edu>>; Archivesspace 
Users Group 
(archivesspace_users_group@lyralists.lyrasis.org)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2



Hello Cory,



We're investigating a gem-related issue where the second release candidate is 
not running correctly on some kinds of servers. (We encountered something 
similar on a Windows server yesterday, though the gem mentioned was different.) 
Would you please post the specs of your server here or email them to me 
directly?



There was an issue that affected all Rails applications between the release of 
our first release candidate and our second one that required us to do some 
unplanned upgrades, though we were hopeful that the impact would be limited for 
3.0 since Rails came out with a fix for their issue during that timeframe. We 
definitely want to hear from people if they are experiencing issues installing 
RC2.



Thanks for your help,

Christine





From: Cory Nimer mailto:cory_ni...@byu.edu>>
Sent: Friday, April 23, 2021 10:18 AM
To: Archivesspace Users 

[Archivesspace_Users_Group] Job announcement: Archivist for Digital Curation

2021-04-23 Thread Olga Virakhovskaya
Dear Colleagues,
The Bentley Historical Library at the University of Michigan seeks a
user-oriented, creative, collaborative, and self-motivated Archivist for
Digital Curation. Reporting to the Assistant Director for Curation, this
person will be primarily responsible for born-digital transfer (including
removable media), consulting on digital processing, and web archiving.
For the full job announcement including closing date, salary, and
application instructions, go to:
https://careers.umich.edu/job_detail/196761/archivist_for_digital_curation_assistantassociate

Please share widely!
Thank you.

Olga Virakhovskaya
Lead Archivist for Collections Management

  1150 Beal Avenue
  Ann Arbor, Michigan 48109-2113
  734-647-2737 
  www.bentley.umich.edu
  @UmichBentley

*The Bentley Historical Library acknowledges that coerced cessions of land
by the Anishinaabeg and Wyandot, including the grant by the Anishinaabeg
under the Treaty of the Foot of the Rapids for "the college at Detroit" so
that their children could be educated, made the University of Michigan
possible, and we seek to reaffirm the ancestral and contemporary ties of
these peoples to the University and the land where it now stands.*
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2

2021-04-23 Thread Blake Carver
What's the JAVA version on there?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Cory 
Nimer 
Sent: Friday, April 23, 2021 12:42 PM
To: Christine Di Bella ; Archivesspace Users 
Group (archivesspace_users_group@lyralists.lyrasis.org) 

Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2


Christine,



Here are the basic specs for our testing server according to our IT staff:



RHEL 8.3

4 procs

5GB RAM



For what it's worth, the error I posted that says there is a missing ruby gem 
is what I see if I go to the staff interface. If I go to the PUI, it will show 
a different missing ruby gem (sassc-2.4.0). Not sure if other pages might 
reveal other missing gems. Christine mentioned that others had seen a similar 
issue but the gem mentioned was different, so maybe they were looking at a 
different page. In any case it seems that somehow this build of ArchivesSpace 
is missing some required ruby gems.



If you need other information about the server, please let me know.



Best,



Cory



From: Christine Di Bella 
Sent: Friday, April 23, 2021 9:17 AM
To: Cory Nimer ; Archivesspace Users Group 
(archivesspace_users_group@lyralists.lyrasis.org) 

Subject: Re: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2



Hello Cory,



We're investigating a gem-related issue where the second release candidate is 
not running correctly on some kinds of servers. (We encountered something 
similar on a Windows server yesterday, though the gem mentioned was different.) 
Would you please post the specs of your server here or email them to me 
directly?



There was an issue that affected all Rails applications between the release of 
our first release candidate and our second one that required us to do some 
unplanned upgrades, though we were hopeful that the impact would be limited for 
3.0 since Rails came out with a fix for their issue during that timeframe. We 
definitely want to hear from people if they are experiencing issues installing 
RC2.



Thanks for your help,

Christine





From: Cory Nimer mailto:cory_ni...@byu.edu>>
Sent: Friday, April 23, 2021 10:18 AM
To: Archivesspace Users Group 
(archivesspace_users_group@lyralists.lyrasis.org)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>;
 Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>
Subject: RE: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2



Christine,



When installing the release candidate our IT staff reports that they are 
encountering an error, as described below:



I'm trying to get archivesspace v 3.0.0-RC2 running on our staging server. 
Everything seemed to install ok, and the server seems to start up ok (based on 
the log output), but when I try to bring up the public or staff website I get 
an error. I'm wondering if you could post something on the listserv or point me 
in the right direction to do it.



I upgraded from v2.8.1 and followed the upgrade directions here: 
https://archivesspace.github.io/tech-docs/administration/upgrading.html



Here's the error I get when I try to bring up the staff website 
(https://asadminstg.lib.byu.edu):



Internal Server Error (500)
Request Method: GET
Request URL: http://asadminstg.lib.byu.edu/
Could not find rubyntlm-0.6.3 in any of the sources from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
 `block in materialize' from org/jruby/RubyArray.java:2609:in `map!' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
 `materialize' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
 `specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:237:in
 `specs_for' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in
 `requested_specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:101:in
 `block in requested_specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:20:in
 `setup' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler.rb:149:in
 `setup' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `block in ' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:136:in
 `with_level' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:88:in
 `silence' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `' from 

Re: [Archivesspace_Users_Group] normalized begin/end date display in PUI

2021-04-23 Thread Alexander Duryee
Kevin - the timewalk plugin (https://github.com/alexduryee/timewalk) will
do exactly that.  I don't recall the exact source for parsing certainty (
https://github.com/alexduryee/timetwister/blob/master/lib/timetwister/utilities.rb#L18-L42),
but I based it on MODS, DCRM, and discussions with archivists/catalogers.

Benn - I'd argue that DACS-compliant Expressions are hardly bad data, but
I'm somewhat biased :)  Transforming Begin/End into clean Expressions is a
really good idea, although my primary concerns would be the number of
places that dates can appear (PUI and its PDF, SUI and its PDF,
EAD/MARC/OAI, etc.), and compressing a variety of ranges (e.g. "April 5 -
May 15, 1973" versus "1973 April 5 - May 15").  I'm sure with enough
examples of common formats and their compression, it should be achievable.

Thanks,
--Alex

On Fri, Apr 16, 2021 at 2:02 PM Benn Joseph 
wrote:

> Hi everyone,
>
> Thanks for your feedback! I did create and submit a new feature request
> for changing to more human-readable dates in the PUI (basically just
> replacing the month in ISO 8601 with the spelled out English equivalent),
> which is now ANW-1273
> .
>
>
>
> Mark, thanks for this background info—I’m also going to submit a linked
> request for compressing the date displays in the way you describe, which is
> a great idea but seems like it might need a separate ticket. Maybe a third
> step would be a customizable display as Dan mentions below.
>
>
>
> Kevin, what you’re describing is exactly what brought this up for us
> initially. I had proposed to folks here that maybe one way to get good
> human-readable dates in the PUI would be to enter them (consistently) as
> date expressions and then have Timewalk or Timetwister normalize them for
> us. But that seemed to be living a bit on the edge, and as a member of the
> team described it: “we shouldn’t be entering bad data on purpose and hoping
> that ASpace will magically fix it for us”. I like to think I received a lot
> of tough love that day 
>
>
>
> Thanks,
>
> --Benn
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of *Clair,
> Kevin
> *Sent:* Wednesday, April 14, 2021 10:58 AM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] normalized begin/end date
> display in PUI
>
>
>
> Hello,
>
>
>
> +1 to all of this. Our current use case seems to go the other way -- at
> Penn State the tendency is to have processing archivists provide
> human-readable date expressions, and that we would like to generate
> machine-readable begin and end dates based on that.
>
>
>
> I'm wondering how uncertain dates would figure into this. In both of the
> ArchivesSpace instances I'm familiar with there are a lot of "circa"s and
> "approximately"s, with varying ideas on how to encode them as begin and end
> dates.
>
>
>
> thanks!  -k
> --
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of
> Custer, Mark 
> *Sent:* Wednesday, April 14, 2021 10:01 AM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] normalized begin/end date
> display in PUI
>
>
>
> Benn,
>
>
>
> Yes, this is a great feature request!
>
>
>
> It was discussed as part of the PUI enhancement phase for 2.1, but never
> got added due to the additional work required (e.g., month names would also
> need to be added to the YML files for translation purposes).  It was also
> hoped that there might already be an adoptable codebase that would handle
> the logic of taking ISO-8601 (and, eventually, EDTF dates, which I think
> are now somewhat part of the newest release of ISO-8601) and transform
> those to human-readable values so that this would not have to be created
> from scratch for ArchivesSpace (maybe
> https://github.com/duke-libraries/edtf-humanize
> 
>  fits
> the bill now... at least it already has translation values, e.g.
> https://github.com/duke-libraries/edtf-humanize/blob/develop/config/locales/fr.edtf.yml#L6
> 

Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2

2021-04-23 Thread Christine Di Bella
Hello Cory,

We're investigating a gem-related issue where the second release candidate is 
not running correctly on some kinds of servers. (We encountered something 
similar on a Windows server yesterday, though the gem mentioned was different.) 
Would you please post the specs of your server here or email them to me 
directly?

There was an issue that affected all Rails applications between the release of 
our first release candidate and our second one that required us to do some 
unplanned upgrades, though we were hopeful that the impact would be limited for 
3.0 since Rails came out with a fix for their issue during that timeframe. We 
definitely want to hear from people if they are experiencing issues installing 
RC2.

Thanks for your help,
Christine


From: Cory Nimer 
Sent: Friday, April 23, 2021 10:18 AM
To: Archivesspace Users Group (archivesspace_users_group@lyralists.lyrasis.org) 
; Christine Di Bella 

Subject: RE: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2


Christine,



When installing the release candidate our IT staff reports that they are 
encountering an error, as described below:



I'm trying to get archivesspace v 3.0.0-RC2 running on our staging server. 
Everything seemed to install ok, and the server seems to start up ok (based on 
the log output), but when I try to bring up the public or staff website I get 
an error. I'm wondering if you could post something on the listserv or point me 
in the right direction to do it.



I upgraded from v2.8.1 and followed the upgrade directions here: 
https://archivesspace.github.io/tech-docs/administration/upgrading.html



Here's the error I get when I try to bring up the staff website 
(https://asadminstg.lib.byu.edu):



Internal Server Error (500)
Request Method: GET
Request URL: http://asadminstg.lib.byu.edu/
Could not find rubyntlm-0.6.3 in any of the sources from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
 `block in materialize' from org/jruby/RubyArray.java:2609:in `map!' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
 `materialize' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
 `specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:237:in
 `specs_for' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in
 `requested_specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:101:in
 `block in requested_specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:20:in
 `setup' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler.rb:149:in
 `setup' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `block in ' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:136:in
 `with_level' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:88:in
 `silence' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `' from org/jruby/RubyKernel.java:974:in `require' from 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:130:in
 `require' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/data/tmp/jetty-0.0.0.0-10080-frontend.war-_-any-/webapp/WEB-INF/config/boot.rb:10:in
 `' from org/jruby/RubyKernel.java:974:in `require' from 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:54:in
 `require' from uri:classloader:/jruby/rack/rails/environment3.rb:23:in 
`load_environment' from uri:classloader:/jruby/rack/rails_booter.rb:83:in 
`load_environment' from 

Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2

2021-04-23 Thread Cory Nimer
We are currently running Java 1.8.0_282.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Blake 
Carver
Sent: Friday, April 23, 2021 10:53 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2

What's the JAVA version on there?

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Cory Nimer mailto:cory_ni...@byu.edu>>
Sent: Friday, April 23, 2021 12:42 PM
To: Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>; 
Archivesspace Users Group 
(archivesspace_users_group@lyralists.lyrasis.org)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2


Christine,



Here are the basic specs for our testing server according to our IT staff:



RHEL 8.3

4 procs

5GB RAM



For what it's worth, the error I posted that says there is a missing ruby gem 
is what I see if I go to the staff interface. If I go to the PUI, it will show 
a different missing ruby gem (sassc-2.4.0). Not sure if other pages might 
reveal other missing gems. Christine mentioned that others had seen a similar 
issue but the gem mentioned was different, so maybe they were looking at a 
different page. In any case it seems that somehow this build of ArchivesSpace 
is missing some required ruby gems.



If you need other information about the server, please let me know.



Best,



Cory



From: Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>
Sent: Friday, April 23, 2021 9:17 AM
To: Cory Nimer mailto:cory_ni...@byu.edu>>; Archivesspace 
Users Group 
(archivesspace_users_group@lyralists.lyrasis.org)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2



Hello Cory,



We're investigating a gem-related issue where the second release candidate is 
not running correctly on some kinds of servers. (We encountered something 
similar on a Windows server yesterday, though the gem mentioned was different.) 
Would you please post the specs of your server here or email them to me 
directly?



There was an issue that affected all Rails applications between the release of 
our first release candidate and our second one that required us to do some 
unplanned upgrades, though we were hopeful that the impact would be limited for 
3.0 since Rails came out with a fix for their issue during that timeframe. We 
definitely want to hear from people if they are experiencing issues installing 
RC2.



Thanks for your help,

Christine





From: Cory Nimer mailto:cory_ni...@byu.edu>>
Sent: Friday, April 23, 2021 10:18 AM
To: Archivesspace Users Group 
(archivesspace_users_group@lyralists.lyrasis.org)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>;
 Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>
Subject: RE: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2



Christine,



When installing the release candidate our IT staff reports that they are 
encountering an error, as described below:



I'm trying to get archivesspace v 3.0.0-RC2 running on our staging server. 
Everything seemed to install ok, and the server seems to start up ok (based on 
the log output), but when I try to bring up the public or staff website I get 
an error. I'm wondering if you could post something on the listserv or point me 
in the right direction to do it.



I upgraded from v2.8.1 and followed the upgrade directions here: 
https://archivesspace.github.io/tech-docs/administration/upgrading.html



Here's the error I get when I try to bring up the staff website 
(https://asadminstg.lib.byu.edu):



Internal Server Error (500)
Request Method: GET
Request URL: http://asadminstg.lib.byu.edu/
Could not find rubyntlm-0.6.3 in any of the sources from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
 `block in materialize' from org/jruby/RubyArray.java:2609:in `map!' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
 `materialize' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
 `specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:237:in
 `specs_for' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in
 

Re: [Archivesspace_Users_Group] Changing Main PUI Search from OR to AND

2021-04-23 Thread Alexander Duryee
Bailey,

Starting in ArchivesSpace 2.8.0, you can pass Solr parameters to the PUI
via config/config.rb.  The default behavior in a fresh installation is
mm='100%', which I believe is (mostly) equivalent to using AND as the
default operator.  I tested this on test.archivesspace.org (3.0.0-RC2), and
it appears to be using AND as its default - for example, searching
"benjamin stockton" (without quotes) returns "Benjamin and Julia Stockton
Rush papers" but not "Benjamin Harrison papers".

If you're using 2.8.0 or newer, I would check the config/config.rb to see
if the following line is present and not commented out:
AppConfig[:solr_params] = { 'mm' => '100%' }

For older versions, you'll need to write a plug-in to override the default
Solr parameters generated by the PUI.

Thanks,
--Alex

On Thu, Apr 22, 2021 at 10:52 AM Hoffner, Bailey E.  wrote:

> Morning All,
>
>
>
> I know I’ve seen conversations about this before, but because I can’t
> think of the appropriate technical terminology, I haven’t been able to
> easily locate those convos in the listserv archive.
>
>
>
> We are interested in changing the automatic search function on the PUI
> from using “or” between search terms, to using “and.” Any help appreciated
> (including just pointing me to previous convos I wasn’t able to locate 
> ).
>
>
>
> -Bailey
>
>
>
> Bailey Hoffner, MLIS
>
> Pronouns: she/her/hers
>
> Metadata and Collections Management Archivist
>
> University of Oklahoma Libraries
>
> bail...@ou.edu
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Alexander Duryee
Metadata Archivist
New York Public Library
(917)-229-9590
alexanderdur...@nypl.org
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


[Archivesspace_Users_Group] Apply now for the ArchivesSpace Member Match program

2021-04-23 Thread Jessica Crouch
Dear ArchivesSpace Members,



As a reminder, there is one week left to apply for the ArchivesSpace Member 
Match program.  Applications are being accepted through April 30, 2021.



The Member Match program is an initiative to engage the ArchivesSpace 
membership community, created and organized by the Member Engagement sub-team 
of the ArchivesSpace User Advisory Council, with support from the ArchivesSpace 
Community Engagement Coordinator. The program is intended to be a resource and 
venue for peer-to-peer support between ArchivesSpace members. For one, 
year-long term, participants will be matched with a member with whom they can 
receive and offer professional insight, advice, and comradery. The program will 
also offer participants the opportunity to engage in exclusive events and 
enlightening discussions about ArchivesSpace and its active user community.


Eligibility


Any individual affiliated with an ArchivesSpace member organization is eligible 
to participate in the ArchivesSpace Member Match program and there is no limit 
to the number of individuals from a member organization that may participate.


If you are unsure of your organization’s ArchivesSpace membership status, visit 
https://archivesspace.org/community/whos-using-archivesspace or email 
archivesspaceh...@lyrasis.org.


To Apply


There is a short application to complete at 
https://airtable.com/shr1nE3RWpR7Y78En.


Applications should be submitted by April 30. Applicants will be notified of 
their matches no later than June 30.


To Learn More


Visit the Member Match wiki: 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2198568994/ArchivesSpace+Member+Match+Program


The ArchivesSpace Member Engagement Sub-team conducted an informational webinar 
on March 10th.  You can find a link to the recording of this webinar on the 
Member Match wiki.



Please feel free to direct any questions to 
archivesspaceh...@lyrasis.org


-Sent on behalf of the ArchivesSpace Member Engagement sub-team


Kate Blalack, American Song Archive

Regina Carra, American Folk Art Museum

Bailey Hoffner, University of Oklahoma

Ashley Knox, University of North Carolina Wilmington

Brittany Newberry, Atlanta University Center and ArchivesSpace User Advisory 
Council Chair

Jessica Crouch, ArchivesSpace Community Engagement Coordinator

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


Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2

2021-04-23 Thread Cory Nimer
Christine,

Here are the basic specs for our testing server according to our IT staff:

RHEL 8.3
4 procs
5GB RAM

For what it's worth, the error I posted that says there is a missing ruby gem 
is what I see if I go to the staff interface. If I go to the PUI, it will show 
a different missing ruby gem (sassc-2.4.0). Not sure if other pages might 
reveal other missing gems. Christine mentioned that others had seen a similar 
issue but the gem mentioned was different, so maybe they were looking at a 
different page. In any case it seems that somehow this build of ArchivesSpace 
is missing some required ruby gems.

If you need other information about the server, please let me know.

Best,

Cory

From: Christine Di Bella 
Sent: Friday, April 23, 2021 9:17 AM
To: Cory Nimer ; Archivesspace Users Group 
(archivesspace_users_group@lyralists.lyrasis.org) 

Subject: Re: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2

Hello Cory,

We're investigating a gem-related issue where the second release candidate is 
not running correctly on some kinds of servers. (We encountered something 
similar on a Windows server yesterday, though the gem mentioned was different.) 
Would you please post the specs of your server here or email them to me 
directly?

There was an issue that affected all Rails applications between the release of 
our first release candidate and our second one that required us to do some 
unplanned upgrades, though we were hopeful that the impact would be limited for 
3.0 since Rails came out with a fix for their issue during that timeframe. We 
definitely want to hear from people if they are experiencing issues installing 
RC2.

Thanks for your help,
Christine


From: Cory Nimer mailto:cory_ni...@byu.edu>>
Sent: Friday, April 23, 2021 10:18 AM
To: Archivesspace Users Group 
(archivesspace_users_group@lyralists.lyrasis.org)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>;
 Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>
Subject: RE: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2


Christine,



When installing the release candidate our IT staff reports that they are 
encountering an error, as described below:



I'm trying to get archivesspace v 3.0.0-RC2 running on our staging server. 
Everything seemed to install ok, and the server seems to start up ok (based on 
the log output), but when I try to bring up the public or staff website I get 
an error. I'm wondering if you could post something on the listserv or point me 
in the right direction to do it.



I upgraded from v2.8.1 and followed the upgrade directions here: 
https://archivesspace.github.io/tech-docs/administration/upgrading.html



Here's the error I get when I try to bring up the staff website 
(https://asadminstg.lib.byu.edu):



Internal Server Error (500)
Request Method: GET
Request URL: http://asadminstg.lib.byu.edu/
Could not find rubyntlm-0.6.3 in any of the sources from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
 `block in materialize' from org/jruby/RubyArray.java:2609:in `map!' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
 `materialize' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
 `specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:237:in
 `specs_for' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in
 `requested_specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:101:in
 `block in requested_specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:20:in
 `setup' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler.rb:149:in
 `setup' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `block in ' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:136:in
 `with_level' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:88:in
 `silence' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `' from org/jruby/RubyKernel.java:974:in `require' from 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:130:in
 `require' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/data/tmp/jetty-0.0.0.0-10080-frontend.war-_-any-/webapp/WEB-INF/config/boot.rb:10:in
 `' from org/jruby/RubyKernel.java:974:in `require' from 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:54:in
 

Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2

2021-04-23 Thread Cory Nimer
Christine,

When installing the release candidate our IT staff reports that they are 
encountering an error, as described below:

I'm trying to get archivesspace v 3.0.0-RC2 running on our staging server. 
Everything seemed to install ok, and the server seems to start up ok (based on 
the log output), but when I try to bring up the public or staff website I get 
an error. I'm wondering if you could post something on the listserv or point me 
in the right direction to do it.

I upgraded from v2.8.1 and followed the upgrade directions here: 
https://archivesspace.github.io/tech-docs/administration/upgrading.html

Here's the error I get when I try to bring up the staff website 
(https://asadminstg.lib.byu.edu):

Internal Server Error (500)
Request Method: GET
Request URL: http://asadminstg.lib.byu.edu/
Could not find rubyntlm-0.6.3 in any of the sources from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
 `block in materialize' from org/jruby/RubyArray.java:2609:in `map!' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
 `materialize' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
 `specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:237:in
 `specs_for' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in
 `requested_specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:101:in
 `block in requested_specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:20:in
 `setup' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler.rb:149:in
 `setup' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `block in ' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:136:in
 `with_level' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:88:in
 `silence' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `' from org/jruby/RubyKernel.java:974:in `require' from 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:130:in
 `require' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/data/tmp/jetty-0.0.0.0-10080-frontend.war-_-any-/webapp/WEB-INF/config/boot.rb:10:in
 `' from org/jruby/RubyKernel.java:974:in `require' from 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:54:in
 `require' from uri:classloader:/jruby/rack/rails/environment3.rb:23:in 
`load_environment' from uri:classloader:/jruby/rack/rails_booter.rb:83:in 
`load_environment' from