Re: [Archivesspace_Users_Group] language plugin implementation 2.7.1

2020-09-08 Thread Knox, Ashley M.
I'd like to clarify my earlier post. After migrating from 2.6.0 to 2.7.1, we 
saw the new 'language of description note' populated with a language, where it 
was not before the migration. We only had 'language of description' populated 
while in 2.6.0. So, my question is just that did anyone else experience this 
when they migrated. Initially, I thought it was purposeful and that one of the 
plugins would rectify it, but that was not the case. We now have 'language of 
description' and 'Script of description' populated correctly, thanks to the 
plugins. The new and unexpected/unwanted 'language of description note' 
remained the same after implementing the plugins.


--earlier post--
We implemented the first two of the three language plugins on a 2.7.1 dev 
instance and for the most part, we got what was expected. What was unexpected 
to us is that in the Finding Aid Data section, Language of description 
(English) became language of description/script of description (English/Latin) 
PLUS language of description note (English). The extra/new lang of desc. note 
feels a little redundant and we are at a loss as to why it appears? Did this 
happen for anyone else? Was this intentional?  Are we missing something obvious?

Ashley

Ashley Knox
Digital Initiatives Librarian
Randall Library
University of North Carolina Wilmington
kn...@uncw.edu
http://library.uncw.edu
http://digitalcollections.uncw.edu


From: Knox, Ashley M.
Sent: Tuesday, September 8, 2020 1:29 PM
To: Archivesspace Users Group 
Subject: language plugin implementation 2.7.1

We implemented the first two of the three language plugins on a 2.7.1 dev 
instance and for the most part, we got what was expected. What was unexpected 
to us is that in the Finding Aid Data section, Language of description 
(English) became language of description/script of description (English/Latin) 
PLUS language of description note (English). The extra/new lang of desc. note 
feels a little redundant and we are at a loss as to why it appears? Did this 
happen for anyone else? Was this intentional?  Are we missing something obvious?

Ashley

Ashley Knox
Digital Initiatives Librarian
Randall Library
University of North Carolina Wilmington
kn...@uncw.edu
http://library.uncw.edu
http://digitalcollections.uncw.edu

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


[Archivesspace_Users_Group] FW: US DataCite Community call for interest

2020-09-08 Thread Christine Di Bella
Forwarding on behalf of our colleague Sheila Rabun at LYRASIS. Please get in 
touch with her at sheila.ra...@lyrasis.org 
with questions.

Christine

From: Sheila Rabun 
Sent: Tuesday, September 8, 2020 11:45 AM
To: Christine Di Bella 
Subject: US DataCite Community call for interest

Hi Christine, the message below is a call for interest in a potential US 
DataCite Community administered by LYRASIS - if you can please forward to the 
ArchivesSpace community, that will be wonderful. Many thanks! -Sheila
---

To: ArchivesSpace community

Subject: US DataCite Community call for interest


Greetings all,

To bolster our existing programs, LYRASIS is considering establishing a 
national DataCite Community, which would 
allow non-profit organizations in the US to create DOIs* (digital object 
identifiers) for digital assets created and hosted locally for a reduced fee as 
part of DataCite's consortium member model.

We are checking in with you to gauge interest in such a program, which we would 
anticipate to begin in January 2021 with an anticipated annual per-institution 
fee of $1,600, plus a DOI fee depending on the number of DOIs created at each 
institution:

Annual DOI Fees:

  *   1-1,999 DOIs created = $.95 per DOI
  *   2,000-10,000 DOIs created = $1,900 flat rate
  *   Any organizations creating more than 10,000 DOIs per year would need to 
operate as a direct member with DataCite.

The more institutions participating, and the more DOIs created, the more 
everyone can potentially save due to DataCite's consortium fee caps. This 
program would provide a savings of approximately 40% per participating 
institution compared to what any single organization might pay for becoming a 
direct member with DataCite.

If your organization would be interested in joining our DataCite consortium, 
please complete this brief form by Sept. 
25 to let us know.

Many thanks, on behalf of the LYRASIS Content & Scholarly Communication team!

*DOIs are unique, persistent identifiers that can be created by institutions 
through a DOI registration service (such as DataCite) and assigned to digital 
works in order to make them easier to find on the web in a reliable manner over 
time. DOIs are commonly assigned to objects such as digital journal articles, 
white papers, OERs (open educational resources), slide decks, posters, or other 
works on the web. For example, the DOI for the document "Recommendations for 
Supporting ORCID in Repositories" is https://doi.org/10.23640/07243.274.


Sheila Rabun, MA, MLIS [cid:image001.gif@01D685BC.5D001280]  
https://orcid.org/-0002-1196-6279
ORCID US Community Specialist
Web: http://orcid-us.org
Twitter: https://twitter.com/USconsortium
Phone: 1-800-999-8558 x4809
Pronouns: she/her/hers

[cid:image004.jpg@01D685ED.3113E8A0]
[cid:image005.png@01D685ED.3113E8A0]

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


[Archivesspace_Users_Group] language plugin implementation 2.7.1

2020-09-08 Thread Knox, Ashley M.
We implemented the first two of the three language plugins on a 2.7.1 dev 
instance and for the most part, we got what was expected. What was unexpected 
to us is that in the Finding Aid Data section, Language of description 
(English) became language of description/script of description (English/Latin) 
PLUS language of description note (English). The extra/new lang of desc. note 
feels a little redundant and we are at a loss as to why it appears? Did this 
happen for anyone else? Was this intentional?  Are we missing something obvious?

Ashley

Ashley Knox
Digital Initiatives Librarian
Randall Library
University of North Carolina Wilmington
kn...@uncw.edu
http://library.uncw.edu
http://digitalcollections.uncw.edu

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


Re: [Archivesspace_Users_Group] (no subject)

2020-09-08 Thread Andrew Morrison
Those URLs are where you are sent to if you click on the request button 
in the public user interface if you do not have JavaScript enabled. It 
is probably a requirement for accessibility.



It doesn't work on this test system:


http://test.archivesspace.org/repositories/2/resources/77/request


But it may require some site-specific configuration. I don't know 
because we don't use that feature.



It is the action-attribute of a form in the HTML, so a bot could easily 
decide to crawl all those URLs.



Andrew.



On 08/09/2020 13:44, Blake Carver wrote:

Could be a bot. That error:

ActionController::RoutingError (No route matches [GET] 
"/repositories/2/archival_objects/8206/request"):


Is essentially just a 404. "ActionController::RoutingError No route 
matches" is an error  means "I went looking for 
"/repositories/2/archival_objects/8206/request" because something just 
asked for it, but there ain't anything there so that's a big Ol' 
RoutingError"


Maybe the AO with the ID 8206 got deleted at some point?

*From:* archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Joshua D. Shaw 

*Sent:* Tuesday, September 8, 2020 8:39 AM
*To:* Archivesspace Users Group 


*Subject:* Re: [Archivesspace_Users_Group] (no subject)
I've seen this as well. I *thought* it was a bot crawling the site for 
indexing, since that URL is the constructed URL for a request, but if 
others have other ideas, I'd be happy to hear it!


Joshua


*From:* archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Ludwig Possie 

*Sent:* Friday, September 4, 2020 7:52 PM
*To:* Archivesspace Users Group 


*Subject:* [Archivesspace_Users_Group] (no subject)
We're currently hosting a copy of Archivesspace 2.6.0.  Recently we 
noticed that Archivesspace is running with a very high cpu load.  I 
checked the log files and got the following message.  I'm not sure if 
this has anything to do with the CPU cycles, but the fatal messages 
have me concerned.  This entire message thread is repeating every few 
minutes.  I'm not sure how to interpret the error message and was 
hoping someone could shed some light on this.  Thx.



F, [2020-09-04T23:32:20.007856 #107] FATAL -- : 
[9a562f9c-6c97-4251-ba41-5587d87a1650]
F, [2020-09-04T23:32:20.008071 #107] FATAL -- : 
[9a562f9c-6c97-4251-ba41-5587d87a1650] ActionController::RoutingError 
(No route matches [GET] "/repositories/2/archival_objects/8206/request"):
F, [2020-09-04T23:32:20.008868 #107] FATAL -- : 
[9a562f9c-6c97-4251-ba41-5587d87a1650]
F, [2020-09-04T23:32:20.012732 #107] FATAL -- : 
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] railties (5.0.7.2) 
lib/rails/rack/logger.rb:36:in `call_app'
[9a562f9c-6c97-4251-ba41-5587d87a1650] railties (5.0.7.2) 
lib/rails/rack/logger.rb:24:in `block in call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] activesupport (5.0.7.2) 
lib/active_support/tagged_logging.rb:69:in `block in tagged'
[9a562f9c-6c97-4251-ba41-5587d87a1650] activesupport (5.0.7.2) 
lib/active_support/tagged_logging.rb:26:in `tagged'
[9a562f9c-6c97-4251-ba41-5587d87a1650] activesupport (5.0.7.2) 
lib/active_support/tagged_logging.rb:69:in `tagged'
[9a562f9c-6c97-4251-ba41-5587d87a1650] railties (5.0.7.2) 
lib/rails/rack/logger.rb:24:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/request_id.rb:24:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] rack (2.0.7) 
lib/rack/method_override.rb:22:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] rack (2.0.7) 
lib/rack/runtime.rb:22:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] activesupport (5.0.7.2) 
lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/executor.rb:12:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/static.rb:136:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] rack (2.0.7) 
lib/rack/sendfile.rb:111:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] railties (5.0.7.2) 
lib/rails/engine.rb:522:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] 
uri:classloader:/rack/handler/servlet.rb:22:in `call'


--
Ludwig Possié
Systems Admin
Stewart Library
Weber State University
801-626-8093

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

Re: [Archivesspace_Users_Group] (no subject)

2020-09-08 Thread Blake Carver
Could be a bot. That error:

ActionController::RoutingError (No route matches [GET] 
"/repositories/2/archival_objects/8206/request"):

Is essentially just a 404. "ActionController::RoutingError No route matches" is 
an error  means "I went looking for 
"/repositories/2/archival_objects/8206/request" because something just asked 
for it, but there ain't anything there so that's a big Ol' RoutingError"

Maybe the AO with the ID 8206 got deleted at some point?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Joshua 
D. Shaw 
Sent: Tuesday, September 8, 2020 8:39 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] (no subject)

I've seen this as well. I *thought* it was a bot crawling the site for 
indexing, since that URL is the constructed URL for a request, but if others 
have other ideas, I'd be happy to hear it!

Joshua


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Ludwig 
Possie 
Sent: Friday, September 4, 2020 7:52 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] (no subject)

We're currently hosting a copy of Archivesspace 2.6.0.  Recently we noticed 
that Archivesspace is running with a very high cpu load.  I checked the log 
files and got the following message.  I'm not sure if this has anything to do 
with the CPU cycles, but the fatal messages have me concerned.  This entire 
message thread is repeating every few minutes.  I'm not sure how to interpret 
the error message and was hoping someone could shed some light on this.  Thx.


F, [2020-09-04T23:32:20.007856 #107] FATAL -- : 
[9a562f9c-6c97-4251-ba41-5587d87a1650]
F, [2020-09-04T23:32:20.008071 #107] FATAL -- : 
[9a562f9c-6c97-4251-ba41-5587d87a1650] ActionController::RoutingError (No route 
matches [GET] "/repositories/2/archival_objects/8206/request"):
F, [2020-09-04T23:32:20.008868 #107] FATAL -- : 
[9a562f9c-6c97-4251-ba41-5587d87a1650]
F, [2020-09-04T23:32:20.012732 #107] FATAL -- : 
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] railties (5.0.7.2) 
lib/rails/rack/logger.rb:36:in `call_app'
[9a562f9c-6c97-4251-ba41-5587d87a1650] railties (5.0.7.2) 
lib/rails/rack/logger.rb:24:in `block in call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] activesupport (5.0.7.2) 
lib/active_support/tagged_logging.rb:69:in `block in tagged'
[9a562f9c-6c97-4251-ba41-5587d87a1650] activesupport (5.0.7.2) 
lib/active_support/tagged_logging.rb:26:in `tagged'
[9a562f9c-6c97-4251-ba41-5587d87a1650] activesupport (5.0.7.2) 
lib/active_support/tagged_logging.rb:69:in `tagged'
[9a562f9c-6c97-4251-ba41-5587d87a1650] railties (5.0.7.2) 
lib/rails/rack/logger.rb:24:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/request_id.rb:24:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] rack (2.0.7) 
lib/rack/method_override.rb:22:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] rack (2.0.7) lib/rack/runtime.rb:22:in 
`call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] activesupport (5.0.7.2) 
lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/executor.rb:12:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/static.rb:136:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] rack (2.0.7) lib/rack/sendfile.rb:111:in 
`call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] railties (5.0.7.2) 
lib/rails/engine.rb:522:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] 
uri:classloader:/rack/handler/servlet.rb:22:in `call'

--
Ludwig Possié
Systems Admin
Stewart Library
Weber State University
801-626-8093
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] (no subject)

2020-09-08 Thread Joshua D. Shaw
I've seen this as well. I *thought* it was a bot crawling the site for 
indexing, since that URL is the constructed URL for a request, but if others 
have other ideas, I'd be happy to hear it!

Joshua


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Ludwig 
Possie 
Sent: Friday, September 4, 2020 7:52 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] (no subject)

We're currently hosting a copy of Archivesspace 2.6.0.  Recently we noticed 
that Archivesspace is running with a very high cpu load.  I checked the log 
files and got the following message.  I'm not sure if this has anything to do 
with the CPU cycles, but the fatal messages have me concerned.  This entire 
message thread is repeating every few minutes.  I'm not sure how to interpret 
the error message and was hoping someone could shed some light on this.  Thx.


F, [2020-09-04T23:32:20.007856 #107] FATAL -- : 
[9a562f9c-6c97-4251-ba41-5587d87a1650]
F, [2020-09-04T23:32:20.008071 #107] FATAL -- : 
[9a562f9c-6c97-4251-ba41-5587d87a1650] ActionController::RoutingError (No route 
matches [GET] "/repositories/2/archival_objects/8206/request"):
F, [2020-09-04T23:32:20.008868 #107] FATAL -- : 
[9a562f9c-6c97-4251-ba41-5587d87a1650]
F, [2020-09-04T23:32:20.012732 #107] FATAL -- : 
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] railties (5.0.7.2) 
lib/rails/rack/logger.rb:36:in `call_app'
[9a562f9c-6c97-4251-ba41-5587d87a1650] railties (5.0.7.2) 
lib/rails/rack/logger.rb:24:in `block in call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] activesupport (5.0.7.2) 
lib/active_support/tagged_logging.rb:69:in `block in tagged'
[9a562f9c-6c97-4251-ba41-5587d87a1650] activesupport (5.0.7.2) 
lib/active_support/tagged_logging.rb:26:in `tagged'
[9a562f9c-6c97-4251-ba41-5587d87a1650] activesupport (5.0.7.2) 
lib/active_support/tagged_logging.rb:69:in `tagged'
[9a562f9c-6c97-4251-ba41-5587d87a1650] railties (5.0.7.2) 
lib/rails/rack/logger.rb:24:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/request_id.rb:24:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] rack (2.0.7) 
lib/rack/method_override.rb:22:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] rack (2.0.7) lib/rack/runtime.rb:22:in 
`call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] activesupport (5.0.7.2) 
lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/executor.rb:12:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] actionpack (5.0.7.2) 
lib/action_dispatch/middleware/static.rb:136:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] rack (2.0.7) lib/rack/sendfile.rb:111:in 
`call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] railties (5.0.7.2) 
lib/rails/engine.rb:522:in `call'
[9a562f9c-6c97-4251-ba41-5587d87a1650] 
uri:classloader:/rack/handler/servlet.rb:22:in `call'

--
Ludwig Possié
Systems Admin
Stewart Library
Weber State University
801-626-8093
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group