From Jessica.Crouch at lyrasis.org Mon Nov 2 10:56:23 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 2 Nov 2020 15:56:23 +0000 Subject: [Archivesspace_Users_Group] =?utf-8?q?ArchivesSpace_Open_Communit?= =?utf-8?q?y_Call_=E2=80=93_November_11_at_2pm_ET_=2811am_PT=29?= Message-ID: <83020A12-07D9-46F0-89C6-03E23024BD3D@lyrasis.org> Dear ArchivesSpace Members, Please join us for our next community Zoom call on November 11, 2020 at 2-3pm ET (11-noon PT). This is an opportunity to hear updates from each other and encourage group discussion. This is a space to surface news, ideas, and challenges. This might be an especially good chance to talk about non-technical questions or ideas that you weren?t quite sure about posting on the Users Group listserv but really would like help with from us or your peers. Please register in advance at: https://lyrasis.zoom.us/meeting/register/tJYsdOGrrTwrEtSEV7bbUTXlp1KbAOHkdnaO After registering, you will receive a confirmation email containing information about how to join the call. If you have a question or topic you'd like to have addressed in the call, you can submit it when you register or email Jessica Crouch at jessica.crouch at lyrasis.org by November 10 at 5pm ET. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 8548 bytes Desc: image001.jpg URL: From VivianLea.Solek at Kofc.Org Mon Nov 2 13:00:51 2020 From: VivianLea.Solek at Kofc.Org (Solek, VivianLea) Date: Mon, 2 Nov 2020 18:00:51 +0000 Subject: [Archivesspace_Users_Group] Help Please - System Setup Before Data Import Message-ID: Good afternoon, I am ready to start importing data into ASpace, but I know there are things I need to do to set up my ASpace instance before I hit "import." I know I need to 1. Set My Repository Preferences (including controlled vocabulary lists) 2. Import location codes 3. Arrange notes per DACS order 4. Create top container profiles. Are there things you wish someone had told you before import? Other things I should set up before importing? I'm working through the video tutorials in the Help Center, but I don't see a video titled "Setting Up ASpace Prior to Import" that would answer my questions. Thank you all VERY much for any and all suggestions you may have! All the best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Mon Nov 2 18:00:55 2020 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 2 Nov 2020 23:00:55 +0000 Subject: [Archivesspace_Users_Group] release candidate available - ArchivesSpace v2.8.1-RC1 Message-ID: Hello ArchivesSpace members, The ArchivesSpace team is pleased to announce a release candidate, v2.8.0-RC1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.8.1-RC1 or test it out without downloading at http://test.archivesspace.org/staff (username admin /password admin). This release candidate includes improvements to the spreadsheet importer, additional settable record type preferences, some bug fixes and small feature improvements, additional translations for the public interface and reports, and a number of infrastructure upgrades. Included within these are a number of performance, indexer, and small backend and staff interface improvements courtesy of work Hudson Molonglo developers James Bullen, Mark Triggs, and Payten Giles did for Queensland State Archives as part of a larger project. For spreadsheet importer fans: Some changes have been made to the spreadsheet importer in this release candidate to extend its functionality and improve its performance, especially with large spreadsheets. Of particular note: there is now a validation option so that a user can do a test run with a file, providing the opportunity to clean up any errors outside ArchivesSpace before doing the actual import; the importer now accepts either Excel spreadsheets or CSV files that use the templates at https://github.com/archivesspace/archivesspace/tree/master/templates; and, while it is accessed from a resource record or resource component as before, the import now runs as a background job so that it can more easily handle large files and to make the log file downloadable and saved within ArchivesSpace. Also, a number of bugs that were introduced with the conversion of the spreadsheet from a plugin to ArchivesSpace have been fixed for this release. We encourage you to test these improvements, especially for the spreadsheet importer, with your own data if you can. (Hey, there are worse ways to pass time this week than importing a few gnarly spreadsheets!) Every bit of testing and feedback helps us ensure that the changes are doing what they should and improves the release. Thanks to the many community members who made contributions to this release, including both individual archives staff and developers, as well as our Development Prioritization sub-team, Testing sub-team, and Core Committers Group. It also benefitted from some friendly Hacktoberfest competition among the ArchivesSpace and extended LYRASIS team. Please try this release candidate out over the next few days and let us know at ArchivesSpaceHome at lyrasis.org by November 9 if you notice any problems with the specific areas addressed in this release, or if anything that was working before no longer is. Assuming good testing results we're aiming to put out the release itself next week. Please get in touch if you have any questions. Thanks as always for your feedback and support. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6609 bytes Desc: image003.jpg URL: From rodmang at ripon.edu Tue Nov 3 15:46:06 2020 From: rodmang at ripon.edu (Rodman, Gary) Date: Tue, 3 Nov 2020 14:46:06 -0600 Subject: [Archivesspace_Users_Group] sudden inablilty to access archivesspace Message-ID: We had a perfectly good instance of archivesspace 2.6 running on windows server 2012 R2. Then something unidentified happened, and now the staff interface and public interface will not load at all. The back end interface produces this error: Internal Server Error (500) Request Method: GET Request URL: http://localhost:8089/ Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 from com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:129) from com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:97) from com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:89) from com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:63) from com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:73) from com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(com/mysql/cj/jdbc/exceptions/SQLExceptionsMapping.java:85) from com.mysql.cj.jdbc.result.ResultSetImpl.getTimestamp(com/mysql/cj/jdbc/result/ResultSetImpl.java:1019) from java.lang.reflect.Method.invoke(java/lang/reflect/Method) from org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) from org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther0:getTimestamp(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:657) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in timestamp_convertor(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:657) from org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) from org.jruby.RubyProc.call19(org/jruby/RubyProc.java:273) from org.jruby.RubyProc$INVOKER$i$0$0$call19.call(org/jruby/RubyProc$INVOKER$i$0$0$call19.gen) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther10:call(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:795) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in process_result_set(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:795) from org.jruby.RubyArray.each(org/jruby/RubyArray.java:1735) from org.jruby.RubyArray$INVOKER$i$0$0$each.call(org/jruby/RubyArray$INVOKER$i$0$0$each.gen) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther33:each(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:794) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.process_result_set(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:794) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther0:process_result_set(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in fetch_rows(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.statement(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:646) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther29:statement(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:85) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther3:hold(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther41:synchronize(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.execute(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther9:execute(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.execute(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther2:execute(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.fetch_rows(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther3:fetch_rows(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:801) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.with_sql_each(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:801) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther1:with_sql_each(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:811) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.with_sql_first(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:811) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.placeholder_literalizer.invokeOther2:with_sql_first(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/placeholder_literalizer.rb:148) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.placeholder_literalizer.first(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/placeholder_literalizer.rb:148) from org.jruby.RubyClass.finvoke(org/jruby/RubyClass.java:523) from org.jruby.RubyBasicObject.send19(org/jruby/RubyBasicObject.java:1684) from org.jruby.RubyKernel.send19(org/jruby/RubyKernel.java:2018) from org.jruby.RubyKernel$INVOKER$s$send19.call(org/jruby/RubyKernel$INVOKER$s$send19.gen) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.model.base.invokeOther1:send(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/model/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/model/base.rb:878) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.model.base.block in def_finder_method(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/model/base.rb:878) from org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.model.base.invokeOther4:first_where(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/model/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/model/base.rb:110) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.model.base.[](D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/model/base.rb:110) from RUBY.create_system_user(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:4) from RUBY.create_hidden_system_user(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:21) from RUBY.create_search_user(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:302) from RUBY.(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:326) from RUBY.
(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:1) from org.jruby.Ruby.runInterpreter(org/jruby/Ruby.java:842) from org.jruby.Ruby.loadFile(org/jruby/Ruby.java:2903) from org.jruby.RubyKernel.requireCommon(org/jruby/RubyKernel.java:963) from org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) from org.jruby.RubyKernel$INVOKER$s$1$0$require19.call(org/jruby/RubyKernel$INVOKER$s$1$0$require19.gen) from uri_3a_classloader_3a_.jruby.kernel.kernel.invokeOther18:require(uri_3a_classloader_3a_/jruby/kernel/uri:classloader:/jruby/kernel/kernel.rb:13) from uri_3a_classloader_3a_.jruby.kernel.kernel.require_relative(uri:classloader:/jruby/kernel/kernel.rb:13) from RUBY.block in (root)(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1) from RUBY.block in ArchivesSpaceService(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:194) from RUBY.block in open(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111) from RUBY.transaction(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75) from RUBY.block in _transaction(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther3:hold(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) from RUBY.transaction(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108) from RUBY.transaction(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97) from RUBY.block in transaction(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74) from org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:305) from org.jruby.RubyFixnum$INVOKER$i$0$0$times.call(org/jruby/RubyFixnum$INVOKER$i$0$0$times.gen) from RUBY.open(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110) from org.jruby.RubyClass.finvoke(org/jruby/RubyClass.java:523) from org.jruby.RubyBasicObject.send19(org/jruby/RubyBasicObject.java:1684) from org.jruby.RubyKernel.send19(org/jruby/RubyKernel.java:2018) from org.jruby.RubyKernel$INVOKER$s$send19.call(org/jruby/RubyKernel$INVOKER$s$send19.gen) from RUBY.block in open(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107) from org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) from RUBY.block in open(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432) from RUBY.ArchivesSpaceService(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:193) from RUBY.(D:/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411) from RUBY.
(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78) from org.jruby.Ruby.runInterpreter(org/jruby/Ruby.java:842) from org.jruby.Ruby.loadFile(org/jruby/Ruby.java:2903) from org.jruby.RubyKernel.requireCommon(org/jruby/RubyKernel.java:963) from org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) from org.jruby.RubyKernel$INVOKER$s$1$0$require19.call(org/jruby/RubyKernel$INVOKER$s$1$0$require19.gen) from RUBY.(root)(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38) from RUBY.block in (root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) from org.jruby.RubyBasicObject.yieldUnder(org/jruby/RubyBasicObject.java:1791) from org.jruby.RubyBasicObject.specificEval(org/jruby/RubyBasicObject.java:1810) from org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1691) from org.jruby.RubyBasicObject$INVOKER$i$instance_eval19.call(org/jruby/RubyBasicObject$INVOKER$i$instance_eval19.gen) from RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) from org.jruby.RubyClass.newInstance(org/jruby/RubyClass.java:1023) from org.jruby.RubyClass$INVOKER$i$newInstance.call(org/jruby/RubyClass$INVOKER$i$newInstance.gen) from RUBY.
(D:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\ config.ru:4) from org.jruby.Ruby.runInterpreter(org/jruby/Ruby.java:847) from org.jruby.Ruby.runInterpreter(org/jruby/Ruby.java:851) from org.jruby.Ruby.executeScript(org/jruby/Ruby.java:508) from org.jruby.rack.DefaultRackApplicationFactory.createRackServletWrapper(org/jruby/rack/DefaultRackApplicationFactory.java:239) from org.jruby.rack.DefaultRackApplicationFactory.createApplicationObject(org/jruby/rack/DefaultRackApplicationFactory.java:168) from org.jruby.rack.DefaultRackApplicationFactory$1.create(org/jruby/rack/DefaultRackApplicationFactory.java:101) from org.jruby.rack.DefaultRackApplicationFactory$RackApplicationImpl.init(org/jruby/rack/DefaultRackApplicationFactory.java:445) from org.jruby.rack.DefaultRackApplicationFactory.getApplication(org/jruby/rack/DefaultRackApplicationFactory.java:114) from org.jruby.rack.SharedRackApplicationFactory.doInit(org/jruby/rack/SharedRackApplicationFactory.java:34) from org.jruby.rack.RackApplicationFactoryDecorator.init(org/jruby/rack/RackApplicationFactoryDecorator.java:100) from org.jruby.rack.RackServletContextListener.contextInitialized(org/jruby/rack/RackServletContextListener.java:50) from org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(org/eclipse/jetty/server/handler/ContextHandler.java:766) from org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(org/eclipse/jetty/servlet/ServletContextHandler.java:406) from org.eclipse.jetty.server.handler.ContextHandler.startContext(org/eclipse/jetty/server/handler/ContextHandler.java:758) from org.eclipse.jetty.servlet.ServletContextHandler.startContext(org/eclipse/jetty/servlet/ServletContextHandler.java:242) from org.eclipse.jetty.webapp.WebAppContext.startContext(org/eclipse/jetty/webapp/WebAppContext.java:1233) from org.eclipse.jetty.server.handler.ContextHandler.doStart(org/eclipse/jetty/server/handler/ContextHandler.java:701) from org.eclipse.jetty.webapp.WebAppContext.doStart(org/eclipse/jetty/webapp/WebAppContext.java:475) from org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59) from org.eclipse.jetty.server.handler.HandlerCollection.doStart(org/eclipse/jetty/server/handler/HandlerCollection.java:224) from org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(org/eclipse/jetty/server/handler/ContextHandlerCollection.java:167) from org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59) from org.eclipse.jetty.server.handler.HandlerWrapper.doStart(org/eclipse/jetty/server/handler/HandlerWrapper.java:90) from org.eclipse.jetty.server.Server.doStart(org/eclipse/jetty/server/Server.java:272) from org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59) from java.lang.reflect.Method.invoke(java/lang/reflect/Method) from org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438) from org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302) from launcher.launcher.invokeOther155:start(launcher/launcher.rb:92) from launcher.launcher.start_server(launcher/launcher.rb:92) from launcher.launcher.invokeOther290:start_server(launcher/launcher.rb:157) from launcher.launcher.main(launcher/launcher.rb:157) from launcher.launcher.invokeOther503:main(launcher/launcher.rb:261) from launcher.launcher.
(launcher/launcher.rb:261) from java.lang.invoke.MethodHandle.invokeWithArguments(java/lang/invoke/MethodHandle) from org.jruby.Ruby.runScript(org/jruby/Ruby.java:830) from org.jruby.Ruby.runNormally(org/jruby/Ruby.java:749) from org.jruby.Ruby.runNormally(org/jruby/Ruby.java:767) from org.jruby.Ruby.runFromMain(org/jruby/Ruby.java:580) from org.jruby.Main.doRunFromMain(org/jruby/Main.java:417) from org.jruby.Main.internalRun(org/jruby/Main.java:305) from org.jruby.Main.run(org/jruby/Main.java:232) from org.jruby.Main.main(org/jruby/Main.java:204) You're seeing this error because you use JRuby::Rack::ErrorApp::ShowStatus. No idea how to troubleshoot - any advice appreciated. Thank you Gary *Gary Rodman *(he/him) Director of Enterprise Applications Ripon College 300 W. Seward St. Ripon, WI 54971 (direct) 920-748-83 <920-748-8365>43 RodmanG at ripon.edu [image: image.png] Visit us at *ripon.edu * -- _This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information.? Any review, dissemination, copying, printing, or other use of this email by persons or entities other than the addressee is prohibited. If you have received this email in error, please contact the sender immediately and delete the material from your computer._ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 17747 bytes Desc: not available URL: From blake.carver at lyrasis.org Tue Nov 3 15:57:12 2020 From: blake.carver at lyrasis.org (Blake Carver) Date: Tue, 3 Nov 2020 20:57:12 +0000 Subject: [Archivesspace_Users_Group] sudden inablilty to access archivesspace In-Reply-To: References: Message-ID: Several users have reported this problem to us in various ways. This error isn't unique to ArchivesSpace, but ArchivesSpace can be affected by it if you have timestamps in the hour that never happened (between 2 and 3am) in the search_indexer row in the user table. We're not sure how this would happen, but maybe if your server got restarted around that time? If you get rid of those errant times that problem should go away. Try this: MySQL [archivesspace]> select * from auth_db; +------+------------------+---------------------+---------------------+--------------------------------------------------------------+ | id | username | create_time | system_mtime | pwhash | +------+------------------+---------------------+---------------------+--------------------------------------------------------------+ | 1 | admin | 2016-03-09 07:10:13 | 2016-03-09 07:10:13 | $2a$10$Gp0oqAuyVXmG/M1s7XDcTuz8.6aTRooPxbf.AWNUuhxNvzsjTa7om | | 2 | search_indexer | 2016-03-09 07:10:14 | 2019-10-05 08:33:40 | $2a$10$WEoh7JjTOFZ.m.ih9sbxPOHomfcReIBlnAoRQceAbwWFK0DuyC8Tm | Take a look atsearch_indexer and the 2 times. The system_time is probably the one with the bad hour. You can just update that the current time and that should do it. So something like update auth_db set system_mtime = NOW()where username = search_indexer. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Rodman, Gary Sent: Tuesday, November 3, 2020 3:46 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] sudden inablilty to access archivesspace We had a perfectly good instance of archivesspace 2.6 running on windows server 2012 R2. Then something unidentified happened, and now the staff interface and public interface will not load at all. The back end interface produces this error: Internal Server Error (500) Request Method: GET Request URL: http://localhost:8089/ Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3 from com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:129) from com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:97) from com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:89) from com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:63) from com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:73) from com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(com/mysql/cj/jdbc/exceptions/SQLExceptionsMapping.java:85) from com.mysql.cj.jdbc.result.ResultSetImpl.getTimestamp(com/mysql/cj/jdbc/result/ResultSetImpl.java:1019) from java.lang.reflect.Method.invoke(java/lang/reflect/Method) from org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) from org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther0:getTimestamp(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:657) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in timestamp_convertor(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:657) from org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) from org.jruby.RubyProc.call19(org/jruby/RubyProc.java:273) from org.jruby.RubyProc$INVOKER$i$0$0$call19.call(org/jruby/RubyProc$INVOKER$i$0$0$call19.gen) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther10:call(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:795) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in process_result_set(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:795) from org.jruby.RubyArray.each(org/jruby/RubyArray.java:1735) from org.jruby.RubyArray$INVOKER$i$0$0$each.call(org/jruby/RubyArray$INVOKER$i$0$0$each.gen) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther33:each(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:794) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.process_result_set(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:794) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther0:process_result_set(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in fetch_rows(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.statement(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:646) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther29:statement(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:85) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther3:hold(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther41:synchronize(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.execute(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther9:execute(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.execute(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther2:execute(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.fetch_rows(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther3:fetch_rows(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:801) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.with_sql_each(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:801) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther1:with_sql_each(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:811) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.with_sql_first(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:811) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.placeholder_literalizer.invokeOther2:with_sql_first(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/placeholder_literalizer.rb:148) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.placeholder_literalizer.first(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/placeholder_literalizer.rb:148) from org.jruby.RubyClass.finvoke(org/jruby/RubyClass.java:523) from org.jruby.RubyBasicObject.send19(org/jruby/RubyBasicObject.java:1684) from org.jruby.RubyKernel.send19(org/jruby/RubyKernel.java:2018) from org.jruby.RubyKernel$INVOKER$s$send19.call(org/jruby/RubyKernel$INVOKER$s$send19.gen) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.model.base.invokeOther1:send(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/model/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/model/base.rb:878) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.model.base.block in def_finder_method(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/model/base.rb:878) from org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.model.base.invokeOther4:first_where(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/model/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/model/base.rb:110) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.model.base.[](D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/model/base.rb:110) from RUBY.create_system_user(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:4) from RUBY.create_hidden_system_user(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:21) from RUBY.create_search_user(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:302) from RUBY.(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:326) from RUBY.
(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:1) from org.jruby.Ruby.runInterpreter(org/jruby/Ruby.java:842) from org.jruby.Ruby.loadFile(org/jruby/Ruby.java:2903) from org.jruby.RubyKernel.requireCommon(org/jruby/RubyKernel.java:963) from org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) from org.jruby.RubyKernel$INVOKER$s$1$0$require19.call(org/jruby/RubyKernel$INVOKER$s$1$0$require19.gen) from uri_3a_classloader_3a_.jruby.kernel.kernel.invokeOther18:require(uri_3a_classloader_3a_/jruby/kernel/uri:classloader:/jruby/kernel/kernel.rb:13) from uri_3a_classloader_3a_.jruby.kernel.kernel.require_relative(uri:classloader:/jruby/kernel/kernel.rb:13) from RUBY.block in (root)(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1) from RUBY.block in ArchivesSpaceService(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:194) from RUBY.block in open(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111) from RUBY.transaction(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75) from RUBY.block in _transaction(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther3:hold(D_3a_/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database/D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) from D_3a_.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) from RUBY.transaction(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108) from RUBY.transaction(D:/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97) from RUBY.block in transaction(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74) from org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:305) from org.jruby.RubyFixnum$INVOKER$i$0$0$times.call(org/jruby/RubyFixnum$INVOKER$i$0$0$times.gen) from RUBY.open(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110) from org.jruby.RubyClass.finvoke(org/jruby/RubyClass.java:523) from org.jruby.RubyBasicObject.send19(org/jruby/RubyBasicObject.java:1684) from org.jruby.RubyKernel.send19(org/jruby/RubyKernel.java:2018) from org.jruby.RubyKernel$INVOKER$s$send19.call(org/jruby/RubyKernel$INVOKER$s$send19.gen) from RUBY.block in open(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107) from org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) from RUBY.block in open(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432) from RUBY.ArchivesSpaceService(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:193) from RUBY.(D:/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411) from RUBY.
(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78) from org.jruby.Ruby.runInterpreter(org/jruby/Ruby.java:842) from org.jruby.Ruby.loadFile(org/jruby/Ruby.java:2903) from org.jruby.RubyKernel.requireCommon(org/jruby/RubyKernel.java:963) from org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) from org.jruby.RubyKernel$INVOKER$s$1$0$require19.call(org/jruby/RubyKernel$INVOKER$s$1$0$require19.gen) from RUBY.(root)(D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38) from RUBY.block in (root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) from org.jruby.RubyBasicObject.yieldUnder(org/jruby/RubyBasicObject.java:1791) from org.jruby.RubyBasicObject.specificEval(org/jruby/RubyBasicObject.java:1810) from org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1691) from org.jruby.RubyBasicObject$INVOKER$i$instance_eval19.call(org/jruby/RubyBasicObject$INVOKER$i$instance_eval19.gen) from RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) from org.jruby.RubyClass.newInstance(org/jruby/RubyClass.java:1023) from org.jruby.RubyClass$INVOKER$i$newInstance.call(org/jruby/RubyClass$INVOKER$i$newInstance.gen) from RUBY.
(D:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4) from org.jruby.Ruby.runInterpreter(org/jruby/Ruby.java:847) from org.jruby.Ruby.runInterpreter(org/jruby/Ruby.java:851) from org.jruby.Ruby.executeScript(org/jruby/Ruby.java:508) from org.jruby.rack.DefaultRackApplicationFactory.createRackServletWrapper(org/jruby/rack/DefaultRackApplicationFactory.java:239) from org.jruby.rack.DefaultRackApplicationFactory.createApplicationObject(org/jruby/rack/DefaultRackApplicationFactory.java:168) from org.jruby.rack.DefaultRackApplicationFactory$1.create(org/jruby/rack/DefaultRackApplicationFactory.java:101) from org.jruby.rack.DefaultRackApplicationFactory$RackApplicationImpl.init(org/jruby/rack/DefaultRackApplicationFactory.java:445) from org.jruby.rack.DefaultRackApplicationFactory.getApplication(org/jruby/rack/DefaultRackApplicationFactory.java:114) from org.jruby.rack.SharedRackApplicationFactory.doInit(org/jruby/rack/SharedRackApplicationFactory.java:34) from org.jruby.rack.RackApplicationFactoryDecorator.init(org/jruby/rack/RackApplicationFactoryDecorator.java:100) from org.jruby.rack.RackServletContextListener.contextInitialized(org/jruby/rack/RackServletContextListener.java:50) from org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(org/eclipse/jetty/server/handler/ContextHandler.java:766) from org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(org/eclipse/jetty/servlet/ServletContextHandler.java:406) from org.eclipse.jetty.server.handler.ContextHandler.startContext(org/eclipse/jetty/server/handler/ContextHandler.java:758) from org.eclipse.jetty.servlet.ServletContextHandler.startContext(org/eclipse/jetty/servlet/ServletContextHandler.java:242) from org.eclipse.jetty.webapp.WebAppContext.startContext(org/eclipse/jetty/webapp/WebAppContext.java:1233) from org.eclipse.jetty.server.handler.ContextHandler.doStart(org/eclipse/jetty/server/handler/ContextHandler.java:701) from org.eclipse.jetty.webapp.WebAppContext.doStart(org/eclipse/jetty/webapp/WebAppContext.java:475) from org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59) from org.eclipse.jetty.server.handler.HandlerCollection.doStart(org/eclipse/jetty/server/handler/HandlerCollection.java:224) from org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(org/eclipse/jetty/server/handler/ContextHandlerCollection.java:167) from org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59) from org.eclipse.jetty.server.handler.HandlerWrapper.doStart(org/eclipse/jetty/server/handler/HandlerWrapper.java:90) from org.eclipse.jetty.server.Server.doStart(org/eclipse/jetty/server/Server.java:272) from org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59) from java.lang.reflect.Method.invoke(java/lang/reflect/Method) from org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438) from org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302) from launcher.launcher.invokeOther155:start(launcher/launcher.rb:92) from launcher.launcher.start_server(launcher/launcher.rb:92) from launcher.launcher.invokeOther290:start_server(launcher/launcher.rb:157) from launcher.launcher.main(launcher/launcher.rb:157) from launcher.launcher.invokeOther503:main(launcher/launcher.rb:261) from launcher.launcher.
(launcher/launcher.rb:261) from java.lang.invoke.MethodHandle.invokeWithArguments(java/lang/invoke/MethodHandle) from org.jruby.Ruby.runScript(org/jruby/Ruby.java:830) from org.jruby.Ruby.runNormally(org/jruby/Ruby.java:749) from org.jruby.Ruby.runNormally(org/jruby/Ruby.java:767) from org.jruby.Ruby.runFromMain(org/jruby/Ruby.java:580) from org.jruby.Main.doRunFromMain(org/jruby/Main.java:417) from org.jruby.Main.internalRun(org/jruby/Main.java:305) from org.jruby.Main.run(org/jruby/Main.java:232) from org.jruby.Main.main(org/jruby/Main.java:204) You're seeing this error because you use JRuby::Rack::ErrorApp::ShowStatus. No idea how to troubleshoot - any advice appreciated. Thank you Gary Gary Rodman (he/him) Director of Enterprise Applications Ripon College 300 W. Seward St. Ripon, WI 54971 (direct) 920-748-8343 RodmanG at ripon.edu [image.png] Visit us at ripon.edu This e?mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing, or other use of this email by persons or entities other than the addressee is prohibited. If you have received this email in error, please contact the sender immediately and delete the material from your computer. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 17747 bytes Desc: image.png URL: From mkottman at ku.edu Thu Nov 5 16:08:34 2020 From: mkottman at ku.edu (Kottman, Miloche) Date: Thu, 5 Nov 2020 21:08:34 +0000 Subject: [Archivesspace_Users_Group] Help Please - System Setup Before Data Import In-Reply-To: References: Message-ID: VivianLea, The only thing you have to set up in ArchivesSpace is a Repository Record. Depending on who is doing the importing, you will need to check the permissions on the User Record. If the system administrator is doing the importing then s/he will have the appropriate permissions for importing by default. For anyone else, make sure the user has permission to initiate import jobs and create and run a background job. There may be other permissions the user will need, I recommend testing. The Repository Preferences are primarily for setting up how you want to browse/search records once you have some in ArchivesSpace. These are easily adjustable and don't need to be set up first (or at all if you prefer the default settings) I'm not sure what you are referring to as location codes. If you are talking about the Organization/Agency Code (i.e. the 040 code in an OCLC MARC record), this is set up in the Repository Record. You do not need to arrange notes in any particular order when importing. If you are using one of the CSV templates to import your data, you need to make sure you leave the columns in the order that they are in on the template. If you are importing via EAD or MARCXML, the order of notes doesn't matter. You can set up a default note order in your repository preferences which will rearrange the notes if you click on the button within a resource record. Again, this is just a staff interface display preference. Note order in record exports or the public user interface are prescribed by style-sheets that do not depend on this setting. You only need to set up container and/or location profiles (e.g. the size of boxes and/or shelves) if you plan to use them. You can set these up at any time so you can import data now and if you decide at a later date to use the location functionality in ArchivesSpace, for example, you can set it up and link records at that time. Depending on how "clean" your imported data is, you may end up creating duplicate(ish) values in the controlled vocabulary lists, e.g. Box and box. You'll want to review your controlled vocabulary values and merge items after a big import project. --Miloche ****************************** Miloche Kottman Head of Cataloging & Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Solek, VivianLea Sent: Monday, November 2, 2020 12:01 PM To: ASpace Users Group (archivesspace_users_group at lyralists.lyrasis.org) ; ASpace - Small Archives List (archivesspace_small_archives_users_group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] Help Please - System Setup Before Data Import Good afternoon, I am ready to start importing data into ASpace, but I know there are things I need to do to set up my ASpace instance before I hit "import." I know I need to 1. Set My Repository Preferences (including controlled vocabulary lists) 2. Import location codes 3. Arrange notes per DACS order 4. Create top container profiles. Are there things you wish someone had told you before import? Other things I should set up before importing? I'm working through the video tutorials in the Help Center, but I don't see a video titled "Setting Up ASpace Prior to Import" that would answer my questions. Thank you all VERY much for any and all suggestions you may have! All the best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrien_hilton at harvard.edu Mon Nov 9 14:23:42 2020 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Mon, 9 Nov 2020 19:23:42 +0000 Subject: [Archivesspace_Users_Group] Developing custom reports Message-ID: Dear Colleagues, We are considering creating three reports that are essentially data dumps of various record types in a repository, e.g. all resource record level data; all accession record level data; and all archival object level data associated with a single resource record. You can see our use cases and specifications here: Resource record level data: https://docs.google.com/document/d/1ndDKXuE27rKdfOycPjCODq6UVOKGlqY4ns3x_S4aFcM/edit?usp=sharing Accession record level data: https://docs.google.com/document/d/1XxddO8KDJdY97q6g9IzLffbnxjP8ei1U9BpErKP3NZA/edit?usp=sharing Archival object data: https://docs.google.com/document/d/1D9H31AoPtqmShf14EnrPoNgTimqzOTQa2GtcTcJBn1M/edit?usp=sharing The out-of-the-box reports don't contain all the data we are looking for in terms of data analysis, editing, and/or reporting purposes. We know there are some challenging areas to accommodate with linked tables and fields that are repeatable (e.g. extent) but are hopeful we can manage those. Given our particular situation reports are more desirable than say read only access to the database, which I know many people would use to get this data. First question: has anyone already written reports similar to these three? Second question: is there any interest in collaborating to develop these? Thanks in advance, Adrien -------------- next part -------------- An HTML attachment was scrubbed... URL: From k-miller3 at northwestern.edu Mon Nov 9 17:41:20 2020 From: k-miller3 at northwestern.edu (Karen Miller) Date: Mon, 9 Nov 2020 22:41:20 +0000 Subject: [Archivesspace_Users_Group] Developing custom reports In-Reply-To: References: Message-ID: Hello Adrien, I've got several reports that bring together multiple tables and aggregate repeatable fields (such as Extent) using SQL. My SQL is not very pretty, but it might be helpful for you. Below is the SQL I use to generate a list of Accession records with aggregated Extents and Agents and another that looks at whether any Archival Objects are unpublished (an archivist wanted to know whether it was OK to click the "Publish All" button for any particular Resource). I also have a couple of shelf lists that might be useful (they pull in Instance information), as well. SELECT T0.id AS 'ID', T1.repo_code AS 'Repository', T0.title AS 'Title', REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(T0.identifier,'","','-'),'[',''),']',''),'null',''),'"',''),',','') AS 'Identifier', T0.accession_date AS 'Accession Date', GROUP_CONCAT(DISTINCT CONCAT(T2.number, ' ', T3.value) ORDER BY CONCAT(T2.number, ' ', T3.value) DESC SEPARATOR ', ') AS 'Extent', GROUP_CONCAT(DISTINCT T2.container_summary ORDER BY T2.container_summary DESC SEPARATOR '; ') AS 'Container Summary', GROUP_CONCAT(DISTINCT T2.dimensions ORDER BY T2.dimensions DESC SEPARATOR '; ') AS 'Dimensions', GROUP_CONCAT(DISTINCT T5.sort_name ORDER BY T5.sort_name DESC SEPARATOR '; ') AS 'Person', GROUP_CONCAT(DISTINCT T7.sort_name ORDER BY T7.sort_name DESC SEPARATOR '; ') AS 'Corporate Body', GROUP_CONCAT(DISTINCT T8.sort_name ORDER BY T8.sort_name DESC SEPARATOR ', ') AS 'Family', GROUP_CONCAT(T6.value SEPARATOR ', ') AS 'Agent Role', T0.suppressed AS 'accessionSuppressed', T0.publish AS 'Published?', T0.created_by AS 'Created by', T0.last_modified_by AS 'Modified by', CONVERT_TZ(T0.create_time, '+00:00', '-5:00') AS 'Creation time', CONVERT_TZ(T0.system_mtime, '+00:00', '-5:00') AS 'Modification time' FROM archivesspace.accession T0 LEFT JOIN archivesspace. linked_agents_rlshp T4 ON T4.accession_id = T0.id LEFT JOIN archivesspace.name_person T5 ON T4.agent_person_id=T5.agent_person_id AND T5.authorized = '1' LEFT JOIN archivesspace.enumeration_value T6 ON T4.role_id=T6.id LEFT JOIN archivesspace.name_corporate_entity T7 ON T4.agent_corporate_entity_id=T7.agent_corporate_entity_id AND T7.authorized = '1' LEFT JOIN archivesspace.name_family T8 ON T4.agent_family_id=T8.agent_family_id AND T8.authorized='1' LEFT JOIN archivesspace.repository T1 ON T0.repo_id=T1.id LEFT JOIN archivesspace.extent T2 ON T0.id=T2.accession_id LEFT JOIN enumeration_value T3 ON T2.extent_type_id=T3.id GROUP BY T0.ID ORDER BY T0.create_time DESC This SQL prompts for a Resource ID (WHERE T8.root_record_id=?) and lists all of the attached Archival Objects, sorted by their Publish value. It's not what you want, but it illustrates connecting a Resource to Archival Objects and Top Container information. SELECT CONCAT(T9.value, " ", T6.indicator) AS `Container`, T8.component_id AS `Level`, T8.display_string AS `Component Title`, T8.publish AS `Publish?` FROM archivesspace.archival_object T8 LEFT OUTER JOIN archivesspace.instance T1 ON T1.archival_object_id=T8.id LEFT JOIN archivesspace.sub_container T2 ON T1.id = T2.instance_id LEFT JOIN archivesspace.top_container_link_rlshp T3 ON T2.id = T3.sub_container_id LEFT OUTER JOIN archivesspace.top_container T6 ON T3.top_container_id = T6.id LEFT JOIN archivesspace.top_container_housed_at_rlshp T4 ON T4.top_container_id = T6.id LEFT JOIN archivesspace.location T5 ON T4.location_id = T5.id LEFT JOIN archivesspace.enumeration_value T9 ON T6.type_id=T9.id WHERE T8.root_record_id=? ORDER by T8.publish, T9.value, T8.component_id ASC Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Hilton, Adrien Sent: Monday, November 09, 2020 1:24 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Developing custom reports Dear Colleagues, We are considering creating three reports that are essentially data dumps of various record types in a repository, e.g. all resource record level data; all accession record level data; and all archival object level data associated with a single resource record. You can see our use cases and specifications here: Resource record level data: https://docs.google.com/document/d/1ndDKXuE27rKdfOycPjCODq6UVOKGlqY4ns3x_S4aFcM/edit?usp=sharing Accession record level data: https://docs.google.com/document/d/1XxddO8KDJdY97q6g9IzLffbnxjP8ei1U9BpErKP3NZA/edit?usp=sharing Archival object data: https://docs.google.com/document/d/1D9H31AoPtqmShf14EnrPoNgTimqzOTQa2GtcTcJBn1M/edit?usp=sharing The out-of-the-box reports don't contain all the data we are looking for in terms of data analysis, editing, and/or reporting purposes. We know there are some challenging areas to accommodate with linked tables and fields that are repeatable (e.g. extent) but are hopeful we can manage those. Given our particular situation reports are more desirable than say read only access to the database, which I know many people would use to get this data. First question: has anyone already written reports similar to these three? Second question: is there any interest in collaborating to develop these? Thanks in advance, Adrien -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Tue Nov 10 11:14:10 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 10 Nov 2020 16:14:10 +0000 Subject: [Archivesspace_Users_Group] =?utf-8?q?Reminder=3A_ArchivesSpace_O?= =?utf-8?q?pen_Community_Call_=E2=80=93_November_11_at_2pm_ET_=2811am_PT?= =?utf-8?q?=29?= Message-ID: <3670139B-0248-4541-A327-1A61E8826525@lyrasis.org> Dear ArchivesSpace Members, Please join us for our next community Zoom call tomorrow, November 11, 2020 at 2-3pm ET (11-noon PT). This is an opportunity to hear updates from each other and encourage group discussion. This is a space to surface news, ideas, and challenges. This might be an especially good chance to talk about non-technical questions or ideas that you weren?t quite sure about posting on the Users Group listserv but really would like help with from us or your peers. The current agenda for this call is at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1796440074/2020-11-11+Meeting+notes. Please register in advance at: https://lyrasis.zoom.us/meeting/register/tJYsdOGrrTwrEtSEV7bbUTXlp1KbAOHkdnaO After registering, you will receive a confirmation email containing information about how to join the call. If you have a question or topic you'd like to have addressed in the call, you can submit it when you register or email Jessica Crouch at jessica.crouch at lyrasis.org by November 10 at 5pm ET. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 8549 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Wed Nov 11 15:47:28 2020 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 11 Nov 2020 20:47:28 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v2.8.1 now available Message-ID: ArchivesSpace is announcing the availability of v2.8.1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.8.1. This release includes improvements to the spreadsheet importer, additional settable record type preferences, some bug fixes and small feature improvements, and a number of infrastructure upgrades. Included among these are some performance, indexer, and small backend and staff interface improvements courtesy of work Hudson Molonglo did for ArchivesSpace member institution Queensland State Archives as part of a larger project. For spreadsheet importer fans: Some changes have been made to the spreadsheet importer in this release to extend its functionality and improve its performance, especially with large spreadsheets. Of particular note: there is now a validation option so that a user can do a test run with a file, providing the opportunity to clean up any errors outside ArchivesSpace before doing the actual import; the importer now accepts either Excel spreadsheets or CSV files that use the templates at https://github.com/archivesspace/archivesspace/tree/master/templates; and, while it is accessed from a resource record or resource component as before, the import now runs as a background job so that it can more easily handle large files and to make the log file downloadable and saved within ArchivesSpace. Also, a number of bugs that were introduced with the conversion of the spreadsheet from a plugin to ArchivesSpace have been fixed for this release. Thanks very much to community members Andrew Morrison, Blake Carver, Brian Harrington, Dee Dee Crema, Douglas Simon, Greg Wiedeman, James Bullen, Jeremy Markowitz, Joshua Shaw, Mark Triggs, Noah Geraci, Payten Giles, and Steve Majewski for their code contributions to this release. Program team members Lora Woodford and Mark Cooper wrote and reviewed code and supervised the work of Bobbi Fox and Brian Zelip, who worked with us as contractors on this release. This release would, of course, not have been possible without the hard work of so many of our community groups, including our Development Prioritization, Testing, Technical Documentation, and User Documentation sub-teams, and Core Committers Group. Information on upgrading to a new version of ArchivesSpace is available at https://archivesspace.github.io/tech-docs/administration/upgrading.html. If you have any difficulties, please let us know. Thanks to all for their help and support. We are expecting to put out one more release in 2020, which will be almost exclusively focused on changes to the Agents module. You will hear more from us about that in the weeks to come. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From Jessica.Crouch at lyrasis.org Thu Nov 12 08:48:45 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 12 Nov 2020 13:48:45 +0000 Subject: [Archivesspace_Users_Group] Volunteer for the next ArchivesSpace online forum planning team Message-ID: <66AF224E-F007-4D4C-8C3C-7A2B098B7F01@lyrasis.org> Dear ArchivesSpace Members, We are currently looking for volunteers for the working group for our third annual ArchivesSpace Online Forum! Planned for March 2021, this event will build on the success of the 2020 Online Forum, which had over 500 registrants, participating from 15 different countries. We would love this event to highlight the work institutions near and far are doing to integrate ArchivesSpace into their systems and workflows, especially as they?ve adapted to working from home throughout the past year. We expect to offer a variety of activities aimed at building community connections and contacts among our users. All ideas are welcome! All community members are welcome to volunteer for this working group. We especially encourage our Small and Very Small members as well as non-U.S. members to join in envisioning the next iteration of this event. We will schedule meetings and the forum itself in ways that allow for participation across time zones. If you would like to volunteer, please respond by November 30, 2020. And if you have any questions, contact Jessica at jessica.crouch at lyrasis.org. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 8548 bytes Desc: image001.jpg URL: From Jessica.Crouch at lyrasis.org Thu Nov 12 14:02:12 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 12 Nov 2020 19:02:12 +0000 Subject: [Archivesspace_Users_Group] Community feedback requested for the ArchivesSpace Code of Conduct Message-ID: <26A4608A-A49C-481D-83F5-66F789B12315@lyrasis.org> [Posted on behalf of the ArchivesSpace Member Engagement sub-team of the User Advisory Council] Dear ArchivesSpace Users, The ArchivesSpace Member Engagement sub-team of the User Advisory Council has drafted a new ArchivesSpace Code of Conduct and seeks input from all ArchivesSpace users. This Code of Conduct will apply to all participants in ArchivesSpace-supported activities, including events, meetings, listservs and other communication channels, and our GitHub repositories. It will be implemented beginning in the 2021 calendar year. You can access the draft document and provide feedback at https://docs.google.com/forms/d/e/1FAIpQLSdQ5l8djzhvYeJVxZ4sbt_h2nL-O9h9DllRVLcVZh533v_JeA/viewform. Please submit any comments by Friday, December 11th, at noon ET via the feedback form. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29061 bytes Desc: image001.jpg URL: From bsutherland at mitre.org Thu Nov 19 13:48:28 2020 From: bsutherland at mitre.org (Bryan W Sutherland) Date: Thu, 19 Nov 2020 18:48:28 +0000 Subject: [Archivesspace_Users_Group] Appraisal information database location Message-ID: Hello, I'm trying to locate where in the ASpace database the information within the item-level appraisal tag is located. There is date information within this tag that I would like to extract. My colleagues in technical support and I have been unable to find it and there doesn't seems to be a report with that information either. Any help would be greatly appreciated, thanks! Bryan Sutherland Collections Management Archivist The MITRE Corporation Bedford, MA 781-271-8941 -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.harrington at lyrasis.org Thu Nov 19 14:46:10 2020 From: brian.harrington at lyrasis.org (Brian Harrington) Date: Thu, 19 Nov 2020 19:46:10 +0000 Subject: [Archivesspace_Users_Group] Appraisal information database location Message-ID: <4AB59DB2-CAFE-48F9-85B5-C7AD7250F6B1@lyrasis.org> Hi Bryan, Appraisal is just a note, so it should be in the ?note? table. The JSON for each note is stored in the notes field. You?ll need to use the MySQL JSON functions to extract the information you want https://dev.mysql.com/doc/refman/5.7/en/json-search-functions.html . I hope this helps. Brian -- Brian Harrington (he/him) Data Migration Specialist LYRASIS brian.harrington at lyrasis.org From: on behalf of Bryan W Sutherland Reply-To: Archivesspace Users Group Date: Thursday, November 19, 2020 at 1:50 PM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Appraisal information database location Hello, I?m trying to locate where in the ASpace database the information within the item-level appraisal tag is located. There is date information within this tag that I would like to extract. My colleagues in technical support and I have been unable to find it and there doesn?t seems to be a report with that information either. Any help would be greatly appreciated, thanks! Bryan Sutherland Collections Management Archivist The MITRE Corporation Bedford, MA 781-271-8941 -------------- next part -------------- An HTML attachment was scrubbed... URL: From zachary.pelli at shu.edu Thu Nov 19 16:11:15 2020 From: zachary.pelli at shu.edu (Zachary L Pelli) Date: Thu, 19 Nov 2020 21:11:15 +0000 Subject: [Archivesspace_Users_Group] Strange indexing issue v2.81 Message-ID: Hey all, After installing v2.81 we're having a strange issue, seemingly related to the index. Some collections cannot be found via search as they were before. I deleted the index in order to force a reindex and the collections were then searchable for a time. But coming back later, the issue had manifested once again and those collections would not appear in searches. Is this something that anyone has experienced before? I can provide logs and examples if you need more information. Regards, Zach Pelli Seton Hall University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From JShedd at library.msstate.edu Thu Nov 19 16:20:10 2020 From: JShedd at library.msstate.edu (Shedd, Julie) Date: Thu, 19 Nov 2020 21:20:10 +0000 Subject: [Archivesspace_Users_Group] Strange indexing issue v2.81 In-Reply-To: References: Message-ID: We are experiencing this issue now, but with accession and resource records. I think it may have something to do ? at least in our case ? with having certain metadata fields empty. When I filled those fields, the items stayed. However, transferring between repositories, they vanished again. So I will be watching the replies to your question closely in hopes that someone can help. ? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Julie D. Shedd she / her / hers Coordinator of Digital Initiatives and Web Services, Mississippi State University Libraries (662) 325-0300 | jshedd at library.msstate.edu https://orcid.org/0000-0002-7508-9033 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Zachary L Pelli Sent: Thursday, November 19, 2020 3:11 PM To: ArchivesSpace List (archivesspace_users_group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] Strange indexing issue v2.81 Hey all, After installing v2.81 we're having a strange issue, seemingly related to the index. Some collections cannot be found via search as they were before. I deleted the index in order to force a reindex and the collections were then searchable for a time. But coming back later, the issue had manifested once again and those collections would not appear in searches. Is this something that anyone has experienced before? I can provide logs and examples if you need more information. Regards, Zach Pelli Seton Hall University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From don.mennerich at nyu.edu Thu Nov 19 16:33:49 2020 From: don.mennerich at nyu.edu (Donald Mennerich) Date: Thu, 19 Nov 2020 16:33:49 -0500 Subject: [Archivesspace_Users_Group] Strange indexing issue v2.81 In-Reply-To: References: Message-ID: Zach, Is your index roughly the same size as it was before you upgraded? How long has it been running since you restarted Aspace after upgrading? I might advise anyone rebuilding the index that it's advantageous to make a backup of the index before deleting your data (I keep a tar file that I can check for the count of files and bytes in the index) in case there is weird behavior after an upgrade. Also, for metrics -- our index took about 11 hours to reindex on infrastructure that I would describe as "beefy". Don On Thu, Nov 19, 2020 at 4:20 PM Shedd, Julie wrote: > We are experiencing this issue now, but with accession and resource > records. I think it may have something to do ? at least in our case ? with > having certain metadata fields empty. When I filled those fields, the items > stayed. However, transferring between repositories, they vanished again. So > I will be watching the replies to your question closely in hopes that > someone can help. ? > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > *Julie D. Shedd *she / her / hers > > *Coordinator of Digital Initiatives and Web Services, Mississippi State > University Libraries > * > > (662) 325-0300 | jshedd at library.msstate.edu > > https://orcid.org/0000-0002-7508-9033 > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Zachary > L Pelli > *Sent:* Thursday, November 19, 2020 3:11 PM > *To:* ArchivesSpace List (archivesspace_users_group at lyralists.lyrasis.org) > > *Subject:* [Archivesspace_Users_Group] Strange indexing issue v2.81 > > > > Hey all, > > > > After installing v2.81 we're having a strange issue, seemingly related to > the index. Some collections cannot be found via search as they were before. > I deleted the index in order to force a reindex and the collections were > then searchable for a time. But coming back later, the issue had manifested > once again and those collections would not appear in searches. Is this > something that anyone has experienced before? I can provide logs and > examples if you need more information. > > > > Regards, > > > > Zach Pelli > > Seton Hall University Libraries > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=_DsNVvE0MidyDzdUOYchWsIErjGtgLba7OOoi6MzJhM&m=kIK-f6IZmFjun8xkPHXRnlgaXiUBHKppRUyW-EI2orQ&s=GNErwd0b2PHf5J6z2YoYe1ldJ_MIdjw7soA789tr4iY&e= > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.harrington at lyrasis.org Thu Nov 19 18:33:13 2020 From: brian.harrington at lyrasis.org (Brian Harrington) Date: Thu, 19 Nov 2020 23:33:13 +0000 Subject: [Archivesspace_Users_Group] Strange indexing issue v2.81 Message-ID: Hi Zach, Try truncating the deleted_records table and reindexing. That usually seems to solve issues with resources disappearing from the search. Brian -- Brian Harrington (he/him) Data Migration Specialist LYRASIS brian.harrington at lyrasis.org From: on behalf of Zachary L Pelli Reply-To: Archivesspace Users Group Date: Thursday, November 19, 2020 at 4:11 PM To: "ArchivesSpace List (archivesspace_users_group at lyralists.lyrasis.org)" Subject: [Archivesspace_Users_Group] Strange indexing issue v2.81 Hey all, After installing v2.81 we're having a strange issue, seemingly related to the index. Some collections cannot be found via search as they were before. I deleted the index in order to force a reindex and the collections were then searchable for a time. But coming back later, the issue had manifested once again and those collections would not appear in searches. Is this something that anyone has experienced before? I can provide logs and examples if you need more information. Regards, Zach Pelli Seton Hall University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From zachary.pelli at shu.edu Fri Nov 20 15:19:01 2020 From: zachary.pelli at shu.edu (Zachary L Pelli) Date: Fri, 20 Nov 2020 20:19:01 +0000 Subject: [Archivesspace_Users_Group] Strange indexing issue v2.81 In-Reply-To: References: Message-ID: Thanks Brian, but the same thing happened after truncating the table and reindexing. It worked at first but did not when I came back a couple hours later. Regards, Zach Pelli ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Brian Harrington Sent: Thursday, November 19, 2020 6:33 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Strange indexing issue v2.81 Hi Zach, Try truncating the deleted_records table and reindexing. That usually seems to solve issues with resources disappearing from the search. Brian -- Brian Harrington (he/him) Data Migration Specialist LYRASIS brian.harrington at lyrasis.org From: on behalf of Zachary L Pelli Reply-To: Archivesspace Users Group Date: Thursday, November 19, 2020 at 4:11 PM To: "ArchivesSpace List (archivesspace_users_group at lyralists.lyrasis.org)" Subject: [Archivesspace_Users_Group] Strange indexing issue v2.81 Hey all, After installing v2.81 we're having a strange issue, seemingly related to the index. Some collections cannot be found via search as they were before. I deleted the index in order to force a reindex and the collections were then searchable for a time. But coming back later, the issue had manifested once again and those collections would not appear in searches. Is this something that anyone has experienced before? I can provide logs and examples if you need more information. Regards, Zach Pelli Seton Hall University Libraries ** WARNING: This email originated from outside of Seton Hall University. Do not click links or open attachments unless you recognize the sender and know the content is safe. ** -------------- next part -------------- An HTML attachment was scrubbed... URL: From zachary.pelli at shu.edu Fri Nov 20 15:31:00 2020 From: zachary.pelli at shu.edu (Zachary L Pelli) Date: Fri, 20 Nov 2020 20:31:00 +0000 Subject: [Archivesspace_Users_Group] Strange indexing issue v2.81 In-Reply-To: References: , Message-ID: Donald, The /data directory in 2.8.0 totaled 713M, and the new one is 809M, different but not eye-raising to my untrained eye. I have it set to reset each night to reduce any memory leakage, which has been a problem before. Our infrastructure is less than beefy, as you can tell ?. Regards, Zach Pelli ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Donald Mennerich Sent: Thursday, November 19, 2020 4:33 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Strange indexing issue v2.81 Zach, Is your index roughly the same size as it was before you upgraded? How long has it been running since you restarted Aspace after upgrading? I might advise anyone rebuilding the index that it's advantageous to make a backup of the index before deleting your data (I keep a tar file that I can check for the count of files and bytes in the index) in case there is weird behavior after an upgrade. Also, for metrics -- our index took about 11 hours to reindex on infrastructure that I would describe as "beefy". Don On Thu, Nov 19, 2020 at 4:20 PM Shedd, Julie > wrote: We are experiencing this issue now, but with accession and resource records. I think it may have something to do ? at least in our case ? with having certain metadata fields empty. When I filled those fields, the items stayed. However, transferring between repositories, they vanished again. So I will be watching the replies to your question closely in hopes that someone can help. ? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Julie D. Shedd she / her / hers Coordinator of Digital Initiatives and Web Services, Mississippi State University Libraries (662) 325-0300 | jshedd at library.msstate.edu https://orcid.org/0000-0002-7508-9033 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Zachary L Pelli Sent: Thursday, November 19, 2020 3:11 PM To: ArchivesSpace List (archivesspace_users_group at lyralists.lyrasis.org) > Subject: [Archivesspace_Users_Group] Strange indexing issue v2.81 Hey all, After installing v2.81 we're having a strange issue, seemingly related to the index. Some collections cannot be found via search as they were before. I deleted the index in order to force a reindex and the collections were then searchable for a time. But coming back later, the issue had manifested once again and those collections would not appear in searches. Is this something that anyone has experienced before? I can provide logs and examples if you need more information. Regards, Zach Pelli Seton Hall University Libraries _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=_DsNVvE0MidyDzdUOYchWsIErjGtgLba7OOoi6MzJhM&m=kIK-f6IZmFjun8xkPHXRnlgaXiUBHKppRUyW-EI2orQ&s=GNErwd0b2PHf5J6z2YoYe1ldJ_MIdjw7soA789tr4iY&e= ** WARNING: This email originated from outside of Seton Hall University. Do not click links or open attachments unless you recognize the sender and know the content is safe. ** -------------- next part -------------- An HTML attachment was scrubbed... URL: From dzuckerm at library.berkeley.edu Mon Nov 23 13:37:15 2020 From: dzuckerm at library.berkeley.edu (David M. ZUCKERMAN) Date: Mon, 23 Nov 2020 10:37:15 -0800 Subject: [Archivesspace_Users_Group] Disable PUI (public interface) Message-ID: Hi, We're upgrading Archivesspace and will not be using the public interface. I see quite a few config options for pui in config.rb but not sure how I'd disable it entirely. I've been searching through various documents but they all seem to deal with how to configure it. Was thinking there would be something similar to this AppConfig[:enable_pui] = false Is there a specific way the public interface should be disabled? Thanks, Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From zachary.pelli at shu.edu Mon Nov 23 14:03:04 2020 From: zachary.pelli at shu.edu (Zachary L Pelli) Date: Mon, 23 Nov 2020 19:03:04 +0000 Subject: [Archivesspace_Users_Group] Disable PUI (public interface) In-Reply-To: References: Message-ID: Hey Dave, Just off the top of my head: just firewall off port 8081 on your server, provided you have that level of control over the server. Regards, Zach Pelli From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of David M. ZUCKERMAN Sent: Monday, November 23, 2020 1:37 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Disable PUI (public interface) Hi, We're upgrading Archivesspace and will not be using the public interface. I see quite a few config options for pui in config.rb but not sure how I'd disable it entirely. I've been searching through various documents but they all seem to deal with how to configure it. Was thinking there would be something similar to this AppConfig[:enable_pui] = false Is there a specific way the public interface should be disabled? Thanks, Dave ** WARNING: This email originated from outside of Seton Hall University. Do not click links or open attachments unless you recognize the sender and know the content is safe. ** -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Mon Nov 23 14:35:15 2020 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Mon, 23 Nov 2020 19:35:15 +0000 Subject: [Archivesspace_Users_Group] Disable PUI (public interface) In-Reply-To: References: Message-ID: <1ebb93fd-242d-e76b-9415-a76c12c8266a@bodleian.ox.ac.uk> This is an AppConfig[:enable_public] setting which can be set to false in config.rb. Andrew. On 23/11/2020 18:37, David M. ZUCKERMAN wrote: > Hi, > > We're upgrading Archivesspace and will not be using the public > interface. I see quite a few config options for pui in config.rb but > not sure how I'd disable it entirely. I've been searching through > various documents but they all seem to deal with how to configure it. > > Was thinking?there would be something similar to this > AppConfig[:enable_pui] = false > > Is there a specific way the public interface should be disabled? > > Thanks, > Dave > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Mon Nov 23 15:10:54 2020 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 23 Nov 2020 20:10:54 +0000 Subject: [Archivesspace_Users_Group] Disable PUI (public interface) In-Reply-To: <1ebb93fd-242d-e76b-9415-a76c12c8266a@bodleian.ox.ac.uk> References: , <1ebb93fd-242d-e76b-9415-a76c12c8266a@bodleian.ox.ac.uk> Message-ID: David, In addition to what Zach and Andrew mentioned, I would also set "pui_indexer_enabled" to false in this case. Also, all the configuration defaults are here: https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb. I always have to look at that to remind myself ? Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Andrew Morrison Sent: Monday, November 23, 2020 2:35 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Disable PUI (public interface) This is an AppConfig[:enable_public] setting which can be set to false in config.rb. Andrew. On 23/11/2020 18:37, David M. ZUCKERMAN wrote: Hi, We're upgrading Archivesspace and will not be using the public interface. I see quite a few config options for pui in config.rb but not sure how I'd disable it entirely. I've been searching through various documents but they all seem to deal with how to configure it. Was thinking there would be something similar to this AppConfig[:enable_pui] = false Is there a specific way the public interface should be disabled? Thanks, Dave _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From scheirw at newschool.edu Wed Nov 25 14:12:28 2020 From: scheirw at newschool.edu (Wendy Scheir) Date: Wed, 25 Nov 2020 14:12:28 -0500 Subject: [Archivesspace_Users_Group] Top Container Searching Message-ID: Hi, We've started working with v2.8.1 and welcome the improvements to top container searching. We noticed that the Resource field does not limit searches to Resource *title*, but rather is a keyword search across resources. Are there plans to add the capability of limiting search results to resource title? This functionality would reduce a result list from potentially hundreds of records to a handful, which would be very useful to us, as it would, I'd imagine, to other ASpace members. Many thanks, Wendy ____________________________________ WENDY SCHEIR *DIRECTOR* 66 5TH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212.229.5942 x2888 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Mon Nov 30 13:22:49 2020 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 30 Nov 2020 18:22:49 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - November 2020 Message-ID: [cid:image005.jpg at 01D6C71B.E56BF3F0] ArchivesSpace Update - November 2020 Development ArchivesSpace is announcing the availability of v2.8.1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.8.1. This release includes improvements to the spreadsheet importer, additional settable record type preferences, some bug fixes and small feature improvements, and a number of infrastructure upgrades. Included among these are some performance, indexer, and small backend and staff interface improvements courtesy of work Hudson Molonglo did for ArchivesSpace member institution Queensland State Archives as part of a larger project. For spreadsheet importer fans: Some changes have been made to the spreadsheet importer in this release to extend its functionality and improve its performance, especially with large spreadsheets. Of particular note: there is now a validation option so that a user can do a test run with a file, providing the opportunity to clean up any errors outside ArchivesSpace before doing the actual import; the importer now accepts either Excel spreadsheets or CSV files that use the templates at https://github.com/archivesspace/archivesspace/tree/master/templates; and, while it is accessed from a resource record or resource component as before, the import now runs as a background job so that it can more easily handle large files and to make the log file downloadable and saved within ArchivesSpace. Also, a number of bugs that were introduced with the conversion of the spreadsheet from a plugin to ArchivesSpace have been fixed for this release. Thanks very much to community members Andrew Morrison, Blake Carver, Brian Harrington, Dee Dee Crema, Douglas Simon, Greg Wiedeman, James Bullen, Jeremy Markowitz, Joshua Shaw, Mark Triggs, Noah Geraci, Payten Giles, and Steve Majewski for their code contributions to this release. Program team members Lora Woodford and Mark Cooper wrote and reviewed code and supervised the work of Bobbi Fox and Brian Zelip, who worked with us as contractors on this release. This release would, of course, not have been possible without the hard work of so many of our community groups, including our Development Prioritization, Testing, Technical Documentation, and User Documentation sub-teams, and Core Committers Group. Information on upgrading to a new version of ArchivesSpace is available at https://archivesspace.github.io/tech-docs/administration/upgrading.html. If you have any difficulties, please let us know. We expect to put out one more release in 2020, which will be almost exclusively focused on changes to the Agents module. You will hear more from us about that in December. Position Announcement: ArchivesSpace Technical Lead We are still accepting applications to be the next Technical Lead for ArchivesSpace. The Technical Lead works with a wide-ranging group of community stakeholders and is responsible for the overall development of the software application and management of the community-based code contribution process. The Technical Lead works to engage a broad set of developers to participate in the project, providing technical guidance, support and leadership to maintain a robust developer community. This position is part of a geographically distributed team, and, as such, applications from candidates interested in telecommuting are very welcome. To learn more, or to submit your resume and cover letter, please visit https://lyrasis.isolvedhire.com/jobs/145014.html. If you know of someone who may be interested, or if you are interested yourself, please feel free to reach out to Christine Di Bella at christine.dibella at lyrasis.org with any questions. Volunteer for the Next Online Forum Planning Team We are currently looking for volunteers for the working group for our third annual ArchivesSpace Online Forum! Planned for March 2021, this event will build on the success of the 2020 Online Forum, which had over 500 registrants, participating from 15 different countries. We would love this event to highlight the work institutions near and far are doing to integrate ArchivesSpace into their systems and workflows, especially as they've adapted to working from home throughout the past year. We expect to offer a variety of activities aimed at building community connections and contacts among our users. All ideas are welcome! All community members are welcome to volunteer for this working group. We especially encourage those from our Small and Very Small member institutions as well as non-U.S. members to join in envisioning the next iteration of this event. We will schedule meetings and the forum itself in ways that allow for participation across time zones. If you would like to volunteer, please contact Jessica Crouch at jessica.crouch at lyrasis.org by December 15, 2020. We look forward to working together for another successful Online Forum. Community Feedback Requested on the ArchivesSpace Code of Conduct The ArchivesSpace Member Engagement sub-team of the User Advisory Council has drafted a new ArchivesSpace Code of Conduct and seeks input from all ArchivesSpace users. This Code of Conduct will apply to all participants in ArchivesSpace-supported activities, including events, meetings, listservs and other communication channels, and our GitHub repositories. It will be implemented beginning in the 2021 calendar year. You can access the draft document and provide feedback at https://docs.google.com/forms/d/e/1FAIpQLSdQ5l8djzhvYeJVxZ4sbt_h2nL-O9h9DllRVLcVZh533v_JeA/viewform. Please submit any comments by Friday, December 11th, at noon ET via the feedback form. Notes Available from November 11 Community Open Call Our most recent community Open Call took place on November 11. The notes are available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1796440074/2020-11-11+Meeting+notes. If you have a question or topic you'd like to have addressed in a future call, please email Jessica at jessica.crouch at lyrasis.org. Membership Update As of November 30, we have 413 General members, 21 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. ________________________________ ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA's Collection Management Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 19935 bytes Desc: image005.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.jpg Type: image/jpeg Size: 6608 bytes Desc: image006.jpg URL: