Re: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin
Try updating the Gemfile.lock to use the 4.0.6 version of the gem and then run the initialize_plugin script. I'm pretty sure that was how I got around the issue at one point. You just need to get the plugin bundled. Version does not matter (in my experience). Tom On Tue, Dec 6, 2022 at 3:03 PM David P. Steelman wrote: > Thanks for the quick responses. > > I have tried using aspace-oauth v3.2.0, and am running the > 'initialize_plugin" script, and still receiving the same error. > > On the server, there is a > "plugins/aspace-oauth/gems/cache/public_suffix-4.0.7.gem" file, and a > "plugins/aspace-oauth/gems/gems/public_suffix-4.0.7" directory, so the > "aspace-oauth" gem appears to be using the "public_suffix:4.0.7" gem > > The "WEB-INF/Gemfile.lock" file in the "public.war" and "frontend.war" WAR > files from the ArchivesSpace distribution each contain a reference to > "public_suffix" v4.0.6. > > In the ArchivesSpace v3.3.1 source distribution there are references to > "plugin_suffix:4.0.6" in the following files: > > * Gemfile.lock > * docs/Gemfile.lock > * frontend/Gemfile.lock > * public/Gemfile.lock > > So I'm wondering if there is some kind of confusion about which version of > the gem is supposed to be used. > > Thanks, > > David > > On Tue, Dec 6, 2022 at 2:55 PM Tom Hanstra wrote: > >> There was a version of the aspace-oauth plugin in which the public_suffix >> gem did not compile. I remember having some problems with that. >> >> I just rebuilt mine here and it looks like the current version is working >> right, with the 4.0.7 version. So it may help to simply download again. >> >> Tom >> >> On Tue, Dec 6, 2022 at 2:19 PM Blake Carver >> wrote: >> >>> Try using the latest tag version on that plugin. >>> >>> >>> https://github.com/lyrasis/aspace-oauth/tags >>> -- >>> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < >>> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of >>> David P. Steelman >>> *Sent:* Tuesday, December 6, 2022 2:02 PM >>> *To:* Archivesspace Users Group < >>> archivesspace_users_group@lyralists.lyrasis.org> >>> *Subject:* [Archivesspace_Users_Group] Startup error with ArchivesSpace >>> v3.3.1/aspace-oauth plugin >>> >>> Hello all, >>> >>> In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am >>> encountering the following error on startup: >>> >>> >>> Dec 05, 2022 8:23:43 PM >>> org.eclipse.jetty.server.handler.ContextHandler$Context log >>> WARNING: ERROR: initialization failed >>> org.jruby.rack.RackInitializationException: Could not find >>> public_suffix-4.0.6 in any of the sources >>> from >>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in >>> `block in materialize' >>> from org/jruby/RubyArray.java:2621:in `map!' >>> from >>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in >>> `materialize' >>> from >>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in >>> `specs' >>> ... >>> >>> >>> We are using the "aspace-oauth" plugin ( >>> https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin >>> from the configuration the error does not occur. >>> >>> Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the >>> "gems/gems" directory in the v3.3.1 distribution includes significantly >>> fewer gems, and no longer includes a "public_suffix-3.0.6" directory. >>> >>> Any pointers in handling this issue are appreciated. >>> >>> Thanks, >>> >>> David >>> ___ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group@lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >> >> >> -- >> *Tom Hanstra* >> *Sr. Systems Administrator* >> hans...@nd.edu >> >> >> ___ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group@lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hans...@nd.edu ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin
Thanks for the quick responses. I have tried using aspace-oauth v3.2.0, and am running the 'initialize_plugin" script, and still receiving the same error. On the server, there is a "plugins/aspace-oauth/gems/cache/public_suffix-4.0.7.gem" file, and a "plugins/aspace-oauth/gems/gems/public_suffix-4.0.7" directory, so the "aspace-oauth" gem appears to be using the "public_suffix:4.0.7" gem The "WEB-INF/Gemfile.lock" file in the "public.war" and "frontend.war" WAR files from the ArchivesSpace distribution each contain a reference to "public_suffix" v4.0.6. In the ArchivesSpace v3.3.1 source distribution there are references to "plugin_suffix:4.0.6" in the following files: * Gemfile.lock * docs/Gemfile.lock * frontend/Gemfile.lock * public/Gemfile.lock So I'm wondering if there is some kind of confusion about which version of the gem is supposed to be used. Thanks, David On Tue, Dec 6, 2022 at 2:55 PM Tom Hanstra wrote: > There was a version of the aspace-oauth plugin in which the public_suffix > gem did not compile. I remember having some problems with that. > > I just rebuilt mine here and it looks like the current version is working > right, with the 4.0.7 version. So it may help to simply download again. > > Tom > > On Tue, Dec 6, 2022 at 2:19 PM Blake Carver > wrote: > >> Try using the latest tag version on that plugin. >> >> >> https://github.com/lyrasis/aspace-oauth/tags >> -- >> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < >> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of >> David P. Steelman >> *Sent:* Tuesday, December 6, 2022 2:02 PM >> *To:* Archivesspace Users Group < >> archivesspace_users_group@lyralists.lyrasis.org> >> *Subject:* [Archivesspace_Users_Group] Startup error with ArchivesSpace >> v3.3.1/aspace-oauth plugin >> >> Hello all, >> >> In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am >> encountering the following error on startup: >> >> >> Dec 05, 2022 8:23:43 PM >> org.eclipse.jetty.server.handler.ContextHandler$Context log >> WARNING: ERROR: initialization failed >> org.jruby.rack.RackInitializationException: Could not find >> public_suffix-4.0.6 in any of the sources >> from >> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in >> `block in materialize' >> from org/jruby/RubyArray.java:2621:in `map!' >> from >> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in >> `materialize' >> from >> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in >> `specs' >> ... >> >> >> We are using the "aspace-oauth" plugin ( >> https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin >> from the configuration the error does not occur. >> >> Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the >> "gems/gems" directory in the v3.3.1 distribution includes significantly >> fewer gems, and no longer includes a "public_suffix-3.0.6" directory. >> >> Any pointers in handling this issue are appreciated. >> >> Thanks, >> >> David >> ___ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group@lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hans...@nd.edu > > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin
There was a version of the aspace-oauth plugin in which the public_suffix gem did not compile. I remember having some problems with that. I just rebuilt mine here and it looks like the current version is working right, with the 4.0.7 version. So it may help to simply download again. Tom On Tue, Dec 6, 2022 at 2:19 PM Blake Carver wrote: > Try using the latest tag version on that plugin. > > > https://github.com/lyrasis/aspace-oauth/tags > -- > *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < > archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of > David P. Steelman > *Sent:* Tuesday, December 6, 2022 2:02 PM > *To:* Archivesspace Users Group < > archivesspace_users_group@lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Startup error with ArchivesSpace > v3.3.1/aspace-oauth plugin > > Hello all, > > In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am > encountering the following error on startup: > > > Dec 05, 2022 8:23:43 PM > org.eclipse.jetty.server.handler.ContextHandler$Context log > WARNING: ERROR: initialization failed > org.jruby.rack.RackInitializationException: Could not find > public_suffix-4.0.6 in any of the sources > from > /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in > `block in materialize' > from org/jruby/RubyArray.java:2621:in `map!' > from > /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in > `materialize' > from > /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in > `specs' > ... > > > We are using the "aspace-oauth" plugin ( > https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin from > the configuration the error does not occur. > > Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the "gems/gems" > directory in the v3.3.1 distribution includes significantly fewer gems, and > no longer includes a "public_suffix-3.0.6" directory. > > Any pointers in handling this issue are appreciated. > > Thanks, > > David > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hans...@nd.edu ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin
Try using the latest tag version on that plugin. https://github.com/lyrasis/aspace-oauth/tags From: archivesspace_users_group-boun...@lyralists.lyrasis.org on behalf of David P. Steelman Sent: Tuesday, December 6, 2022 2:02 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin Hello all, In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am encountering the following error on startup: Dec 05, 2022 8:23:43 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: Could not find public_suffix-4.0.6 in any of the sources from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in `block in materialize' from org/jruby/RubyArray.java:2621:in `map!' from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `materialize' from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in `specs' ... We are using the "aspace-oauth" plugin (https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin from the configuration the error does not occur. Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the "gems/gems" directory in the v3.3.1 distribution includes significantly fewer gems, and no longer includes a "public_suffix-3.0.6" directory. Any pointers in handling this issue are appreciated. Thanks, David ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin
Be sure to run the initialize_plugin script again after the upgrade. Tom On Tue, Dec 6, 2022 at 2:06 PM David P. Steelman wrote: > Hello all, > > In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am > encountering the following error on startup: > > > Dec 05, 2022 8:23:43 PM > org.eclipse.jetty.server.handler.ContextHandler$Context log > WARNING: ERROR: initialization failed > org.jruby.rack.RackInitializationException: Could not find > public_suffix-4.0.6 in any of the sources > from > /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in > `block in materialize' > from org/jruby/RubyArray.java:2621:in `map!' > from > /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in > `materialize' > from > /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in > `specs' > ... > > > We are using the "aspace-oauth" plugin ( > https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin from > the configuration the error does not occur. > > Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the "gems/gems" > directory in the v3.3.1 distribution includes significantly fewer gems, and > no longer includes a "public_suffix-3.0.6" directory. > > Any pointers in handling this issue are appreciated. > > Thanks, > > David > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hans...@nd.edu ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin
Hello all, In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am encountering the following error on startup: Dec 05, 2022 8:23:43 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: Could not find public_suffix-4.0.6 in any of the sources from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in `block in materialize' from org/jruby/RubyArray.java:2621:in `map!' from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `materialize' from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in `specs' ... We are using the "aspace-oauth" plugin ( https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin from the configuration the error does not occur. Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the "gems/gems" directory in the v3.3.1 distribution includes significantly fewer gems, and no longer includes a "public_suffix-3.0.6" directory. Any pointers in handling this issue are appreciated. Thanks, David ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] How does searching with the dates filled out work?
All dates in the "Dates" section of a record are indexed for use in
date-range searches, regardless of the label.
For example, if something was created between 1880 and 1885, but it was
also published in June 1950, and digitized on 4th May 2010, then it'll
be indexed with the years 1880, 1881, 1882, 1883, 1884, 1885, 1950, and
2010. Therefore, as well as matching searches with a date range of
1800-1900, it'll also match 1900-2000, or even 2000-present. But it
won't match dates ranges in the gaps between, i.e. any subset of
1886-1949 or 1951-2009.
It would be possible to write a plug-in to choose which dates to index.
Andrew.
On 05/12/2022 17:08, Tessa Wakefield wrote:
Hello!
Forgive me if this is a silly question -- we're new to using
ArchivesSpace! I'm confused as to how the dates work when entered in
the search function ("From year" and "To year" boxes). Does narrowing
your search by date range only pull records marked with dates that
fall within? I've tried doing this in our Aspace instance, as well as
in a few others, and results show up that are not within the dates.
For example, with a parameter of 1900 to 2000, results with dates from
the 1800s were included. I think I'm not understanding how this
actually works and before we go live for our users to access our
finding aids, I want to make sure we know what we're talking about!
Thanks!
--
*Tessa Wakefield(she/her .*
UNI / University of Northern Iowa**
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
