From brian.sheppard at wisc.edu  Thu May  2 15:30:07 2019
From: brian.sheppard at wisc.edu (Brian Sheppard)
Date: Thu, 2 May 2019 19:30:07 +0000
Subject: [Archivesspace_Users_Group] mysql db connection error
Message-ID: <5BD0E0E8-CDDF-452F-AEB0-CBE19B1AC121@wisc.edu>


I'm having a problem connecting to a localhost mysql backend and, despite having perused a number of related threads, can't get it to work. I'd appreciate any insight.

AS runs normally when I use the default backend (when AppConfig[:db_url] is commented out). When uncommented,
I get a db connection error, though I can connect to the db via the mysql command-line using the same credentials specified in config.rb. The user has all privileges on the archivesspace db. Also, I see nothing in my mysql_error.log beyond startup comments.

The connector is in lib:
archivesspace_2_5_1/lib/mysql-connector-java-8.0.16.jar

mysql:  Ver 8.0.13 for osx10.12 on x86_64 (Homebrew)
java: version "1.8.0_211"
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin16]
jdbc-mysql gem: jdbc-mysql (5.1.42)

Redacted config.rb line:
AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=[adminuser]&password=[foo]&useUnicode=true&characterEncoding=UTF-8&useSSL=false"

TRACE:
Database connection failed from
/archivesspace_2_5_1/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure' from
archivesspace_2_5_1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in `<class:ArchivesSpaceService>' from
rchivesspace_2_5_1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in `<main>' from
 org/jruby/RubyKernel.java:961:in `require' from
 uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from
 archivesspace_2_5_1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in `block in (root)' from
 org/jruby/RubyBasicObject.java:1687:in `instance_eval' from
 archivesspace_2_5_1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in `(root)' from
 uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55:in `<main>' from
 launcher/launcher.rb:92:in `start_server' from
 launcher/launcher.rb:157:in `main' from
 launcher/launcher.rb:261:in `<main>'


Thanks.
-Brian

?????????????????????????????
Brian Sheppard
UW Digital Collections Center
brian.sheppard at wisc.edu






From blake.carver at lyrasis.org  Thu May  2 15:41:40 2019
From: blake.carver at lyrasis.org (Blake Carver)
Date: Thu, 2 May 2019 19:41:40 +0000
Subject: [Archivesspace_Users_Group] mysql db connection error
In-Reply-To: <5BD0E0E8-CDDF-452F-AEB0-CBE19B1AC121@wisc.edu>
References: <5BD0E0E8-CDDF-452F-AEB0-CBE19B1AC121@wisc.edu>
Message-ID: <DM5PR22MB0811B469178176E87A3D3C559F340@DM5PR22MB0811.namprd22.prod.outlook.com>

Could be a MySQL8 issue. That being said, the error might be up father near the top in your log file, I don't see a good error in what you posted.

Read the log from the top down, there will be something that is the first sign of trouble with MySQL, probably within 50 lines or so, that should explain it.

MySQL 8 is a bit different. The GRANTS are a bit different:

CREATE USER 'jeffrey'@'localhost' IDENTIFIED BY 'password';
GRANT ALL ON db1.* TO 'jeffrey'@'localhost';


Also, the docs have this note:

NOTE: For MySQL 8. MySQL 8 uses a new method (caching_sha2_password) as the default authentication plugin instead of the old mysql_native_password that MySQL 5.7 and older used. This may require starting a MySQL 8 server with the --default-authentication-plugin=mysql_native_password option. You may also be able to change the auth mechanism on a per user basis by logging into mysql and running ALTER USER 'archivesspace' IDENTIFIED WITH mysql_native_password BY '123456';. Also be sure to have the LATEST MySQL Connector for Java from MySQL in your /lib/ directory for ArchivesSpace.


I have been able to run ArchivesSpace on 8, but it does have a couple small issues to work through sometimes.

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Brian Sheppard <brian.sheppard at wisc.edu>
Sent: Thursday, May 2, 2019 3:30 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] mysql db connection error


I'm having a problem connecting to a localhost mysql backend and, despite having perused a number of related threads, can't get it to work. I'd appreciate any insight.

AS runs normally when I use the default backend (when AppConfig[:db_url] is commented out). When uncommented,
I get a db connection error, though I can connect to the db via the mysql command-line using the same credentials specified in config.rb. The user has all privileges on the archivesspace db. Also, I see nothing in my mysql_error.log beyond startup comments.

The connector is in lib:
archivesspace_2_5_1/lib/mysql-connector-java-8.0.16.jar

mysql:  Ver 8.0.13 for osx10.12 on x86_64 (Homebrew)
java: version "1.8.0_211"
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin16]
jdbc-mysql gem: jdbc-mysql (5.1.42)

Redacted config.rb line:
AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=[adminuser]&password=[foo]&useUnicode=true&characterEncoding=UTF-8&useSSL=false"

TRACE:
Database connection failed from
/archivesspace_2_5_1/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure' from
archivesspace_2_5_1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in `<class:ArchivesSpaceService>' from
rchivesspace_2_5_1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in `<main>' from
 org/jruby/RubyKernel.java:961:in `require' from
 uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from
 archivesspace_2_5_1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in `block in (root)' from
 org/jruby/RubyBasicObject.java:1687:in `instance_eval' from
 archivesspace_2_5_1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in `(root)' from
 uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55:in `<main>' from
 launcher/launcher.rb:92:in `start_server' from
 launcher/launcher.rb:157:in `main' from
 launcher/launcher.rb:261:in `<main>'


Thanks.
-Brian

?????????????????????????????
Brian Sheppard
UW Digital Collections Center
brian.sheppard at wisc.edu





_______________________________________________
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: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190502/e5a51da6/attachment.html>

From rachel.searcy at nyu.edu  Wed May  8 15:58:34 2019
From: rachel.searcy at nyu.edu (Rachel Aileen Searcy)
Date: Wed, 8 May 2019 15:58:34 -0400
Subject: [Archivesspace_Users_Group] Digitization Work Order plugin +
 ASpace v 2.5.2
In-Reply-To: <CAJnL6E-rovkpvwQ7gEe++7Z9zN5ioZtvS4U0oVVfuLD+XPngvg@mail.gmail.com>
References: <CAJnL6E-rovkpvwQ7gEe++7Z9zN5ioZtvS4U0oVVfuLD+XPngvg@mail.gmail.com>
Message-ID: <CAGFAsrO+owdmTVEGdNhWKKn3qUpRXzSv7DRNFwx0_unz+fgZhA@mail.gmail.com>

Hi Rachel,

I wanted to follow-up to let you know that NYU just upgraded to version
2.5.2 and we are able to successfully run the work order plugin on this
release (we are locally hosted, by the way). I'm not sure if that's helpful
to you, but thought I should mention that it's possible.

Best of luck,

Rachel Searcy (she/her)
Accessioning Archivist, Archival Collections Management
New York University Libraries
212.998.2539 | rachel.searcy at nyu.edu

On Mon, Apr 1, 2019 at 9:35 AM Rachel Trent <racheltrent at gwu.edu> wrote:

> Good morning,
>
> I was wondering if anyone might have had any luck installing the
> Digitization Work Order plugin (
> https://github.com/hudmol/digitization_work_order
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_hudmol_digitization-5Fwork-5Forder&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=zzRnIdx7G_feRCCnDN9VjT-xMmoXallpeqDPWDI5KYo&s=-0dHGj7N7h4PYoMMmu5vQ9SFnCF3dPgjRAKg8BQkKyA&e=>)
> on ArchivesSpace version 2.5.2.
>
> We saw that Tufts, NYU, and perhaps some others have had success with
> installing on version 2.5.1 (thanks Henry and Rachel for your thread back
> in January!).
>
> We've tried installing the plugin on our 2.5.2 instance, but ASpace won't
> restart afterwards. Looking at the logs, I see it loads the configuration
> file, attempts a thread dump, and then hits a server error. It keeps
> retrying and re-hitting the error.
>
> Anyone else have luck (or not have luck) on 2.5.2?
>
> Thanks!
> Rachel
>
> Rachel Trent
> Digital Services Manager
> Special Collections Research Center
> Gelman Library,  George Washington University
> 2130 H Street NW
> Washington DC 20052
> 202.994.4824
> racheltrent at gwu.edu
> _______________________________________________
> 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=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=zzRnIdx7G_feRCCnDN9VjT-xMmoXallpeqDPWDI5KYo&s=IwpPu6T2L58FZ0MNZAP_wpjEnNlQPtVHHfSqdmO74DQ&e=
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190508/e1b46f55/attachment.html>

From livsolis at utexas.edu  Thu May  9 13:09:11 2019
From: livsolis at utexas.edu (Olivia S Solis)
Date: Thu, 9 May 2019 12:09:11 -0500
Subject: [Archivesspace_Users_Group] Browsing for accessions with a certain
	classification
Message-ID: <CAKu+i=04yWA0rn7tvRxX_k=FQGEyYgpCUT3+SnQ2qNpwjLxLZw@mail.gmail.com>

Hi all,

We are using v2.4.1. So as a full disclosure, I've not thoroughly explored
custom reports. But I am wondering about any way to access accession
records as filtered by a particular classification. We're doing our best to
use the native system as is. But the primary accessioner at my institution
had a question I could not answer.

All he wanted to do was to retrieve all the accessions he'd tagged with a
certain classification. Is that not possible through the GUI?

I sent him to browse --> classifications. Then, after selecting a
particular classification, 2 levels down, it gave him a list of records
that had that classification assigned. From there, there was no facet to
get him the information he wanted. JUST accessions, not resources that also
had the classification.

I then looked at the native reports. There was one named Accession and
Linked Subjects, Names and Classifications. 1) the report failed for me. 2)
the results, at least by the report name, will be too broad (he only wants
a certain classification, not all subjects and linked agents), and  3) why
can't we just browse for this without a report.

I can query the database, but am I just missing something? Why can't he
just get to accessions with a particular classification by browsing? I must
be missing something.

Thanks!
Olivia
-- 
Olivia Solis, MSIS
Metadata Coordinator
Dolph Briscoe Center for American History
The University of Texas at Austin
2300 Red River St. Stop D1100
Austin TX, 78712-1426
(512) 232-8013
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190509/30e9c983/attachment.html>

From alexanderduryee at nypl.org  Fri May 10 13:06:20 2019
From: alexanderduryee at nypl.org (Alexander Duryee)
Date: Fri, 10 May 2019 13:06:20 -0400
Subject: [Archivesspace_Users_Group] Components Out of Order in EAD/PDF
Message-ID: <CAK5BadAX3HEQU7Sq7vwy5tG+43_4WYUPkGhpeiF5G3UyZn-YiQ@mail.gmail.com>

After updating our ASpace instance to 2.5.0, we've started to see odd
behavior when exporting PDFs.  Components will occasionally export in the
wrong order in the PDF; for example, a recent collection exported with:

Series I
-- Subseries III
---- [...subseries I components...]
-- Subseries I
---- [...subseries II components...]
-- Subseries II
--- [...subseries III components...]

Strangely, while the subseries components are out of order, their children
are in the correct location/order!

This error has been intermittent; regenerating the PDF immediately resolves
the issue.  Unfortunately, this means that it has not been possible to
reproduce the problem.  Checking the logs, I did not see anything
indicating an error in EAD or PDF generation from ASpace.  I don't believe
that the issue is in the EAD-to-PDF stylesheet, so I'm concerned that our
EAD records may be generating with components in the wrong place in the
finding aid.

Has anyone else encountered issues like this?  My suspicion is that
https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/models/ead.rb#L38
may be surfacing fleeting discrepancies between our search index and
database, but it's difficult to tell, given how intermittent the issue is.

Thanks,
--Alex

-- 
Alexander Duryee
Metadata Archivist
New York Public Library
(917)-229-9590
alexanderduryee at nypl.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190510/35bd5e26/attachment.html>

From suzanna.calev at wilkes.edu  Fri May 10 13:30:29 2019
From: suzanna.calev at wilkes.edu (Calev, Suzanna)
Date: Fri, 10 May 2019 13:30:29 -0400
Subject: [Archivesspace_Users_Group] Feedback/Suggestions on a Digital Asset
	Management System
Message-ID: <CAJ5QzCd-1ytL9hrcWVv93mzOfHTMfJMVjz7uGBgTFTQXM_pRxw@mail.gmail.com>

Hello, everyone!

 My library this past year switched from Archon to ArchivesSpace, and we
currently link our digital collections from our servers but we would like
to implement a Digital Asset Management System at some point in the near
future.

Could any of you provide feedback on which systems work the best for
ArchivesSpace? Pros and Cons for the systems you use, and if they are easy
to migrate data to?

I should also note that we're on a tight budget and we'd like to explore
open source options but are unsure about which ones are the easiest to
implement?

Thank you and I hope to hear from any of you!

Kindest regards,
Suzanna

-- 
Suzanna Calev, MLIS & MA
Archivist/Public Services Librarian
Farley Library
187 South Franklin Street
Wilkes-Barre, PA 18766
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190510/594e2863/attachment.html>

From noah.huffman at duke.edu  Fri May 10 14:02:41 2019
From: noah.huffman at duke.edu (Noah Huffman)
Date: Fri, 10 May 2019 18:02:41 +0000
Subject: [Archivesspace_Users_Group] Feedback/Suggestions on a Digital
 Asset	Management System
In-Reply-To: <CAJ5QzCd-1ytL9hrcWVv93mzOfHTMfJMVjz7uGBgTFTQXM_pRxw@mail.gmail.com>
References: <CAJ5QzCd-1ytL9hrcWVv93mzOfHTMfJMVjz7uGBgTFTQXM_pRxw@mail.gmail.com>
Message-ID: <BN6PR05MB3316BB58D1E2926FB370A9B8E60C0@BN6PR05MB3316.namprd05.prod.outlook.com>

Hi Suzanna,

I?m not sure there is a single DAMS that works best with ArchivesSpace, but there was a session at the ArchivesSpace Online Forum in March exploring how different institutions have integrated ArchivesSpace with various DAMS (DSpace, Islandora, Samvera, etc.).

You can find info about the session (Integrations for Digital Objects) here: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/802127927/ArchivesSpace+Online+Forum+2019

Video of the session is also available: https://www.youtube.com/watch?v=l6k5BJpl3xw&feature=youtu.be

Best,
-Noah

================
Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Calev, Suzanna
Sent: Friday, May 10, 2019 1:30 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Feedback/Suggestions on a Digital Asset Management System

Hello, everyone!

 My library this past year switched from Archon to ArchivesSpace, and we currently link our digital collections from our servers but we would like to implement a Digital Asset Management System at some point in the near future.
Could any of you provide feedback on which systems work the best for ArchivesSpace? Pros and Cons for the systems you use, and if they are easy to migrate data to?
I should also note that we're on a tight budget and we'd like to explore open source options but are unsure about which ones are the easiest to implement?
Thank you and I hope to hear from any of you!
Kindest regards,
Suzanna

--
Suzanna Calev, MLIS & MA
Archivist/Public Services Librarian
Farley Library
187 South Franklin Street
Wilkes-Barre, PA 18766
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190510/4e0b67e6/attachment.html>

From Jessica.Crouch at lyrasis.org  Mon May 13 13:09:03 2019
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Mon, 13 May 2019 17:09:03 +0000
Subject: [Archivesspace_Users_Group] Reminder: May 15 deadline to volunteer
 for the Annual Forum planning group by May 15
Message-ID: <C20677FD-8B87-4914-B305-84AA17A3056F@lyrasis.org>

Don?t forget! The last day to volunteer for our annual forum planning group is May 15! We are looking for volunteers from member institutions of all sizes to form a working group to plan the agenda and program for our largest member event of the year!



ArchivesSpace will hold its 5th annual Member Forum on August 2nd at the Thompson Conference Center at our member institution the University of Texas - Austin.  As in previous years, this will be a free opportunity for staff of ArchivesSpace member institutions to meet and share information with each other and the program team.



Contact Jessica at jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org> to volunteer by May 15th.


Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
Skype: jdowdcrouch

[page1image482511520]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190513/b82d844e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 29058 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190513/b82d844e/attachment-0001.jpg>

From freya.anderson at alaska.gov  Tue May 14 20:17:02 2019
From: freya.anderson at alaska.gov (Anderson, Freya N (EED))
Date: Wed, 15 May 2019 00:17:02 +0000
Subject: [Archivesspace_Users_Group] Rights Statement on public user
	interface
Message-ID: <e5b560e847624671b994071aea6e5de8@SOAJNUEXCH01.soa.alaska.gov>

Hello all,

It was recently pointed out to me by one of our team, as we rush to get content into ArchivesSpace, that the Rights Statement doesn?t show up on the public user interface.  We enter it in the Resource, mark every Publish box, and click Publish All at the end.  Everything looks fine at the staff end, but no rights statement appears for the public.  Is this the way it?s supposed to work?  Is there anything we can do so the right statement shows up, other than adding it in the Notes?

We?re using LibraryHost to host our instance.

Thanks!
Freya

[cid:image001.png at 01D507DF.8CCD64B0]

Freya Anderson
Head, Information Services
Acting Head, Historical Collections
phone: 907.465.1315

Andrew P. Kashevaroff Building
Mail: PO Box 110571, Juneau, AK 99811
Visit: 395 Whittier St., Juneau, AK 99801

email<mailto:freya.anderson at alaska.gov> | web<http://library.alaska.gov/> |  sign up for event notifications<http://list.state.ak.us/mailman/listinfo/at-apk-and-sjm> | The Information Center for Government<http://library.alaska.gov/is/>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190515/84f61f74/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 16891 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190515/84f61f74/attachment.png>

From egadsby at towson.edu  Wed May 15 10:06:24 2019
From: egadsby at towson.edu (Gadsby, Eric T.)
Date: Wed, 15 May 2019 14:06:24 +0000
Subject: [Archivesspace_Users_Group] What are the ramifications of Oracle's
 monetizing binge on ArchivesSpace
Message-ID: <57C26931-B9F6-4263-A047-E91AF91C9D9D@towson.edu>

Good Morning,

I don?t want to be alarmist but what do folks think about Oracle's monetizing anything it?s ever acquired. I know Aspace is java based in more ways than one.  Thanks!







[Towson University logo]<http://www.towson.edu/>

Eric T. Gadsby
IT Operations Specialist | Albert S. Cook Library
?
P: 410-704-3340
egadsby at towson.edu<mailto:egadsby at towson.edu>  |  libraries.towson.edu<http://www.towson.edu/https:/libraries.towson.edu>
?
Pronouns: he/him/his


Confidentiality Notice: This message may contain information that is confidential, privileged, proprietary, or otherwise legally exempt from disclosure. If you are not the intended recipient, you are notified that you are not authorized to read, print, copy or disseminate this message, any part of it, or any attachments. If this message has been sent to you in error, please notify the sender by replying to this transmission, or by calling Albert S. Cook Library at 410-704-3340.






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190515/3501bbdf/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2210 bytes
Desc: image001.gif
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190515/3501bbdf/attachment.gif>

From blake.carver at lyrasis.org  Wed May 15 10:24:06 2019
From: blake.carver at lyrasis.org (Blake Carver)
Date: Wed, 15 May 2019 14:24:06 +0000
Subject: [Archivesspace_Users_Group] What are the ramifications of
 Oracle's monetizing binge on ArchivesSpace
In-Reply-To: <57C26931-B9F6-4263-A047-E91AF91C9D9D@towson.edu>
References: <57C26931-B9F6-4263-A047-E91AF91C9D9D@towson.edu>
Message-ID: <DM5PR22MB08118347F48C2BA74FB033869F090@DM5PR22MB0811.namprd22.prod.outlook.com>

eh, I wouldn't worry all that much. Maybe worry just a little, just enough keep an eye on things. Red Hat has control of openjdk, so I assume that'll be fine. It'll run fine on any of the MySQL clones out there, I run it on Maria locally here and it's fine. I'd think there's just way too much out in the world that depend on Java/MySQL/Etc for them to really mess things up in a big way.

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Gadsby, Eric T. <egadsby at towson.edu>
Sent: Wednesday, May 15, 2019 10:06 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] What are the ramifications of Oracle's monetizing binge on ArchivesSpace


Good Morning,



I don?t want to be alarmist but what do folks think about Oracle's monetizing anything it?s ever acquired. I know Aspace is java based in more ways than one.  Thanks!







[Towson University logo]<http://www.towson.edu/>

Eric T. Gadsby

IT Operations Specialist | Albert S. Cook Library

?

P: 410-704-3340
egadsby at towson.edu<mailto:egadsby at towson.edu>  |  libraries.towson.edu<http://www.towson.edu/https:/libraries.towson.edu>

?

Pronouns: he/him/his

Confidentiality Notice: This message may contain information that is confidential, privileged, proprietary, or otherwise legally exempt from disclosure. If you are not the intended recipient, you are notified that you are not authorized to read, print, copy or disseminate this message, any part of it, or any attachments. If this message has been sent to you in error, please notify the sender by replying to this transmission, or by calling Albert S. Cook Library at 410-704-3340.






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190515/9f83b8ef/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2210 bytes
Desc: image001.gif
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190515/9f83b8ef/attachment.gif>

From christine.dibella at lyrasis.org  Wed May 15 11:25:07 2019
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Wed, 15 May 2019 15:25:07 +0000
Subject: [Archivesspace_Users_Group] release candidate available -
	ArchivesSpace v2.6.0-RC1
Message-ID: <CY4PR2201MB11432950B4C3AE521ED9D1AEF1090@CY4PR2201MB1143.namprd22.prod.outlook.com>

Hello ArchivesSpace members,

The ArchivesSpace team is pleased to announce a release candidate, v2.6.0-RC1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.6.0-RC1 or test it out without downloading at http://test.archivesspace.org/staff (username admin /password admin). We do encourage you to download and try it out with your own local setup and/or data if you can for the most accurate results.

This release candidate contains program-led and community pull requests that provide feature enhancements, bug fixes, infrastructure improvements, and documentation updates. You'll see many small changes to the staff and public interfaces that came out of community-prioritized requests. There is also a significant revamp of how background jobs run, including a new reports page layout. While testing, we highly encourage you to not only check out the new changes, but also to make sure that features you already use are working as intended.

This release candidate also has a new feature guided by a community-initiated and authored specification, the option to generate human-readable URLs for use in the public user interface. Human-readable urls can help improve the user experience and also contribute to Search Engage Optimization (SEO). More information about how human-readable URLs work in ArchivesSpace is available at https://docs.google.com/document/d/1ycNuk86TD9jGHS5YzTw3tjQY3Kuln3F4fvR7kLlfigQ/edit?usp=sharing. I encourage you to contribute ideas and even edits to this documentation while testing human-readable urls. Thanks to Celia Caust-Ellenbogen and Cory Nimer for authoring and circulating the human-readable URLs specification throughout the community last year.

Thanks to the many community members who made contributions to the work reflected in this release candidate, including individual archives staff and developers, our Development Prioritization sub-team, Testing sub-team, Technical Documentation sub-team, and the Core Committers Group.

We'll be collecting feedback through Friday, May 24. Please let us know at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org> if you notice any problems with the specific areas addressed in this release, or if anything that was working before no longer is. Barring major issues, we expect to release v2.6.0 by the end of the month.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190515/4732f54d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190515/4732f54d/attachment.jpg>

From mpaquette at smith.edu  Wed May 15 15:30:31 2019
From: mpaquette at smith.edu (Michelle Paquette)
Date: Wed, 15 May 2019 15:30:31 -0400
Subject: [Archivesspace_Users_Group] Disallows in robots.txt?
Message-ID: <CANgF2FuJ=vsh5OVw499WDP86oELwm=HMskJNTFajK28Uz+HRhw@mail.gmail.com>

Hello all,

For those of you who are already using the Public User Interface, I
wondered if you had suggested disallows for the robots.txt. We're planning
to disallow on search but wasn't sure of the arguments for or against other
disallows. Any advice much appreciated!

Michelle Paquette

-- 
Michelle Paquette
Metadata & Technical Services Archivist
Special Collections
Smith College
413-585-7029
mpaquette at smith.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190515/48b9cdd3/attachment.html>

From billb at ssec.wisc.edu  Wed May 15 15:55:36 2019
From: billb at ssec.wisc.edu (Bill Bellon)
Date: Wed, 15 May 2019 19:55:36 +0000
Subject: [Archivesspace_Users_Group] Migration from Archon - login Endpoint
	not found
Message-ID: <SN6PR06MB6368D5F7BCEE36F6C9B14909EF090@SN6PR06MB6368.namprd06.prod.outlook.com>

I'm trying to migrate from Archon (3.21 rev-3) to Archives Space (2.5.2) using the Java desktop migration tool after having followed all of the instructions.

I filled out the tool with the following values:

------------------------------------------------------------------------------------------------------
Archon Source:                                https://SRC-ARCHON-WEBSITE.COM    (this is a placeholder as I don't want to publicly share the actual URLs yet)

Archon User:                                    THE_USER_NAME                                    (tested on the website)

Password:                                         THE_PASSWORD                                      (tested on the website)

Download Digital Object Files:      unchecked

Set Default Repository:                  unchecked

Host:                                                  https://DEST-ARCHIVESSPACE-ADMIN.COM    (this is a placeholder as I don't want to publicly share the actual URLs yet)

A Space admin:                                 THE_USER_NAME                             (tested on the website)

Password:                                          THE_PASSWORD                               (tested on the website)

Reset Password:                               Left blank

Migration Options:                          -bbcode_html                                    (left the default value as is)
------------------------------------------------------------------------------------------------------

When I click on the "Copy to Archives Space" button, I get the following in the Error Log:

RECORD CONVERSION ERRORS/WARNINGS ( 0 ) ::

RECORD SAVE ERRORS ( 0 ) ::

Endpoint: https://DEST-ARCHIVESSPACE-ADMIN.COM//users/admin/login<https://DEST-ARCHIVESSPACE-ADMIN.COM/users/admin/login>
AR Identifier:N/A
Status code: 404
Status text: Not Found
<!DOCTYPE html>
<html>
<head>
  <title>The page you were looking for doesn't exist (404)</title>
  <style type="text/css">
    body { background-color: #fff; color: #666; text-align: center; font-family: arial, sans-serif; }
    div.dialog {
      width: 25em;
      padding: 0 4em;
      margin: 4em auto 0 auto;
      border: 1px solid #ccc;
      border-right-color: #999;
      border-bottom-color: #999;
    }
    h1 { font-size: 100%; color: #f00; line-height: 1.5em; }
  </style>
</head>

<body>
  <div class="dialog">
    <h1>The page you were looking for doesn't exist.</h1>
    <p>You may have mistyped the address or the page may have moved.</p>
  </div>
</body>
</html>

Running for: 5.09 sec

Current # of Records Copied:

My IT department set up Archives Space with two URLs - a public facing one (let's call that https://DEST-ARCHIVESSPACE.COM) and
a separate URL for the backend admin interface (https://DEST-ARCHIVESSPACE-ADMIN.COM).

I tried the tool using the public URL for host and got the same results.

It looks like the Java desktop migration tool is trying to login to my Archives Space website via a URL path that doesn't exist
(which I've copied the URL into my browser and confirmed the URL path doesn't exist).

Suggestions?

Bill
--
Bill Bellon
SSEC Webmaster
Space Science and Engineering Center
University of Wisconsin - Madison

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190515/de1bdc3a/attachment.html>

From brian.harrington at lyrasis.org  Wed May 15 16:21:17 2019
From: brian.harrington at lyrasis.org (Brian Harrington)
Date: Wed, 15 May 2019 20:21:17 +0000
Subject: [Archivesspace_Users_Group] Migration from Archon - login
 Endpoint	not found
In-Reply-To: <SN6PR06MB6368D5F7BCEE36F6C9B14909EF090@SN6PR06MB6368.namprd06.prod.outlook.com>
References: <SN6PR06MB6368D5F7BCEE36F6C9B14909EF090@SN6PR06MB6368.namprd06.prod.outlook.com>
Message-ID: <C1197FBB-CF59-4E1F-95B0-1A4CCC1B9B59@lyrasis.org>

Hi Bill,

You need to point the migration tool at the API endpoint, rather than either of the public or staff user interfaces.  It normally lives on port 8089, but your IT folks probably mapped it to a third URL.   I would check with them and see what they say.

I hope this helps.

Brian

? 
Brian Harrington
Migration Specialist
LYRASIS
brian.harrington at lyrasis.org
Skype: abbistani

> On May 15, 2019, at 3:55 PM, Bill Bellon <billb at ssec.wisc.edu> wrote:
> 
> I?m trying to migrate from Archon (3.21 rev-3) to Archives Space (2.5.2) using the Java desktop migration tool after having followed all of the instructions.
>  
> I filled out the tool with the following values:
>  
> ------------------------------------------------------------------------------------------------------
> Archon Source:                                https://SRC-ARCHON-WEBSITE.COM    (this is a placeholder as I don?t want to publicly share the actual URLs yet)
>  
> Archon User:                                    THE_USER_NAME                                    (tested on the website)
>  
> Password:                                         THE_PASSWORD                                      (tested on the website)
>  
> Download Digital Object Files:      unchecked
>  
> Set Default Repository:                  unchecked
>  
> Host:                                                  https://DEST-ARCHIVESSPACE-ADMIN.COM    (this is a placeholder as I don?t want to publicly share the actual URLs yet)
>  
> A Space admin:                                 THE_USER_NAME                             (tested on the website)
>  
> Password:                                          THE_PASSWORD                               (tested on the website)
>  
> Reset Password:                               Left blank
>  
> Migration Options:                          -bbcode_html                                    (left the default value as is)
> ------------------------------------------------------------------------------------------------------
>  
> When I click on the ?Copy to Archives Space? button, I get the following in the Error Log:
>  
> RECORD CONVERSION ERRORS/WARNINGS ( 0 ) ::
>  
> RECORD SAVE ERRORS ( 0 ) ::
>  
> Endpoint: https://DEST-ARCHIVESSPACE-ADMIN.COM//users/admin/login
> AR Identifier:N/A
> Status code: 404
> Status text: Not Found
> <!DOCTYPE html>
> <html>
> <head>
>   <title>The page you were looking for doesn't exist (404)</title>
>   <style type="text/css">
>     body { background-color: #fff; color: #666; text-align: center; font-family: arial, sans-serif; }
>     div.dialog {
>       width: 25em;
>       padding: 0 4em;
>       margin: 4em auto 0 auto;
>       border: 1px solid #ccc;
>       border-right-color: #999;
>       border-bottom-color: #999;
>     }
>     h1 { font-size: 100%; color: #f00; line-height: 1.5em; }
>   </style>
> </head>
>                 
> <body>
>   <div class="dialog">
>     <h1>The page you were looking for doesn't exist.</h1>
>     <p>You may have mistyped the address or the page may have moved.</p>
>   </div>
> </body>
> </html>
>                 
> Running for: 5.09 sec
>                 
> Current # of Records Copied:
>  
> My IT department set up Archives Space with two URLs ? a public facing one (let?s call that https://DEST-ARCHIVESSPACE.COM) and
> a separate URL for the backend admin interface (https://DEST-ARCHIVESSPACE-ADMIN.COM). 
>  
> I tried the tool using the public URL for host and got the same results.
>  
> It looks like the Java desktop migration tool is trying to login to my Archives Space website via a URL path that doesn?t exist
> (which I?ve copied the URL into my browser and confirmed the URL path doesn?t exist).
>  
> Suggestions?  
>  
> Bill
> --
> Bill Bellon
> SSEC Webmaster
> Space Science and Engineering Center
> University of Wisconsin - Madison
>  
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

? 
Brian Harrington
Migration Specialist
LYRASIS
brian.harrington at lyrasis.org
Skype: abbistani




From blake.carver at lyrasis.org  Wed May 15 18:42:52 2019
From: blake.carver at lyrasis.org (Blake Carver)
Date: Wed, 15 May 2019 22:42:52 +0000
Subject: [Archivesspace_Users_Group] Disallows in robots.txt?
In-Reply-To: <CANgF2FuJ=vsh5OVw499WDP86oELwm=HMskJNTFajK28Uz+HRhw@mail.gmail.com>
References: <CANgF2FuJ=vsh5OVw499WDP86oELwm=HMskJNTFajK28Uz+HRhw@mail.gmail.com>
Message-ID: <DM5PR22MB08111252351E2E28D81BD00F9F090@DM5PR22MB0811.namprd22.prod.outlook.com>

We've found this works pretty well:

Disallow: /search*
Disallow: /inventory/*
Disallow: /collection_organization/*
Disallow: /repositories/*/top_containers/*
Disallow: /check_session*
Disallow: /repositories/*/resources/*/tree/*


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Michelle Paquette <mpaquette at smith.edu>
Sent: Wednesday, May 15, 2019 3:30 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Disallows in robots.txt?

Hello all,

For those of you who are already using the Public User Interface, I wondered if you had suggested disallows for the robots.txt. We're planning to disallow on search but wasn't sure of the arguments for or against other disallows. Any advice much appreciated!

Michelle Paquette

--
Michelle Paquette
Metadata & Technical Services Archivist
Special Collections
Smith College
413-585-7029
mpaquette at smith.edu<mailto:mpaquette at smith.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190515/c7086bbb/attachment.html>

From eloehr at smith.edu  Thu May 16 09:48:18 2019
From: eloehr at smith.edu (Eric Loehr)
Date: Thu, 16 May 2019 09:48:18 -0400
Subject: [Archivesspace_Users_Group] Reindexing problems
Message-ID: <CADuR=+SwYdZmOUHmeCwUGmw9DySkiKiAU61pcy7Q8QapbfOX3w@mail.gmail.com>

Hi all,

We're having reindexing issues with our local test version of
ArchivesSpace; on Monday I uploaded a copy of our production database and
also deleted the /data/indexer_state and data/indexer_pui_state to force a
reindex.  Looking at the /data/ directory today showed that neither of
those directories had been recreated, and the reindexing didn't work.  I am
seeing an .archivesspace.pid file in the /data/ directory -- does that mean
that he reindexing could still be running?


Thanks or any insight --

Eric


-- 
Eric Loehr
Head of Library Technology Services
Smith College Libraries
eloehr at smith.edu
(413) 585-2969

*Young Library is now our central campus hub. The latest information is on
the Smith College Libraries web site <https://www.smith.edu/libraries/>. *

*Please don't hesitate to be in touch with questions, comments or feedback
-- Ask Us! <http://smith.libanswers.com/ask>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190516/45a89739/attachment.html>

From blake.carver at lyrasis.org  Thu May 16 15:52:28 2019
From: blake.carver at lyrasis.org (Blake Carver)
Date: Thu, 16 May 2019 19:52:28 +0000
Subject: [Archivesspace_Users_Group] Reindexing problems
In-Reply-To: <CADuR=+SwYdZmOUHmeCwUGmw9DySkiKiAU61pcy7Q8QapbfOX3w@mail.gmail.com>
References: <CADuR=+SwYdZmOUHmeCwUGmw9DySkiKiAU61pcy7Q8QapbfOX3w@mail.gmail.com>
Message-ID: <DM5PR22MB0811173146059CAB8490C9609F0A0@DM5PR22MB0811.namprd22.prod.outlook.com>

Those files should show up right away. Sounds like it's crashed, what's in the logs?
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Eric Loehr <eloehr at smith.edu>
Sent: Thursday, May 16, 2019 9:48 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Reindexing problems

Hi all,

We're having reindexing issues with our local test version of ArchivesSpace; on Monday I uploaded a copy of our production database and also deleted the /data/indexer_state and data/indexer_pui_state to force a reindex.  Looking at the /data/ directory today showed that neither of those directories had been recreated, and the reindexing didn't work.  I am seeing an .archivesspace.pid file in the /data/ directory -- does that mean that he reindexing could still be running?


Thanks or any insight --

Eric


--
Eric Loehr
Head of Library Technology Services
Smith College Libraries
eloehr at smith.edu<mailto:eloehr at smith.edu>
(413) 585-2969

Young Library is now our central campus hub. The latest information is on the Smith College Libraries web site<https://www.smith.edu/libraries/>.

Please don't hesitate to be in touch with questions, comments or feedback -- Ask Us!<http://smith.libanswers.com/ask>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190516/d225b29f/attachment.html>

From eloehr at smith.edu  Fri May 17 10:12:22 2019
From: eloehr at smith.edu (Eric Loehr)
Date: Fri, 17 May 2019 10:12:22 -0400
Subject: [Archivesspace_Users_Group] Reindexing problems
In-Reply-To: <DM5PR22MB0811173146059CAB8490C9609F0A0@DM5PR22MB0811.namprd22.prod.outlook.com>
References: <CADuR=+SwYdZmOUHmeCwUGmw9DySkiKiAU61pcy7Q8QapbfOX3w@mail.gmail.com>
 <DM5PR22MB0811173146059CAB8490C9609F0A0@DM5PR22MB0811.namprd22.prod.outlook.com>
Message-ID: <CADuR=+RB-pKVzL8e9C-SH1KH4YTmv1V47XYo-zmP+PtuvLCW6w@mail.gmail.com>

Hi Blake and all,

Yesterday I tried again, but this time deleted everything in the /data/
directory (although the /solr_backups and /tmp/ directory didn't delete
with the rest of the directories).

Today nothing is showing up in the gui and still no /indexer_state/
directory in the /data/ directory:
[image: image.png]

I'm seeing this in the log file:
archivesspace.out:850: E, [2019-05-16T13:00:00.061372 #7940] ERROR -- :
Thread-2292: Solr snapshot failed (unknown file type: /data/indexer_state)
- attempt 0
archivesspace.out:853: E, [2019-05-16T13:00:00.068175 #7940] ERROR -- :
Thread-2292: Solr snapshot failed (unknown file type: /data/indexer_state)
- attempt 1
archivesspace.out:855: E, [2019-05-16T13:00:00.073198 #7940] ERROR -- :
Thread-2292: Solr snapshot failed (unknown file type: /data/indexer_state)
- attempt 2
archivesspace.out:856: E, [2019-05-16T13:00:00.077054 #7940] ERROR -- :
Thread-2292: Solr snapshot failed (unknown file type: /data/indexer_state)
- attempt 3
archivesspace.out:857: E, [2019-05-16T13:00:00.079964 #7940] ERROR -- :
Thread-2292: Solr snapshot failed (unknown file type: /data/indexer_state)
- attempt 4
archivesspace.out:860: Solr snapshot failed after 5 retries: unknown file
type: /home/as/as252/data/indexer_state

Any ideas on how to fix this?

Thanks - -

Eric


On Thu, May 16, 2019 at 3:52 PM Blake Carver <blake.carver at lyrasis.org>
wrote:

> Those files should show up right away. Sounds like it's crashed, what's in
> the logs?
> ------------------------------
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
> Eric Loehr <eloehr at smith.edu>
> *Sent:* Thursday, May 16, 2019 9:48 AM
> *To:* Archivesspace Users Group
> *Subject:* [Archivesspace_Users_Group] Reindexing problems
>
> Hi all,
>
> We're having reindexing issues with our local test version of
> ArchivesSpace; on Monday I uploaded a copy of our production database and
> also deleted the /data/indexer_state and data/indexer_pui_state to force a
> reindex.  Looking at the /data/ directory today showed that neither of
> those directories had been recreated, and the reindexing didn't work.  I am
> seeing an .archivesspace.pid file in the /data/ directory -- does that mean
> that he reindexing could still be running?
>
>
> Thanks or any insight --
>
> Eric
>
>
> --
> Eric Loehr
> Head of Library Technology Services
> Smith College Libraries
> eloehr at smith.edu
> (413) 585-2969
>
> *Young Library is now our central campus hub. The latest information is on
> the Smith College Libraries web site <https://www.smith.edu/libraries/>. *
>
> *Please don't hesitate to be in touch with questions, comments or feedback
> -- Ask Us! <http://smith.libanswers.com/ask>*
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Eric Loehr
Head of Library Technology Services
Smith College Libraries
eloehr at smith.edu
(413) 585-2969

*Young Library is now our central campus hub. The latest information is on
the Smith College Libraries web site <https://www.smith.edu/libraries/>. *

*Please don't hesitate to be in touch with questions, comments or feedback
-- Ask Us! <http://smith.libanswers.com/ask>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190517/716559cc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 5596 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190517/716559cc/attachment.png>

From blake.carver at lyrasis.org  Fri May 17 10:22:46 2019
From: blake.carver at lyrasis.org (Blake Carver)
Date: Fri, 17 May 2019 14:22:46 +0000
Subject: [Archivesspace_Users_Group] Reindexing problems
In-Reply-To: <CADuR=+RB-pKVzL8e9C-SH1KH4YTmv1V47XYo-zmP+PtuvLCW6w@mail.gmail.com>
References: <CADuR=+SwYdZmOUHmeCwUGmw9DySkiKiAU61pcy7Q8QapbfOX3w@mail.gmail.com>
 <DM5PR22MB0811173146059CAB8490C9609F0A0@DM5PR22MB0811.namprd22.prod.outlook.com>,
 <CADuR=+RB-pKVzL8e9C-SH1KH4YTmv1V47XYo-zmP+PtuvLCW6w@mail.gmail.com>
Message-ID: <DM5PR22MB0811B898A670C39AB4FF44A49F0B0@DM5PR22MB0811.namprd22.prod.outlook.com>

Permissions maybe? There must be more errors in the log. grep it for FATAL and ERROR
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Eric Loehr <eloehr at smith.edu>
Sent: Friday, May 17, 2019 10:12 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Reindexing problems

Hi Blake and all,

Yesterday I tried again, but this time deleted everything in the /data/ directory (although the /solr_backups and /tmp/ directory didn't delete with the rest of the directories).

Today nothing is showing up in the gui and still no /indexer_state/ directory in the /data/ directory:
[image.png]

I'm seeing this in the log file:
archivesspace.out:850: E, [2019-05-16T13:00:00.061372 #7940] ERROR -- : Thread-2292: Solr snapshot failed (unknown file type: /data/indexer_state) - attempt 0
archivesspace.out:853: E, [2019-05-16T13:00:00.068175 #7940] ERROR -- : Thread-2292: Solr snapshot failed (unknown file type: /data/indexer_state) - attempt 1
archivesspace.out:855: E, [2019-05-16T13:00:00.073198 #7940] ERROR -- : Thread-2292: Solr snapshot failed (unknown file type: /data/indexer_state) - attempt 2
archivesspace.out:856: E, [2019-05-16T13:00:00.077054 #7940] ERROR -- : Thread-2292: Solr snapshot failed (unknown file type: /data/indexer_state) - attempt 3
archivesspace.out:857: E, [2019-05-16T13:00:00.079964 #7940] ERROR -- : Thread-2292: Solr snapshot failed (unknown file type: /data/indexer_state) - attempt 4
archivesspace.out:860: Solr snapshot failed after 5 retries: unknown file type: /home/as/as252/data/indexer_state

Any ideas on how to fix this?

Thanks - -

Eric


On Thu, May 16, 2019 at 3:52 PM Blake Carver <blake.carver at lyrasis.org<mailto:blake.carver at lyrasis.org>> wrote:
Those files should show up right away. Sounds like it's crashed, what's in the logs?
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Eric Loehr <eloehr at smith.edu<mailto:eloehr at smith.edu>>
Sent: Thursday, May 16, 2019 9:48 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Reindexing problems

Hi all,

We're having reindexing issues with our local test version of ArchivesSpace; on Monday I uploaded a copy of our production database and also deleted the /data/indexer_state and data/indexer_pui_state to force a reindex.  Looking at the /data/ directory today showed that neither of those directories had been recreated, and the reindexing didn't work.  I am seeing an .archivesspace.pid file in the /data/ directory -- does that mean that he reindexing could still be running?


Thanks or any insight --

Eric


--
Eric Loehr
Head of Library Technology Services
Smith College Libraries
eloehr at smith.edu<mailto:eloehr at smith.edu>
(413) 585-2969

Young Library is now our central campus hub. The latest information is on the Smith College Libraries web site<https://www.smith.edu/libraries/>.

Please don't hesitate to be in touch with questions, comments or feedback -- Ask Us!<http://smith.libanswers.com/ask>

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Eric Loehr
Head of Library Technology Services
Smith College Libraries
eloehr at smith.edu<mailto:eloehr at smith.edu>
(413) 585-2969

Young Library is now our central campus hub. The latest information is on the Smith College Libraries web site<https://www.smith.edu/libraries/>.

Please don't hesitate to be in touch with questions, comments or feedback -- Ask Us!<http://smith.libanswers.com/ask>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190517/ec02210c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 5596 bytes
Desc: image.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190517/ec02210c/attachment.png>

From sdm7g at virginia.edu  Fri May 17 17:56:23 2019
From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g))
Date: Fri, 17 May 2019 21:56:23 +0000
Subject: [Archivesspace_Users_Group] A more forgiving version of
 oai-harvest	& public OAI feeds
In-Reply-To: <7F66E65C-C224-446B-9E2F-452484187538@virginia.edu>
References: <7F66E65C-C224-446B-9E2F-452484187538@virginia.edu>
Message-ID: <87A30F18-82E1-4340-B8CE-C50B843F4961@virginia.edu>


We?ve added a column to the ASpace PUI in the Wild document for OAI feeds:
https://docs.google.com/spreadsheets/d/1IVDp_tN6swURAZr0o-OG5pHwQiZP2oTwnp436WYaB9w/edit#gid=0 <https://docs.google.com/spreadsheets/d/1IVDp_tN6swURAZr0o-OG5pHwQiZP2oTwnp436WYaB9w/edit#gid=0>

And added the feeds I?ve been using and a few others I?ve discovered. 

Then I discovered a whole bunch of OAI feeds found by appending /oai to the PUI URL in the above document. 


https://archivessearch.bsu.edu/oai
https://beloitarchives.lyrasistechnology.org/oai
https://archives.caldwell.edu/oai
https://collections.archives.caltech.edu/oai
https://archives.baltimorecarmel.org/oai
https://archivesspace.case.edu/oai
https://archives.colgate.edu/oai
https://archives.depaul.edu/oai
https://archives.dom.edu/oai
https://archives.elon.edu/oai
https://fortworthlibrary.lyrasistechnology.org/oai
https://archives.library.fau.edu/oai
https://archives.fgcu.edu/oai
https://archives.fiu.edu/oai
https://archives.lib.fsu.edu/oai
https://gvsu.lyrasistechnology.org/oai
https://archives.hamilton.edu/oai
https://archivesspace.hws.edu/oai
https://ial.lyrasistechnology.org/oai
https://aspace.lib.jmu.edu/oai
https://kinkaid.lyrasistechnology.org/oai
https://archives.mercyhurst.edu/oai
https://emmas-lib.mit.edu/oai
https://archives.multco.us/oai
https://nmu.lyrasistechnology.org/oai
https://opspecialcollections.lyrasistechnology.org/oai
https://aspace.libraries.psu.edu/public/oai
https://specialcollections.pequotlibrary.org/oai
https://archives.pueblolibrary.org/oai
https://catalog.sos.ri.gov/oai
https://scplarchives-public.lyrasistechnology.org/oai
https://sdarchives.lyrasistechnology.org/oai
https://archives.tntech.edu/oai
https://aspace.organhistoricalsociety.org/oai
https://monticello-archiveguides.lyrasistechnology.org/oai
https://archives.colorado.edu/oai
https://archivescatalog.udayton.edu/oai
https://findingaids.libraries.uc.edu/oai
https://archives.nebraska.edu/oai
https://archives.unf.edu/oai
https://archivesspace.library.nd.edu/oai
https://archives.library.upike.edu/oai
https://specialcollections.usm.edu/oai
https://archives.vmfa.museum/oai
https://wcu.lyrasistechnology.org/oai
https://archives.yale.edu/oai



> On Apr 19, 2019, at 7:17 PM, Majewski, Steven Dennis (sdm7g) <sdm7g at virginia.edu> wrote

> 
> My current collection of feeds is: 
> 
> export VT=https://aspace.lib.vt.edu:8082/ <https://aspace.lib.vt.edu:8082/>
> export VMFA=https://archives.vmfa.museum/oai <https://archives.vmfa.museum/oai>
> export JMU=https://aspace.lib.jmu.edu/oai <https://aspace.lib.jmu.edu/oai>
> export VCU=https://archives.library.vcu.edu/oai <https://archives.library.vcu.edu/oai>
> export UVA=https://archives-oai.lib.virginia.edu <https://archives-oai.lib.virginia.edu/>
> 
> 
> If you submit your public ArchivesSpace OAI endpoint URLs as reply to this thread, I will collect them to put on the Wiki somewhere. 
> 
> 
> ? Steve Majewski
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190517/bfad4ebe/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3598 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190517/bfad4ebe/attachment.bin>

From mark.custer at yale.edu  Sun May 19 20:47:07 2019
From: mark.custer at yale.edu (Custer, Mark)
Date: Mon, 20 May 2019 00:47:07 +0000
Subject: [Archivesspace_Users_Group] Rights Statement on public
	user	interface
In-Reply-To: <e5b560e847624671b994071aea6e5de8@SOAJNUEXCH01.soa.alaska.gov>
References: <e5b560e847624671b994071aea6e5de8@SOAJNUEXCH01.soa.alaska.gov>
Message-ID: <BN8PR08MB57770EE6BF985A9E82C16F738C060@BN8PR08MB5777.namprd08.prod.outlook.com>

Dear Freya,

Unfortunately that's right.  The rights statement records (as well as some other record types, like event records) do not appear in the public interface as far as I'm aware.  They also do not get added to EAD exports (although they could, if there were a mapping for that data).

That said, the rights metadata is still available in the public interface for display, so that data could be surfaced with a plugin with any version of ArchivesSpace.  I don't know of any plugins offhand that do that (maybe others on the list do?), but I could come up with a pretty basic one if that's of interest.

There is lots of data that can be stored in an ArchivesSpace rights statements, though (such as linked agents, acts, external documents, and notes), which makes adding them to the PUI a bit of a design challenge. I'll also admit that I'm not very familiar with those records in ArchivesSpace. Right now, we only use  notes to capture that type of information.

Which fields are you using with your rights statements?

All my best,

Mark


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Anderson, Freya N (EED) <freya.anderson at alaska.gov>
Sent: Tuesday, May 14, 2019 8:17 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Rights Statement on public user interface


Hello all,



It was recently pointed out to me by one of our team, as we rush to get content into ArchivesSpace, that the Rights Statement doesn?t show up on the public user interface.  We enter it in the Resource, mark every Publish box, and click Publish All at the end.  Everything looks fine at the staff end, but no rights statement appears for the public.  Is this the way it?s supposed to work?  Is there anything we can do so the right statement shows up, other than adding it in the Notes?



We?re using LibraryHost to host our instance.



Thanks!

Freya



[cid:image001.png at 01D507DF.8CCD64B0]

Freya Anderson

Head, Information Services

Acting Head, Historical Collections

phone: 907.465.1315



Andrew P. Kashevaroff Building

Mail: PO Box 110571, Juneau, AK 99811

Visit: 395 Whittier St., Juneau, AK 99801



email<mailto:freya.anderson at alaska.gov> | web<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flibrary.alaska.gov%2F&data=02%7C01%7Cmark.custer%40yale.edu%7C9995d0a848f049d8428408d6d8caad6c%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636934762377844252&sdata=hUlnyA1RfmUYxxJyQ2SgZlQmS3B96zqYYmJHBqB%2BIds%3D&reserved=0> |  sign up for event notifications<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.state.ak.us%2Fmailman%2Flistinfo%2Fat-apk-and-sjm&data=02%7C01%7Cmark.custer%40yale.edu%7C9995d0a848f049d8428408d6d8caad6c%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636934762377854261&sdata=UMb56zC%2FonMsuJ0FNV9dDoBA1oeoq8wJwDDKdsHxlCo%3D&reserved=0> | The Information Center for Government<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flibrary.alaska.gov%2Fis%2F&data=02%7C01%7Cmark.custer%40yale.edu%7C9995d0a848f049d8428408d6d8caad6c%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636934762377854261&sdata=%2B8QyAazSkUS7T%2BG0eDc1b4Pt1Pjyvc9TtrJU1hwgOHA%3D&reserved=0>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190520/03bbe2b6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 16891 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190520/03bbe2b6/attachment.png>

From billb at ssec.wisc.edu  Mon May 20 12:58:09 2019
From: billb at ssec.wisc.edu (Bill Bellon)
Date: Mon, 20 May 2019 16:58:09 +0000
Subject: [Archivesspace_Users_Group] Importing from Archon: Recommended
 location for Digital Objects source files?
Message-ID: <SN6PR06MB63685BF0A2FE971E64E9BCABEF060@SN6PR06MB6368.namprd06.prod.outlook.com>

I'm migrating our collection from Archon to ArchivesSpace and the migration tool requires that
I specify a URL where I will upload the digital object source files (in this case, images)
after the migration.

Is there a recommended location to store digital object files?  Can ArchivesSpace serve static files?  If
so, is there documentation somewhere regarding this (i.e., how to serve static files, such as images, from an ArchivesSpace
website)?  If this is not recommended, then I'm assuming I can just put the digital object files on
some other web server that I control?

--
Bill Bellon
SSEC Webmaster
Space Science and Engineering Center
University of Wisconsin - Madison

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190520/a1adc840/attachment.html>

From mcallahan at smith.edu  Mon May 20 13:08:48 2019
From: mcallahan at smith.edu (Maureen Callahan)
Date: Mon, 20 May 2019 13:08:48 -0400
Subject: [Archivesspace_Users_Group] Rights Statement on public user
	interface
In-Reply-To: <BN8PR08MB57770EE6BF985A9E82C16F738C060@BN8PR08MB5777.namprd08.prod.outlook.com>
References: <e5b560e847624671b994071aea6e5de8@SOAJNUEXCH01.soa.alaska.gov>
 <BN8PR08MB57770EE6BF985A9E82C16F738C060@BN8PR08MB5777.namprd08.prod.outlook.com>
Message-ID: <CAH0VKbAGoSmCF2BX7bT0Wi1oKnQ7ow51BQfDL2Qo7a1H51GRXw@mail.gmail.com>

One thing that I would add to Mark's reply is that it's worth thinking
through how you're using Rights statements -- sometimes I've noticed that
information that might be better suited to Conditions Governing Access
(DACS 4.1) and Conditions Governing Use (DACS 4.4) ends up there. Those
elements do show up in the PUI and in EAD exports.

MC

On Sun, May 19, 2019 at 8:47 PM Custer, Mark <mark.custer at yale.edu> wrote:

> Dear Freya,
>
> Unfortunately that's right.  The rights statement records (as well as some
> other record types, like event records) do not appear in the public
> interface as far as I'm aware.  They also do not get added to EAD exports
> (although they could, if there were a mapping for that data).
>
> That said, the rights metadata is still available in the public interface
> for display, so that data could be surfaced with a plugin with any version
> of ArchivesSpace.  I don't know of any plugins offhand that do that (maybe
> others on the list do?), but I could come up with a pretty basic one if
> that's of interest.
>
> There is lots of data that can be stored in an ArchivesSpace rights
> statements, though (such as linked agents, acts, external documents, and
> notes), which makes adding them to the PUI a bit of a design challenge.
> I'll also admit that I'm not very familiar with those records in
> ArchivesSpace. Right now, we only use  notes to capture that type of
> information.
>
> Which fields are you using with your rights statements?
>
> All my best,
>
> Mark
>
>
> ------------------------------
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
> Anderson, Freya N (EED) <freya.anderson at alaska.gov>
> *Sent:* Tuesday, May 14, 2019 8:17 PM
> *To:* Archivesspace Users Group
> *Subject:* [Archivesspace_Users_Group] Rights Statement on public user
> interface
>
>
> Hello all,
>
>
>
> It was recently pointed out to me by one of our team, as we rush to get
> content into ArchivesSpace, that the Rights Statement doesn?t show up on
> the public user interface.  We enter it in the Resource, mark every Publish
> box, and click Publish All at the end.  Everything looks fine at the staff
> end, but no rights statement appears for the public.  Is this the way it?s
> supposed to work?  Is there anything we can do so the right statement shows
> up, other than adding it in the Notes?
>
>
>
> We?re using LibraryHost to host our instance.
>
>
>
> Thanks!
>
> Freya
>
>
>
> [image: cid:image001.png at 01D507DF.8CCD64B0]
>
> Freya Anderson
>
> *Head, Information Services  *
>
> *Acting Head, Historical Collections*
>
> phone: 907.465.1315
>
>
>
> Andrew P. Kashevaroff Building
>
> *Mail:* PO Box 110571, Juneau, AK 99811
>
> *Visit:* 395 Whittier St., Juneau, AK 99801
>
>
>
> email <freya.anderson at alaska.gov> | web
> <https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flibrary.alaska.gov%2F&data=02%7C01%7Cmark.custer%40yale.edu%7C9995d0a848f049d8428408d6d8caad6c%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636934762377844252&sdata=hUlnyA1RfmUYxxJyQ2SgZlQmS3B96zqYYmJHBqB%2BIds%3D&reserved=0>
> |  sign up for event notifications
> <https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.state.ak.us%2Fmailman%2Flistinfo%2Fat-apk-and-sjm&data=02%7C01%7Cmark.custer%40yale.edu%7C9995d0a848f049d8428408d6d8caad6c%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636934762377854261&sdata=UMb56zC%2FonMsuJ0FNV9dDoBA1oeoq8wJwDDKdsHxlCo%3D&reserved=0> |
> The Information Center for Government
> <https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flibrary.alaska.gov%2Fis%2F&data=02%7C01%7Cmark.custer%40yale.edu%7C9995d0a848f049d8428408d6d8caad6c%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636934762377854261&sdata=%2B8QyAazSkUS7T%2BG0eDc1b4Pt1Pjyvc9TtrJU1hwgOHA%3D&reserved=0>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
413 585 2981
mcallahan at smith.edu

Pronouns: she/her/hers

Smith College Special Collections is now housed at Young Library
<https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>.
Learn more about renovations to Neilson Library here
<https://www.smith.edu/libraries/about/new-neilson>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190520/6cd9f94e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 16891 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190520/6cd9f94e/attachment.png>

From blake.carver at lyrasis.org  Mon May 20 15:40:56 2019
From: blake.carver at lyrasis.org (Blake Carver)
Date: Mon, 20 May 2019 19:40:56 +0000
Subject: [Archivesspace_Users_Group] Importing from Archon: Recommended
 location for Digital Objects source files?
In-Reply-To: <SN6PR06MB63685BF0A2FE971E64E9BCABEF060@SN6PR06MB6368.namprd06.prod.outlook.com>
References: <SN6PR06MB63685BF0A2FE971E64E9BCABEF060@SN6PR06MB6368.namprd06.prod.outlook.com>
Message-ID: <DM5PR22MB08111C67CE8C54E4B99328A39F060@DM5PR22MB0811.namprd22.prod.outlook.com>

>> Is there a recommended location to store digital object files?

If you want people to be able to see them, then any publicly available server. ArchivesSpace just links out to the files on another server.

>> Can ArchivesSpace serve static files?

Nope.

>> If this is not recommended, then I?m assuming I can just put the digital object files on some other web server that I control?



Yep. If you don't know the URL before you run the migration it can be updated directly in the DB later.





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190520/070b0715/attachment.html>

From bob.swanson at uconn.edu  Tue May 21 09:59:03 2019
From: bob.swanson at uconn.edu (Swanson, Bob)
Date: Tue, 21 May 2019 13:59:03 +0000
Subject: [Archivesspace_Users_Group] Help with robots.txt
Message-ID: <BN7PR05MB43544303567E729C4FC97407E1070@BN7PR05MB4354.namprd05.prod.outlook.com>

Please forgive me if this is posted twice, I sent the following yesterday before I submitted the "acceptance Email" to the ArchivesSpace Users Group.  I don't see where it was posted on the board (am I doing this correctly?).

So far as I can tell, this is how I'm supposed to ask questions regarding ArchivesSpace.
Please forgive and correct me if I'm going about this incorrectly.

I am new to ArchivesSpace, Ruby, JBOD and web development, so I'm pretty dumb.

The PUI Pre-Launch checklist advises creating and updating robots.txt,
So we would like to set up a robots.txt file to control what crawlers can access when they crawl our ArvhivesSpace site https://archivessearch.lib.uconn.edu/.
I understand that robots.txt is supposed to go in the web root directory of the website.
In a normal apache configuration that's simple enough.

But,
We are serving ArchivesSpace via HTTPS.

a)       All Port 80 traffic is redirected to Port 443.

b)      443 traffic is proxied to 8081 (for the public interface) per the ArchivesSpace documentation.
  RequestHeader set X-Forwarded-Proto "https"
  ProxyPreserveHost On
  ProxyPass / http://localhost:8081/ retry=1 acquire=3000 timeout=600 Keepalive=on
  ProxyPassReverse / http://localhost:8081/
So, my web root directory (var/www/html) is empty (save some garbage left over from when I was testing).

I've read the documentation on www.robotstxt.org<http://www.robotstxt.org> but I can't find anything that pertains to my situation.
I have to imagine that most ArchivesSpace sites are now https and use robots.txt, so this should be a somewhat a somewhat standard implementation.

I don not find much information on the Users Group site pertaining to this,
I find reference to plans for this being implemented at the web server level back in 2016,
But nothing beyond that.
http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2016-August/003916.html

A search of the ArchivesSpace Technical Documentation for "robots" comes up empty as well.

Can you please direct me to any documentation that may exist on setting up a robots.txt file in a proxied HTTPS instance of ArchviceSpace?
Thank you, and please tolerate my naivety.



Bob Swanson
UConn Libraries
860-486-5260 - Office
860-617-1188 - Mobile

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190521/490d1b23/attachment.html>

From npwb2 at cam.ac.uk  Tue May 21 10:10:51 2019
From: npwb2 at cam.ac.uk (Nick Butler)
Date: Tue, 21 May 2019 14:10:51 +0000
Subject: [Archivesspace_Users_Group] Plugin problems: want the Notes section
	to default to open
Message-ID: <2329bb709747e7653fc2af9be42e985a55c2b0e3.camel@cam.ac.uk>

Hi all,

We're trying to write a plugin to default the Notes section of the new and edit resources pages to being open (i.e. as if the "Add Note" button had been clicked automatically when the page loaded).

I've got a layout_head.html.erb file which loads the appropriate js file in the correct page, my difficulty just comes from getting the button to click without creating errors. Here are the contents of my js file:

$(function () {
  var click_the_button = function () {
    var button = document.querySelector('.btn.btn-sm.btn-default.pull-right.add-note');
    button.click();
  };
  click_the_button();
});

When the page loads I get the error messages seen in my attached screenshot. I've also tried requiring notes.crud.js and simply running the createTopLevelNote function, but this gives precisely the same error messages. Note that the URL for creating a new resource is https://arcspace-dev.lib.cam.ac.uk/staff/resources/new, but when the error messages appear this changes to https://arcspace-dev.lib.cam.ac.uk/staff/resources.

As a test I've changed the click_the_button function to perform another task instead:

var click_the_button = function () {
    var button = document.querySelector('.btn.btn-sm.btn-default.pull-right.add-note');
   button.style.backgroundColor = 'green';
  };

This works exactly as expected, changing the button colour to green. No error messages appear and the URL stays as expected.

I haven't found any other plugins that do something like this (and I know very little Javascript!) so I'm at a loss here. Any advice or links to relevant documentation would be greatly appreciated.

Many thanks,
Nick

--

Nick Butler
Software Developer
Digital Services
Cambridge University Library
West Road
Cambridge CB3 9DR, UK

npwb2 at cam.ac.uk<mailto:npwb2 at cam.ac.uk>

Internal tel: 33067
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190521/1e7351ce/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2019-05-21 15-04-26.png
Type: image/png
Size: 229245 bytes
Desc: Screenshot from 2019-05-21 15-04-26.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190521/1e7351ce/attachment.png>

From blake.carver at lyrasis.org  Tue May 21 10:59:19 2019
From: blake.carver at lyrasis.org (Blake Carver)
Date: Tue, 21 May 2019 14:59:19 +0000
Subject: [Archivesspace_Users_Group] Help with robots.txt
In-Reply-To: <BN7PR05MB43544303567E729C4FC97407E1070@BN7PR05MB4354.namprd05.prod.outlook.com>
References: <BN7PR05MB43544303567E729C4FC97407E1070@BN7PR05MB4354.namprd05.prod.outlook.com>
Message-ID: <DM5PR22MB08110F810E6EBA2E32B52C8A9F070@DM5PR22MB0811.namprd22.prod.outlook.com>

I'll be sure to add this one to the docs, so let me know if this works!

I think you'll need to do an alias, something like this for Apache:

<Location "/robots.txt">
 SetHandler None
 Require all granted
</Location>
Alias /robots.txt /var/www/robots.txt

nginx, more like this:
  location /robots.txt {
    alias /var/www/robots.txt;
  }


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Swanson, Bob <bob.swanson at uconn.edu>
Sent: Tuesday, May 21, 2019 9:59 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Help with robots.txt


Please forgive me if this is posted twice, I sent the following yesterday before I submitted the ?acceptance Email? to the ArchivesSpace Users Group.  I don?t see where it was posted on the board (am I doing this correctly?).



So far as I can tell, this is how I?m supposed to ask questions regarding ArchivesSpace.

Please forgive and correct me if I?m going about this incorrectly.



I am new to ArchivesSpace, Ruby, JBOD and web development, so I?m pretty dumb.



The PUI Pre-Launch checklist advises creating and updating robots.txt,

So we would like to set up a robots.txt file to control what crawlers can access when they crawl our ArvhivesSpace site https://archivessearch.lib.uconn.edu/.

I understand that robots.txt is supposed to go in the web root directory of the website.

In a normal apache configuration that?s simple enough.



But,

We are serving ArchivesSpace via HTTPS.

a)       All Port 80 traffic is redirected to Port 443.

b)      443 traffic is proxied to 8081 (for the public interface) per the ArchivesSpace documentation.

  RequestHeader set X-Forwarded-Proto "https"

  ProxyPreserveHost On

  ProxyPass / http://localhost:8081/ retry=1 acquire=3000 timeout=600 Keepalive=on

  ProxyPassReverse / http://localhost:8081/

So, my web root directory (var/www/html) is empty (save some garbage left over from when I was testing).



I?ve read the documentation on www.robotstxt.org<http://www.robotstxt.org> but I can?t find anything that pertains to my situation.

I have to imagine that most ArchivesSpace sites are now https and use robots.txt, so this should be a somewhat a somewhat standard implementation.



I don not find much information on the Users Group site pertaining to this,

I find reference to plans for this being implemented at the web server level back in 2016,

But nothing beyond that.

http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2016-August/003916.html



A search of the ArchivesSpace Technical Documentation for ?robots? comes up empty as well.



Can you please direct me to any documentation that may exist on setting up a robots.txt file in a proxied HTTPS instance of ArchviceSpace?

Thank you, and please tolerate my naivety.







Bob Swanson

UConn Libraries

860-486-5260 ? Office

860-617-1188 - Mobile


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190521/87315bc1/attachment.html>

From andrew.morrison at bodleian.ox.ac.uk  Tue May 21 11:37:40 2019
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Tue, 21 May 2019 15:37:40 +0000
Subject: [Archivesspace_Users_Group] Help with robots.txt
In-Reply-To: <BN7PR05MB43544303567E729C4FC97407E1070@BN7PR05MB4354.namprd05.prod.outlook.com>
References: <BN7PR05MB43544303567E729C4FC97407E1070@BN7PR05MB4354.namprd05.prod.outlook.com>
Message-ID: <1558453059.8626.92.camel@bodleian.ox.ac.uk>

Hello,

If you put a robots.txt file in the config folder of your ArchivesSpace system, it will be served by a request for /robots.txt, after the next restart. I cannot remember where I read that, and cannot find it now, but can confirm it works, since I believe 2.6.0.

Regards,

Andrew Morrison
Software Engineer
Bodleian Digital Library Systems and Services
https://www.bodleian.ox.ac.uk/bdlss


On Tue, 2019-05-21 at 13:59 +0000, Swanson, Bob wrote:
Please forgive me if this is posted twice, I sent the following yesterday before I submitted the ?acceptance Email? to the ArchivesSpace Users Group.  I don?t see where it was posted on the board (am I doing this correctly?).

So far as I can tell, this is how I?m supposed to ask questions regarding ArchivesSpace.
Please forgive and correct me if I?m going about this incorrectly.

I am new to ArchivesSpace, Ruby, JBOD and web development, so I?m pretty dumb.

The PUI Pre-Launch checklist advises creating and updating robots.txt,
So we would like to set up a robots.txt file to control what crawlers can access when they crawl our ArvhivesSpace site https://archivessearch.lib.uconn.edu/.
I understand that robots.txt is supposed to go in the web root directory of the website.
In a normal apache configuration that?s simple enough.

But,
We are serving ArchivesSpace via HTTPS.

a)       All Port 80 traffic is redirected to Port 443.

b)      443 traffic is proxied to 8081 (for the public interface) per the ArchivesSpace documentation.
  RequestHeader set X-Forwarded-Proto "https"
  ProxyPreserveHost On
  ProxyPass / http://localhost:8081/ retry=1 acquire=3000 timeout=600 Keepalive=on
  ProxyPassReverse / http://localhost:8081/
So, my web root directory (var/www/html) is empty (save some garbage left over from when I was testing).

I?ve read the documentation on www.robotstxt.org<http://www.robotstxt.org> but I can?t find anything that pertains to my situation.
I have to imagine that most ArchivesSpace sites are now https and use robots.txt, so this should be a somewhat a somewhat standard implementation.

I don not find much information on the Users Group site pertaining to this,
I find reference to plans for this being implemented at the web server level back in 2016,
But nothing beyond that.
http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2016-August/003916.html

A search of the ArchivesSpace Technical Documentation for ?robots? comes up empty as well.

Can you please direct me to any documentation that may exist on setting up a robots.txt file in a proxied HTTPS instance of ArchviceSpace?
Thank you, and please tolerate my naivety.



Bob Swanson
UConn Libraries
860-486-5260 ? Office
860-617-1188 - Mobile


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190521/46d390ee/attachment.html>

From blake.carver at lyrasis.org  Tue May 21 11:54:24 2019
From: blake.carver at lyrasis.org (Blake Carver)
Date: Tue, 21 May 2019 15:54:24 +0000
Subject: [Archivesspace_Users_Group] Help with robots.txt
In-Reply-To: <1558453059.8626.92.camel@bodleian.ox.ac.uk>
References: <BN7PR05MB43544303567E729C4FC97407E1070@BN7PR05MB4354.namprd05.prod.outlook.com>,
 <1558453059.8626.92.camel@bodleian.ox.ac.uk>
Message-ID: <DM5PR22MB081182789E81039BB315E6429F070@DM5PR22MB0811.namprd22.prod.outlook.com>

Look at that!
https://github.com/archivesspace/archivesspace/commit/0bfb91e7f27a18b4cb6e0a27527be1041c877237#diff-f266d24dcc6fcbe9020ee4f31cf538f7
Yep, sure looks like that'll work as well.
So it seems like the easiest way to serve up a robots file is just throw it in your config directory.
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Andrew Morrison <andrew.morrison at bodleian.ox.ac.uk>
Sent: Tuesday, May 21, 2019 11:37 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Help with robots.txt

Hello,

If you put a robots.txt file in the config folder of your ArchivesSpace system, it will be served by a request for /robots.txt, after the next restart. I cannot remember where I read that, and cannot find it now, but can confirm it works, since I believe 2.6.0.

Regards,

Andrew Morrison
Software Engineer
Bodleian Digital Library Systems and Services
https://www.bodleian.ox.ac.uk/bdlss


On Tue, 2019-05-21 at 13:59 +0000, Swanson, Bob wrote:

Please forgive me if this is posted twice, I sent the following yesterday before I submitted the ?acceptance Email? to the ArchivesSpace Users Group.  I don?t see where it was posted on the board (am I doing this correctly?).



So far as I can tell, this is how I?m supposed to ask questions regarding ArchivesSpace.

Please forgive and correct me if I?m going about this incorrectly.



I am new to ArchivesSpace, Ruby, JBOD and web development, so I?m pretty dumb.



The PUI Pre-Launch checklist advises creating and updating robots.txt,

So we would like to set up a robots.txt file to control what crawlers can access when they crawl our ArvhivesSpace site https://archivessearch.lib.uconn.edu/.

I understand that robots.txt is supposed to go in the web root directory of the website.

In a normal apache configuration that?s simple enough.



But,

We are serving ArchivesSpace via HTTPS.

a)       All Port 80 traffic is redirected to Port 443.

b)      443 traffic is proxied to 8081 (for the public interface) per the ArchivesSpace documentation.

  RequestHeader set X-Forwarded-Proto "https"

  ProxyPreserveHost On

  ProxyPass / http://localhost:8081/ retry=1 acquire=3000 timeout=600 Keepalive=on

  ProxyPassReverse / http://localhost:8081/

So, my web root directory (var/www/html) is empty (save some garbage left over from when I was testing).



I?ve read the documentation on www.robotstxt.org<http://www.robotstxt.org> but I can?t find anything that pertains to my situation.

I have to imagine that most ArchivesSpace sites are now https and use robots.txt, so this should be a somewhat a somewhat standard implementation.



I don not find much information on the Users Group site pertaining to this,

I find reference to plans for this being implemented at the web server level back in 2016,

But nothing beyond that.

http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2016-August/003916.html



A search of the ArchivesSpace Technical Documentation for ?robots? comes up empty as well.



Can you please direct me to any documentation that may exist on setting up a robots.txt file in a proxied HTTPS instance of ArchviceSpace?

Thank you, and please tolerate my naivety.







Bob Swanson

UConn Libraries

860-486-5260 ? Office

860-617-1188 - Mobile



_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190521/5d08ab12/attachment-0001.html>

From bob.swanson at uconn.edu  Tue May 21 12:08:33 2019
From: bob.swanson at uconn.edu (Swanson, Bob)
Date: Tue, 21 May 2019 16:08:33 +0000
Subject: [Archivesspace_Users_Group] Help with robots.txt
In-Reply-To: <DM5PR22MB081182789E81039BB315E6429F070@DM5PR22MB0811.namprd22.prod.outlook.com>
References: <BN7PR05MB43544303567E729C4FC97407E1070@BN7PR05MB4354.namprd05.prod.outlook.com>,
 <1558453059.8626.92.camel@bodleian.ox.ac.uk>
 <DM5PR22MB081182789E81039BB315E6429F070@DM5PR22MB0811.namprd22.prod.outlook.com>
Message-ID: <BN7PR05MB43541D7601F1A87BB38EF9B1E1070@BN7PR05MB4354.namprd05.prod.outlook.com>

Thank you so much!
I will comply.

Bob Swanson
UConn Libraries
860-486-5260 - Office
860-617-1188 - Mobile

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Blake Carver
Sent: Tuesday, May 21, 2019 11:54 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Help with robots.txt

Look at that!
https://github.com/archivesspace/archivesspace/commit/0bfb91e7f27a18b4cb6e0a27527be1041c877237#diff-f266d24dcc6fcbe9020ee4f31cf538f7<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farchivesspace%2Farchivesspace%2Fcommit%2F0bfb91e7f27a18b4cb6e0a27527be1041c877237%23diff-f266d24dcc6fcbe9020ee4f31cf538f7&data=02%7C01%7Cbob.swanson%40uconn.edu%7C60149aa8361344aef23008d6de049c5c%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636940508729129268&sdata=MJ9vLNVGxdo0LQ53cO40qAmukhSclOrZv8yFwiO9WKk%3D&reserved=0>
Yep, sure looks like that'll work as well.
So it seems like the easiest way to serve up a robots file is just throw it in your config directory.
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Andrew Morrison <andrew.morrison at bodleian.ox.ac.uk<mailto:andrew.morrison at bodleian.ox.ac.uk>>
Sent: Tuesday, May 21, 2019 11:37 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Help with robots.txt

Hello,

If you put a robots.txt file in the config folder of your ArchivesSpace system, it will be served by a request for /robots.txt, after the next restart. I cannot remember where I read that, and cannot find it now, but can confirm it works, since I believe 2.6.0.

Regards,

Andrew Morrison
Software Engineer
Bodleian Digital Library Systems and Services
https://www.bodleian.ox.ac.uk/bdlss<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bodleian.ox.ac.uk%2Fbdlss&data=02%7C01%7Cbob.swanson%40uconn.edu%7C60149aa8361344aef23008d6de049c5c%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636940508729129268&sdata=hHEwf14Gs%2Bm5sfD8Lp68S7wN0n9pL1NbK2nbkO90pWg%3D&reserved=0>


On Tue, 2019-05-21 at 13:59 +0000, Swanson, Bob wrote:

Please forgive me if this is posted twice, I sent the following yesterday before I submitted the "acceptance Email" to the ArchivesSpace Users Group.  I don't see where it was posted on the board (am I doing this correctly?).



So far as I can tell, this is how I'm supposed to ask questions regarding ArchivesSpace.

Please forgive and correct me if I'm going about this incorrectly.



I am new to ArchivesSpace, Ruby, JBOD and web development, so I'm pretty dumb.



The PUI Pre-Launch checklist advises creating and updating robots.txt,

So we would like to set up a robots.txt file to control what crawlers can access when they crawl our ArvhivesSpace site https://archivessearch.lib.uconn.edu/<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivessearch.lib.uconn.edu%2F&data=02%7C01%7Cbob.swanson%40uconn.edu%7C60149aa8361344aef23008d6de049c5c%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636940508729139257&sdata=g1gJFYqoFtX5S5EImTzssbksDfi328kw%2B%2F1H6TigIXk%3D&reserved=0>.

I understand that robots.txt is supposed to go in the web root directory of the website.

In a normal apache configuration that's simple enough.



But,

We are serving ArchivesSpace via HTTPS.

a)       All Port 80 traffic is redirected to Port 443.

b)      443 traffic is proxied to 8081 (for the public interface) per the ArchivesSpace documentation.

  RequestHeader set X-Forwarded-Proto "https"

  ProxyPreserveHost On

  ProxyPass / http://localhost:8081/ retry=1 acquire=3000 timeout=600 Keepalive=on

  ProxyPassReverse / http://localhost:8081/

So, my web root directory (var/www/html) is empty (save some garbage left over from when I was testing).



I've read the documentation on www.robotstxt.org<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.robotstxt.org&data=02%7C01%7Cbob.swanson%40uconn.edu%7C60149aa8361344aef23008d6de049c5c%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636940508729139257&sdata=BxRVDxhr3LQAM%2FX2GD58d%2Bt%2BUoNsnoJPYfWRk6UtH9c%3D&reserved=0> but I can't find anything that pertains to my situation.

I have to imagine that most ArchivesSpace sites are now https and use robots.txt, so this should be a somewhat a somewhat standard implementation.



I don not find much information on the Users Group site pertaining to this,

I find reference to plans for this being implemented at the web server level back in 2016,

But nothing beyond that.

http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2016-August/003916.html<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fpipermail%2Farchivesspace_users_group%2F2016-August%2F003916.html&data=02%7C01%7Cbob.swanson%40uconn.edu%7C60149aa8361344aef23008d6de049c5c%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636940508729149251&sdata=RaQCHvtRY6H7Ned5F0ULjrwYo1yG6E7lyi%2FvHgrGUSI%3D&reserved=0>



A search of the ArchivesSpace Technical Documentation for "robots" comes up empty as well.



Can you please direct me to any documentation that may exist on setting up a robots.txt file in a proxied HTTPS instance of ArchviceSpace?

Thank you, and please tolerate my naivety.







Bob Swanson

UConn Libraries

860-486-5260 - Office

860-617-1188 - Mobile



_______________________________________________

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cbob.swanson%40uconn.edu%7C60149aa8361344aef23008d6de049c5c%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636940508729149251&sdata=BUFnf%2FKkS6d%2BBrLDT1S1X5S09kuEtmG%2B3OWFlOk3ob4%3D&reserved=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190521/3787b5e6/attachment.html>

From andrew.morrison at bodleian.ox.ac.uk  Tue May 21 14:26:58 2019
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Tue, 21 May 2019 18:26:58 +0000
Subject: [Archivesspace_Users_Group] Help with robots.txt
In-Reply-To: <BN7PR05MB43541D7601F1A87BB38EF9B1E1070@BN7PR05MB4354.namprd05.prod.outlook.com>
References: <BN7PR05MB43544303567E729C4FC97407E1070@BN7PR05MB4354.namprd05.prod.outlook.com>,
 <1558453059.8626.92.camel@bodleian.ox.ac.uk>
 <DM5PR22MB081182789E81039BB315E6429F070@DM5PR22MB0811.namprd22.prod.outlook.com>,
 <BN7PR05MB43541D7601F1A87BB38EF9B1E1070@BN7PR05MB4354.namprd05.prod.outlook.com>
Message-ID: <LNXP265MB02365194254E425439C7C066E5070@LNXP265MB0236.GBRP265.PROD.OUTLOOK.COM>

Small correction: adding robots.txt to the config folder has worked since 2.2.2, not 2.6.0.


I think documentation of this feature was lost because it was added around the same time that the tech-docs repository was being created.


Andrew.

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Swanson, Bob <bob.swanson at uconn.edu>
Sent: 21 May 2019 17:08:33
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Help with robots.txt


Thank you so much!

I will comply.



Bob Swanson

UConn Libraries

860-486-5260 ? Office

860-617-1188 - Mobile



From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Blake Carver
Sent: Tuesday, May 21, 2019 11:54 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Help with robots.txt



Look at that!

https://github.com/archivesspace/archivesspace/commit/0bfb91e7f27a18b4cb6e0a27527be1041c877237#diff-f266d24dcc6fcbe9020ee4f31cf538f7<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farchivesspace%2Farchivesspace%2Fcommit%2F0bfb91e7f27a18b4cb6e0a27527be1041c877237%23diff-f266d24dcc6fcbe9020ee4f31cf538f7&data=02%7C01%7Cbob.swanson%40uconn.edu%7C60149aa8361344aef23008d6de049c5c%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636940508729129268&sdata=MJ9vLNVGxdo0LQ53cO40qAmukhSclOrZv8yFwiO9WKk%3D&reserved=0>

Yep, sure looks like that'll work as well.

So it seems like the easiest way to serve up a robots file is just throw it in your config directory.

________________________________

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Andrew Morrison <andrew.morrison at bodleian.ox.ac.uk<mailto:andrew.morrison at bodleian.ox.ac.uk>>
Sent: Tuesday, May 21, 2019 11:37 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Help with robots.txt



Hello,



If you put a robots.txt file in the config folder of your ArchivesSpace system, it will be served by a request for /robots.txt, after the next restart. I cannot remember where I read that, and cannot find it now, but can confirm it works, since I believe 2.6.0.



Regards,



Andrew Morrison

Software Engineer

Bodleian Digital Library Systems and Services

https://www.bodleian.ox.ac.uk/bdlss<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bodleian.ox.ac.uk%2Fbdlss&data=02%7C01%7Cbob.swanson%40uconn.edu%7C60149aa8361344aef23008d6de049c5c%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636940508729129268&sdata=hHEwf14Gs%2Bm5sfD8Lp68S7wN0n9pL1NbK2nbkO90pWg%3D&reserved=0>





On Tue, 2019-05-21 at 13:59 +0000, Swanson, Bob wrote:

Please forgive me if this is posted twice, I sent the following yesterday before I submitted the ?acceptance Email? to the ArchivesSpace Users Group.  I don?t see where it was posted on the board (am I doing this correctly?).



So far as I can tell, this is how I?m supposed to ask questions regarding ArchivesSpace.

Please forgive and correct me if I?m going about this incorrectly.



I am new to ArchivesSpace, Ruby, JBOD and web development, so I?m pretty dumb.



The PUI Pre-Launch checklist advises creating and updating robots.txt,

So we would like to set up a robots.txt file to control what crawlers can access when they crawl our ArvhivesSpace site https://archivessearch.lib.uconn.edu/<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivessearch.lib.uconn.edu%2F&data=02%7C01%7Cbob.swanson%40uconn.edu%7C60149aa8361344aef23008d6de049c5c%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636940508729139257&sdata=g1gJFYqoFtX5S5EImTzssbksDfi328kw%2B%2F1H6TigIXk%3D&reserved=0>.

I understand that robots.txt is supposed to go in the web root directory of the website.

In a normal apache configuration that?s simple enough.



But,

We are serving ArchivesSpace via HTTPS.

a)       All Port 80 traffic is redirected to Port 443.

b)      443 traffic is proxied to 8081 (for the public interface) per the ArchivesSpace documentation.

  RequestHeader set X-Forwarded-Proto "https"

  ProxyPreserveHost On

  ProxyPass / http://localhost:8081/ retry=1 acquire=3000 timeout=600 Keepalive=on

  ProxyPassReverse / http://localhost:8081/

So, my web root directory (var/www/html) is empty (save some garbage left over from when I was testing).



I?ve read the documentation on www.robotstxt.org<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.robotstxt.org&data=02%7C01%7Cbob.swanson%40uconn.edu%7C60149aa8361344aef23008d6de049c5c%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636940508729139257&sdata=BxRVDxhr3LQAM%2FX2GD58d%2Bt%2BUoNsnoJPYfWRk6UtH9c%3D&reserved=0> but I can?t find anything that pertains to my situation.

I have to imagine that most ArchivesSpace sites are now https and use robots.txt, so this should be a somewhat a somewhat standard implementation.



I don not find much information on the Users Group site pertaining to this,

I find reference to plans for this being implemented at the web server level back in 2016,

But nothing beyond that.

http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2016-August/003916.html<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fpipermail%2Farchivesspace_users_group%2F2016-August%2F003916.html&data=02%7C01%7Cbob.swanson%40uconn.edu%7C60149aa8361344aef23008d6de049c5c%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636940508729149251&sdata=RaQCHvtRY6H7Ned5F0ULjrwYo1yG6E7lyi%2FvHgrGUSI%3D&reserved=0>



A search of the ArchivesSpace Technical Documentation for ?robots? comes up empty as well.



Can you please direct me to any documentation that may exist on setting up a robots.txt file in a proxied HTTPS instance of ArchviceSpace?

Thank you, and please tolerate my naivety.







Bob Swanson

UConn Libraries

860-486-5260 ? Office

860-617-1188 - Mobile



_______________________________________________

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cbob.swanson%40uconn.edu%7C60149aa8361344aef23008d6de049c5c%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636940508729149251&sdata=BUFnf%2FKkS6d%2BBrLDT1S1X5S09kuEtmG%2B3OWFlOk3ob4%3D&reserved=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190521/b4ecd8c1/attachment.html>

From PGalligan at rockarch.org  Tue May 21 15:16:43 2019
From: PGalligan at rockarch.org (Galligan, Patrick)
Date: Tue, 21 May 2019 19:16:43 +0000
Subject: [Archivesspace_Users_Group] TAC Integrations Introduction
Message-ID: <545B29C7-E2CE-411E-A5FB-4EE8B2B3C8ED@rockarch.org>

Hello,


I?m writing on behalf of the ArchivesSpace Technical Advisory Council?s Integrations sub-team. If you?re not familiar with our work, the Integrations subteam supports the ArchivesSpace community by taking a transparent approach to documenting and facilitating the integration of systems with the ArchivesSpace application. Some of our activities include:

  *   Tracking current integrations and communicating their status with the larger community
  *   Creating resources that assist members of the community with their integration work
  *   Act as liaisons between integration developers, the AS program team, and the community
  *   Act as general resources for those working on integrations


We?ve recently given our documentation a refresh -- please give it a look! You can read a little more about what we consider integrations on our ?What Are Integrations?<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/102471723/What+are+Integrations>? page, and we have a few examples of existing integrations on our team?s ?Integrations<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/17137746/Integrations>? page. We also have documentation about ?How<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/102471870/How+to+Integrate+with+ArchivesSpace>? and ?Why<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/102471809/Why+Integrate+with+ArchivesSpace>? to integrate with ArchivesSpace if you?re thinking about or are currently working on a systems integration.


We?re reaching out today because we saw an opportunity to better support integrations work by reaching out to communities that might not already know about the work we do. We?re actively seeking more information about any past or current integrations work so that we can better share it out with others. If you?re working on an integration, we?d love to hear about it! Please either email us at as_tac_integrations at lyralists.lyrasis.org<mailto:as_tac_integrations at lyralists.lyrasis.org> or fill out our ArchivesSpace Integrations Form<https://docs.google.com/forms/d/e/1FAIpQLScrz3ZpZRIz6qYf7ZV4plV_6eb8bc3lfPvWO9FquhRKmiqepQ/viewform>.


We?d really like to know what you?re working on or thinking about working on, and want to make sure as many people know of our existence as possible. We?re here to act as a resource and answer any questions you might have about how to go about integrating with ArchivesSpace. We may not always be able to answer your deepest technological questions, but we can definitely point you in the right direction.


Best,

Patrick Galligan


Oh behalf of Integrations sub-team

Jared Campbell

Megan Firestone

Edgar Garcia

Maggie Hughes

Dallas Pillen

Trevor Thornton

Gregory Wiedeman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190521/f30b40da/attachment.html>

From benn.joseph at northwestern.edu  Tue May 21 17:22:17 2019
From: benn.joseph at northwestern.edu (Benn Joseph)
Date: Tue, 21 May 2019 21:22:17 +0000
Subject: [Archivesspace_Users_Group] merge Top Container functionality
Message-ID: <fb524742b3b943c0b084247374b29c42@evcspmbx04.ads.northwestern.edu>

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

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

Thanks!
--Benn

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



-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Tang, Lydia
Sent: Wednesday, January 16, 2019 12:18 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input

I second the ability to merge containers!  ?
Lydia

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Valerie Addonizio <vaddoniz at jhu.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Wednesday, January 16, 2019 at 1:17 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input

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

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

Dear ArchivesSpace community:

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

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

 ? Multi-field top container indicators
     Some commenters wondered if the multiple fields were to accommodate child containers. To clarify, the suggestion was to facilitate parsing top container identifiers.  As a few commenters have surmised, this is to cope with legacy numbers.  These are especially common on medium-rare materials.
     One suggestion was to use a sort algorithm that would obviate the need for separated fields for data. However, because there would be is more than one algorithm necessary over the installation, such a solution would require an added field to identify the algorithm and probably a third field retain a value derived by the algorithm to be sorted alphanumerically. Thus, the direct 3-field solution seems simpler. (A 4-field suggestion was mooted in the committee as potentially more useful communally.) It does occur to me that there just might not be enough really old, really big repositories with lots of legacy identifiers in the ArchivesSpace community for the parsing of legacy numbers to be a common problem. I appreciate the recognition that a plug-in might be needed instead, but it would be worth hearing from any repositories with similar issues.

 ? Container and location profiles by repository
       We were envisioning a one-to-one profile-to-repository scenario. Due to the ArchivesSpace staff user interface requirement that one identify only a single repository at login, it is extremely easy for users to forget the impact they might have beyond their repository if they change or delete a shared record.  We have already experienced mistaken mergers and deletions of agents due to the design of AS staff user interface that does not allow one to see where the record may be linked beyond their repository.  For this reason, it is wise to be able to limit changes and deletions of location profiles and container profiles impact to the same chosen repository.

 ? Inactive
     As Maureen wisely intuited, inactive locations are necessary to recording a complete location history.  However, there are additional use cases. When a repository is renovating, for example (as is happening now at the Schlesinger Library) the shelves in a location may be inactive for a time and become active again when the building re-opens.  Other scenarios include water intrusion or other occasions when a smaller sub-set of shelves may have to become inactive until repairs are completed and tested before the shelving can again come into use. Because inactive locations are to be eliminated by default from search results, we can prevent them from overwhelming staff members? search results or sending staff to unusable locations.

 ? Notes in containers and locations
     Notes are for dedicated shelving or rehousing issues.  Notes on containers may contain things like ?Label falling off? ?Acidic-needs replacing? ?Acid box replaced with acid-free box 2017-06-08? ?Not on shelf 2015-10-10?.  Notes on locations may contain things like ?only use as last resort?overhead drip pan makes retrieval difficult? ?reserved for outgoing transfers until 2019-01-01?.  In locations especially, we would expect the reason for a location becoming inactive might be noted.  ?Made inactive because next to heating duct?do not reactivate?.

 ? Bibliographic record IDs in containers
     This data would allow for more sustainable interoperability between systems and more flexibility in workflows.
     Especially with medium-rare materials, the physical item?s location might need to be recorded before description is finalized, and if the description is to be created in foreign system and ingested to ArchivesSpace, hooking up the container and location will be problematic.  In this scenario, a resource with initial description in a bibliographic system could be placed on an archives? shelf, and the description, once completed in the ILS, could be ingested via MARC XML ingest for example.  After the resource is ingested, the ILS bibliographic record number could be searched in the containers to link the container to the resource.
     When an ILS system migrates, it is unlikely that the migration would maintain obsolte holding or item system numbers, but it is common to migrate with obsolete bibliographic system record numbers embedded into the new system.  Should there be a need to re-migrate holdings or items from ArchivesSpace to a new ILS, bibliographic record numbers would ensure continuity.

Thanks for reading!

Kate






From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Maureen Callahan
Sent: Monday, December 17, 2018 2:09 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input

A million thanks to folks from Harvard for showing leadership and investing to improve the experience of the software for all of us.

I was having pleasant flashbacks to my days at Yale working through the original specifications for the container management functionality -- what it all means, what it should do, how this will improve the experience for archivists and patrons, and how to abstract all of this work to more general archival and data management principles. It's such fun, hard work!

Generally speaking, it would be really helpful if user stories gave a better sense of what you want to accomplish instead of what you want to see on the screen. For some of this, I had a hard time understanding where you were coming from and I think it's possible that there are different ways of accomplishing what you've laid out. "As an W, I want to have X feature, so that Y behavior happens in Z way and lets me do my work in ABC fashion." I think that many of the goals behind this proposal are sound, but that perhaps there's too narrow an approach to solutions to meet these goals. Developers might find better ways to address the problems you've identified.

1. Hell YES there need to be easier ways to browse/sort/find locations!!!!

2. I agree that it would be useful to have the option to filter locations/container profiles by the repository they tend to belong to and that this should also be extensible so that it's easy to change this information after a move or administrative change. I sort of remember that folks at NYU talked about this as a possible outcome in the beginning of their location profile work, so it may be worth talking with them about the best way to think about it and any reasons they might have opted to not associate a repository with a location profile.

3. Lora did some nice work with search to make it possible to see the entire breadcrumb trail of where a search result comes from (the hierarchies of AOs within a resource). I'm thinking that perhaps you just want the same thing to happen when you look at the associated archival objects / accessions in a top container, rather than adding another column (resource) to the search result.

4. As someone who has had to do a lot of systems migrations that involved moving heterogenous data into more structured places, I get really nervous about a notes field for either the location or the top container. If there are common types of information that end up in this field, it may be worth considering adding more structured fields to either the location or the location profile or container or container profile so that it can be better managed, queried, and kept tidy & up-to-date. What's the scenario by which someone would actually look at this notes field? What do you want to go in there?

5. Soooooo tell me more about this inactive location idea. AFAIR, ArchivesSpace doesn't keep an audit trail of previous locations. What's the value of knowing that inactive locations exist when there aren't containers living in those locations and there's no way to see that those locations perviously held containers?

6. This may be implicit in your proposal, but it sounds like you want "repository" to be a multi-valued field in your location profiles and your container profiles. Paige boxes, for instance, will probably end up being associated with every repository.

7. I was initially a bit perplexed by the request to add additional fields for container indicators, but reading between the lines, my guess is that you want to be able to sort them properly in various circumstances.

If, for instance, you have boxes 2, 2a, and 3, you want to be able to make sure that when you sort by indicator, they appear in this order. That's a great goal! But I think that you might want to state this goal instead of stating one possible outcome.

I definitely DO NOT want a three-part container indicator because who knows what kind of crap people will put in those fields and they could potentially be a nightmare to clean up. Plus, it would have to account for every possible heterodox way that people design their container indicators -- or just default to Harvard's scheme, which... I mean, this is software for the whole community.

Instead, I would suggest making the requirement that you want for alphanumeric characters to sort properly and clever developers can come up with the best way to do this. That seems like a more elegant solution than changing the data model.

8. YES BIBIDs!!!! But my read is that a BIBID is a control number for intellectual description, not for holdings. I know that folks are currently putting BIBIDs in user-defined fields in the resource record, and it would be great for those to have a canonical spot to help with systems integrations. I would much rather see the addition of a BIBID to the resource record, which can then be displayed with the top container by the system if desired (although why?). There's already a field for the ILS holdings ID to go with the top container.

Thanks all,
Maureen


--
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
413 585 2981
mcallahan at smith.edu<mailto:mcallahan at smith.edu>

Pronouns: she/her/hers

Smith College Special Collections is now housed at Young Library<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.smith.edu_libraries_about_new-2Dneilson_wheres-2Dmy-2Dlibrary&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=bbRMI526TLbYRRGdpIJjhaQSNXcp3-xidB745mYa688&s=6_5o894RumU3UiMWDspYsi9hvlxzwybbDZhwqxoqzUk&e=>. Learn more about renovations to Neilson Library here<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.smith.edu_libraries_about_new-2Dneilson&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=bbRMI526TLbYRRGdpIJjhaQSNXcp3-xidB745mYa688&s=D7vktPydut0KZQpgPuTDeMfGLme5d9GNsfXHoWV7CRk&e=>.

On Mon, Dec 17, 2018 at 12:42 PM Rackley, Marilyn <marilyn_rackley at harvard.edu<mailto:marilyn_rackley at harvard.edu>> wrote:
Dear all,

Please remember to review the Harvard Library proposal for container management enhancements and submit feedback by Wednesday, December 19, 2018. See the email below for more information.

In case people are not able to access the attachment, the proposal can also be accessed through this link: https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-3Fid-3D14-2D6CFEAATfwYc1JZoAmCSD3CQVW7p3b3&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=bInpBUPKeV0QKr-JQH2j9yaDdfw8v580qBTSZmMBwx4&e=<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-3Fid-3D14-2D6CFEAATfwYc1JZoAmCSD3CQVW7p3b3&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=bbRMI526TLbYRRGdpIJjhaQSNXcp3-xidB745mYa688&s=1GjU8ktQ9bncQdhvdE2zi0a2fHSWL8NDj17jV9byJn8&e=>.

We really appreciate all the comments provided so far.

Best,
Marilyn

From: Rackley, Marilyn
Sent: Monday, December 3, 2018 9:36 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: Proposal for Container Management Enhancements - Call for Community Input

Dear ArchivesSpace Community,

The Harvard Library has been reviewing container and location management functionality in ArchivesSpace and we are proposing to make enhancements to this functionality that we would like to contribute to the core code.

With these enhancements, we hope to make finding, viewing, and updating information related to containers and locations in the staff interface more efficient and effective.

We have completed the draft proposal attached to this email and we are now asking for community review and feedback. The proposal includes the rationale for the changes, a list of database fields to be added, user stories describing the specific changes we are proposing, and mockups of the related updates to the staff interface. Please note that in the proposal, certain changes are designated as being a lower priority; it is possible that we may not be able to complete all the proposed changes at this time.

If you have questions or feedback, please email me at marilyn_rackley at harvard.edu<mailto:marilyn_rackley at harvard.edu> and/or Robin Wendler at robin_wendler at harvard.edu<mailto:robin_wendler at harvard.edu>. We will be accepting comments through Wednesday, December 19, 2018.

We look forward to receiving community input.

Best,
Marilyn

Marilyn Rackley
Aeon Project Manager and Digital Librarian Harvard Library | 617.496.4043 marilyn_rackley at harvard.edu<mailto:marilyn_rackley at harvard.edu>

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto: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=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=FB4KqB3TcRmkmN9zqyRn6s9tpjfpDzM3U9XYqkb3Ock&e=<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=bbRMI526TLbYRRGdpIJjhaQSNXcp3-xidB745mYa688&s=Ia_oQ7YT5R2fLTqMbss7oSChwO-HRtiNxwPbTe1RCRM&e=>



_______________________________________________
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=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=FB4KqB3TcRmkmN9zqyRn6s9tpjfpDzM3U9XYqkb3Ock&e=

From freya.anderson at alaska.gov  Tue May 21 18:13:36 2019
From: freya.anderson at alaska.gov (Anderson, Freya N (EED))
Date: Tue, 21 May 2019 22:13:36 +0000
Subject: [Archivesspace_Users_Group] Rights Statement on
	public	user	interface
In-Reply-To: <BN8PR08MB57770EE6BF985A9E82C16F738C060@BN8PR08MB5777.namprd08.prod.outlook.com>
References: <e5b560e847624671b994071aea6e5de8@SOAJNUEXCH01.soa.alaska.gov>
 <BN8PR08MB57770EE6BF985A9E82C16F738C060@BN8PR08MB5777.namprd08.prod.outlook.com>
Message-ID: <9b4d5bfbafe8464e884d3f90d697c583@SOAJNUEXCH01.soa.alaska.gov>

Thanks Mark and MC!

We were just including a notes field in the rights statement, along with the required type and start date, and rarely an end date.  We're starting now to include the information in notes fields, but because there was a publish checkbox in the Rights Statement Note, we just assumed checking it would publish the information, and we had over 150 finding aids entered before anyone realized that they weren't actually showing up.  I know, I know.  Assuming is a bad thing.  We're doing a bit of a rush job, as we have a deadline for taking down our old PDFs.

I believe that LibraryHost.com, our host, has now put in a feature request to Lyrasis.  I'm not sure if they'd be willing or able to implement a plug-in.  It sounds wonderful if it were pretty easy all around.  Otherwise, we can make do with the notes fields.

As a side note, part of what threw me is that it seems counterintuitive to me, as a complete n00b, for the rights statement not to show up in the public interface.  I wonder if a note to this effect should be included in the help documentation?  Is this where I should mention this?  Or maybe something on the wiki? Or is it only counterintuitive to me?

Thanks again!
Freya

[cid:image001.png at 01D507DF.8CCD64B0]

Freya Anderson
Head, Information Services
Acting Head, Historical Collections
phone: 907.465.1315

Andrew P. Kashevaroff Building
Mail: PO Box 110571, Juneau, AK 99811
Visit: 395 Whittier St., Juneau, AK 99801

email<mailto:freya.anderson at alaska.gov> | web<http://library.alaska.gov/> |  sign up for event notifications<http://list.state.ak.us/mailman/listinfo/at-apk-and-sjm> | The Information Center for Government<http://library.alaska.gov/is/>




From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Custer, Mark
Sent: Sunday, May 19, 2019 4:47 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Rights Statement on public user interface

Dear Freya,

Unfortunately that's right.  The rights statement records (as well as some other record types, like event records) do not appear in the public interface as far as I'm aware.  They also do not get added to EAD exports (although they could, if there were a mapping for that data).

That said, the rights metadata is still available in the public interface for display, so that data could be surfaced with a plugin with any version of ArchivesSpace.  I don't know of any plugins offhand that do that (maybe others on the list do?), but I could come up with a pretty basic one if that's of interest.

There is lots of data that can be stored in an ArchivesSpace rights statements, though (such as linked agents, acts, external documents, and notes), which makes adding them to the PUI a bit of a design challenge. I'll also admit that I'm not very familiar with those records in ArchivesSpace. Right now, we only use  notes to capture that type of information.


Which fields are you using with your rights statements?

All my best,

Mark


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Anderson, Freya N (EED) <freya.anderson at alaska.gov<mailto:freya.anderson at alaska.gov>>
Sent: Tuesday, May 14, 2019 8:17 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Rights Statement on public user interface


Hello all,



It was recently pointed out to me by one of our team, as we rush to get content into ArchivesSpace, that the Rights Statement doesn't show up on the public user interface.  We enter it in the Resource, mark every Publish box, and click Publish All at the end.  Everything looks fine at the staff end, but no rights statement appears for the public.  Is this the way it's supposed to work?  Is there anything we can do so the right statement shows up, other than adding it in the Notes?



We're using LibraryHost to host our instance.



Thanks!

Freya



[cid:image001.png at 01D507DF.8CCD64B0]


Freya Anderson

Head, Information Services

Acting Head, Historical Collections

phone: 907.465.1315



Andrew P. Kashevaroff Building

Mail: PO Box 110571, Juneau, AK 99811

Visit: 395 Whittier St., Juneau, AK 99801



email<mailto:freya.anderson at alaska.gov> | web<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Flibrary.alaska.gov-252F-26data-3D02-257C01-257Cmark.custer-2540yale.edu-257C9995d0a848f049d8428408d6d8caad6c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C636934762377844252-26sdata-3DhUlnyA1RfmUYxxJyQ2SgZlQmS3B96zqYYmJHBqB-252BIds-253D-26reserved-3D0&d=DwMF-g&c=teXCf5DW4bHgLDM-H5_GmQ&r=zpyNM8XmubIcMD3TDrS5VNZH6ddxfi9PcHMl6Maf5tU&m=ypDcUz93C--DgEM5EiLJzp5WNQ4VdCI9iXYkydAC0Wo&s=MpT0iIqCqQvWkameLoGvymG9iGvVihHAb9gkbtM95EM&e=> |  sign up for event notifications<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Flist.state.ak.us-252Fmailman-252Flistinfo-252Fat-2Dapk-2Dand-2Dsjm-26data-3D02-257C01-257Cmark.custer-2540yale.edu-257C9995d0a848f049d8428408d6d8caad6c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C636934762377854261-26sdata-3DUMb56zC-252FonMsuJ0FNV9dDoBA1oeoq8wJwDDKdsHxlCo-253D-26reserved-3D0&d=DwMF-g&c=teXCf5DW4bHgLDM-H5_GmQ&r=zpyNM8XmubIcMD3TDrS5VNZH6ddxfi9PcHMl6Maf5tU&m=ypDcUz93C--DgEM5EiLJzp5WNQ4VdCI9iXYkydAC0Wo&s=DoKhjDVhuzSkaMq_wYlI4zEznfm308RMjMp1tvJ1UK4&e=> | The Information Center for Government<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Flibrary.alaska.gov-252Fis-252F-26data-3D02-257C01-257Cmark.custer-2540yale.edu-257C9995d0a848f049d8428408d6d8caad6c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C636934762377854261-26sdata-3D-252B8QyAazSkUS7T-252BG0eDc1b4Pt1Pjyvc9TtrJU1hwgOHA-253D-26reserved-3D0&d=DwMF-g&c=teXCf5DW4bHgLDM-H5_GmQ&r=zpyNM8XmubIcMD3TDrS5VNZH6ddxfi9PcHMl6Maf5tU&m=ypDcUz93C--DgEM5EiLJzp5WNQ4VdCI9iXYkydAC0Wo&s=iQeuWYEjh9DST_50Tz82_uIp_SEua7NHmbNdWYIPBWQ&e=>





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190521/0f5841c0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 16891 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190521/0f5841c0/attachment.png>

From Kevin.Clair at du.edu  Tue May 21 19:43:09 2019
From: Kevin.Clair at du.edu (Kevin Clair)
Date: Tue, 21 May 2019 23:43:09 +0000
Subject: [Archivesspace_Users_Group] Survey of ArchivesSpace documentation
	writers
Message-ID: <4D60E05F-77C4-4729-8D5E-E9F517580137@du.edu>

Hello!

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

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

cheers,
-Kevin Clair, for the ArchivesSpace UAC Documentation Sub-team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190521/d1559cfb/attachment.html>

From rachel.searcy at nyu.edu  Wed May 22 17:02:30 2019
From: rachel.searcy at nyu.edu (Rachel Aileen Searcy)
Date: Wed, 22 May 2019 17:02:30 -0400
Subject: [Archivesspace_Users_Group] MARC export bug in 2.5.2
Message-ID: <CAGFAsrOjrJ+bXz1vRXsaeva8GXCexS61BUhsxgrNOZgsMeGHpA@mail.gmail.com>

Hello list!

We upgraded to version 2.5.2 a few weeks back and missed this issue in our
testing process. We noticed that the MARC export is exporting relators of
added entries as the translation instead of the actual value. For example,
now =700 1\$aDoe, John.$4Donor is being exported instead of =700 1\$aDoe,
John.$4dnr. We have confirmed this to be happening in both our local
instance and the community sandbox. On our end, this creates a validation
error for OCLC records, and is inconvenient for our ILS workflow, as the
two are bundled together.

We've already submitted a JIRA ticket
<https://archivesspace.atlassian.net/browse/ANW-896> for this bug, and are
planning to address this in the short-term through a MarcEdit tasklist, but
wanted to flag this for others or hear if there were alternative solutions
we hadn't thought of.

Thanks,
Rachel Searcy
Accessioning Archivist, Archival Collections Management
New York University Libraries
212.998.2539 | rachel.searcy at nyu.edu
My pronouns are she/her
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190522/f07a4eed/attachment.html>

From chad.mills at rutgers.edu  Wed May 29 10:34:09 2019
From: chad.mills at rutgers.edu (Chad Mills)
Date: Wed, 29 May 2019 14:34:09 +0000
Subject: [Archivesspace_Users_Group] Lyrasis OAuth plugin HTTP/HTTPS
Message-ID: <BN7PR14MB24013EEAFFF515BFA443A066871F0@BN7PR14MB2401.namprd14.prod.outlook.com>

Hi all,

We are working on installing and using the Lyrasis OAuth plugin<https://github.com/lyrasis/aspace-oauth> to add institutional login.  When we have that configured with the HTTPS proxy setting<http://archivesspace.github.io/archivesspace/user/serving-archivesspace-user-facing-applications-over-https/> in Apache the requests being sent to our institutional login do not contain the final redirect back with https, but rather http.  So the value in the service parameter needs to be changed from starting with http:// to https://.  We are stumped as to how to correct this issue and we are hoping someone hit this same roadblock and could help out.

Thanks!
Chad


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190529/608053bc/attachment.html>

From reesj at mail.nlm.nih.gov  Wed May 29 11:43:41 2019
From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E])
Date: Wed, 29 May 2019 15:43:41 +0000
Subject: [Archivesspace_Users_Group] Working with multiple ASpace strings
Message-ID: <BN8PR09MB3345F6034F7D58CD799DDDECC81F0@BN8PR09MB3345.namprd09.prod.outlook.com>

Hi all,

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


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

Do you worry about keeping the strings in synch?

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

John


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





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190529/344bdc66/attachment.html>

From Joshua.D.Shaw at dartmouth.edu  Thu May 30 08:12:14 2019
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Thu, 30 May 2019 12:12:14 +0000
Subject: [Archivesspace_Users_Group] Working with multiple ASpace strings
In-Reply-To: <BN8PR09MB3345F6034F7D58CD799DDDECC81F0@BN8PR09MB3345.namprd09.prod.outlook.com>
References: <BN8PR09MB3345F6034F7D58CD799DDDECC81F0@BN8PR09MB3345.namprd09.prod.outlook.com>
Message-ID: <BL0PR03MB41459155AE5989BFAF799BF1AB1F0@BL0PR03MB4145.namprd03.prod.outlook.com>

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

Hope that helps!
Joshua

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Rees, John (NIH/NLM) [E] <reesj at mail.nlm.nih.gov>
Sent: Wednesday, May 29, 2019 11:43 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Working with multiple ASpace strings


Hi all,



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



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



Do you worry about keeping the strings in synch?



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



John





John P. Rees

Archivist and Digital Resources Manager

History of Medicine Division

National Library of Medicine

301-827-4510










-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190530/4fc69bbd/attachment.html>

From Kevin.Clair at du.edu  Thu May 30 08:32:22 2019
From: Kevin.Clair at du.edu (Kevin Clair)
Date: Thu, 30 May 2019 12:32:22 +0000
Subject: [Archivesspace_Users_Group] Working with multiple ASpace strings
Message-ID: <5DC20C16-D71B-4A2A-B0BC-4A35CE82DF68@du.edu>

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

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Joshua D. Shaw" <Joshua.D.Shaw at dartmouth.edu>
Reply-To: Archivesspace Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, May 30, 2019 at 6:12 AM
To: Archivesspace Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Working with multiple ASpace strings

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

Hope that helps!
Joshua

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Rees, John (NIH/NLM) [E] <reesj at mail.nlm.nih.gov>
Sent: Wednesday, May 29, 2019 11:43 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Working with multiple ASpace strings


Hi all,



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



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



Do you worry about keeping the strings in synch?



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



John





John P. Rees

Archivist and Digital Resources Manager

History of Medicine Division

National Library of Medicine

301-827-4510










-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190530/282b6882/attachment.html>

From reesj at mail.nlm.nih.gov  Thu May 30 12:13:10 2019
From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E])
Date: Thu, 30 May 2019 16:13:10 +0000
Subject: [Archivesspace_Users_Group] Working with multiple ASpace strings
In-Reply-To: <5DC20C16-D71B-4A2A-B0BC-4A35CE82DF68@du.edu>
References: <5DC20C16-D71B-4A2A-B0BC-4A35CE82DF68@du.edu>
Message-ID: <BN8PR09MB33454BFF9A90FAFDA2CD33F3C8180@BN8PR09MB3345.namprd09.prod.outlook.com>

Thank you.

As usual, it?s the nervous-human equation that is the most confounding when embarking on major technological change.

Namaste,
John


From: Kevin Clair <Kevin.Clair at du.edu>
Sent: Thursday, May 30, 2019 8:32 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Working with multiple ASpace strings

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

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Joshua D. Shaw" <Joshua.D.Shaw at dartmouth.edu<mailto:Joshua.D.Shaw at dartmouth.edu>>
Reply-To: Archivesspace Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, May 30, 2019 at 6:12 AM
To: Archivesspace Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Working with multiple ASpace strings

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

Hope that helps!
Joshua

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Rees, John (NIH/NLM) [E] <reesj at mail.nlm.nih.gov<mailto:reesj at mail.nlm.nih.gov>>
Sent: Wednesday, May 29, 2019 11:43 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Working with multiple ASpace strings


Hi all,



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



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



Do you worry about keeping the strings in synch?



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



John





John P. Rees

Archivist and Digital Resources Manager

History of Medicine Division

National Library of Medicine

301-827-4510










-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190530/14cce1db/attachment.html>

From christine.dibella at lyrasis.org  Thu May 30 16:54:41 2019
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Thu, 30 May 2019 20:54:41 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace v2.6.0 now available
Message-ID: <CY4PR2201MB11433130904DE06FF76F768FF1180@CY4PR2201MB1143.namprd22.prod.outlook.com>

ArchivesSpace is announcing the availability of v2.6.0. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.6.0.

This release contains program-led and community pull requests that provide feature enhancements, bug fixes, infrastructure improvements and documentation updates. There are a number of small changes to the staff and public interfaces to improve usability and clarity. There is also a significant revamp of how background jobs run, including a new reports page layout. This release also has a new feature guided by a community-initiated and authored specification, the option to generate human-readable URLs for use in the public user interface. A full list of the changes and improvements is provided on the release page.

Thanks very much to community members Br. Paul, Blake Carver, Mark Cooper, Tim DiLauro, Bobbi Fox, Brian Harrington, dvhassel, Adam Jazairi, Steve Majewski, Dave Mayo, Curtis Poston, Austin Schaffer, and Trevor Thornton for their code contributions to this release. Thanks also to the contract developer we have been able to engage through member funds, Manny Rodriguez (via LibraryHost), for his substantial efforts on the human-readable URLs feature. Thanks as always to LYRASIS Digital Technology Services for their technical support. This release is also very much a testament to the efforts of our Development Prioritization sub-team, Testing sub-team, Technical Documentation sub-team, and Core Committers Group, as well as individual ArchivesSpace users like Celia Caust-Ellenbogen, Cory Nimer, and Rachel Searcy, who identified and helped us work through particular bug fixes and new features in this release.

Within the program, our co-op student Sarah Morrissey did amazing work in providing a number of community-requested improvements to the staff and public interfaces (many of them recommended by the Staff Interface Enhancement Working Group last year). And though I don't always call them out in release announcements, I would be remiss if I didn't mention that Technical Lead Laney McGlohon and Junior Developer Lora Woodford worked through a tremendous amount of their own code and that of others to bring this packed release to you. We are very fortunate to have such a wonderful community-based and user-focused developer team.

Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not yet upgraded to a recent version, we recommend going directly to 2.6.0. Please note that a complete reindex is required for this release.

Please let us know if you have any questions or need help upgrading. We are turning our attention to some needed infrastructure improvements for the application, but also aim for some work on agents and recording language information that will make ArchivesSpace more standards-compliant in these areas to be ready to go into the application in a release later this summer. We'll be updating the roadmap on the wiki in the next few days.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190530/f19e5d55/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 6609 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190530/f19e5d55/attachment.jpg>

From Jessica.Crouch at lyrasis.org  Fri May 31 09:17:34 2019
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Fri, 31 May 2019 13:17:34 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace Update - May 2019
Message-ID: <F84E89F9-9503-46BD-9418-55454B296243@lyrasis.org>

[ASpaceOrgHome.jpg]

May 2019 Update
Development


ArchivesSpace has released v2.6.0. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.6.0.

This release contains program-led and community pull requests that provide feature enhancements, bug fixes, infrastructure improvements and documentation updates. There are a number of small changes to the staff and public interfaces to improve usability and clarity. There is also a significant revamp of how background jobs run, including a new reports page layout. This release also has a new feature guided by a community-initiated and authored specification, the option to generate human-readable URLs for use in the public user interface. A full list of the changes and improvements is provided on the release page.

Thanks very much to community members Br. Paul, Blake Carver, Mark Cooper, Tim DiLauro, Bobbi Fox, Brian Harrington, dvhassel, Adam Jazairi, Steve Majewski, Dave Mayo, Curtis Poston, Austin Schaffer, and Trevor Thornton for their code contributions to this release. Thanks also to the contract developer we have been able to engage through member funds, Manny Rodriguez (via LibraryHost), for his substantial efforts on the human-readable URLs feature. Within the program, our co-op student Sarah Morrissey did amazing work in providing a number of community-requested improvements to the staff and public interfaces, and Technical Lead Laney McGlohon and Junior Developer Lora Woodford worked through a tremendous amount of their own code and that of others to bring this packed release to you. This release is also very much a testament to the efforts of our Development Prioritization sub-team, Testing sub-team, Technical Documentation sub-team, and Core Committers Group, as well as individual ArchivesSpace users like Celia Caust-Ellenbogen, Cory Nimer, and Rachel Searcy, who identified and helped us work through particular bug fixes and new features in this release.


Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not yet upgraded to a recent version, we recommend going directly to 2.6.0. Please note that a complete reindex is required for this release.

Save the Date: ArchivesSpace Annual Member Forum


The 5th annual ArchivesSpace Member Forum will be held on August 2nd at the Thompson Conference Center at our member institution the University of Texas - Austin.  As in previous years, this will be a free opportunity for staff of ArchivesSpace member institutions to meet and share information with each other and the program team.  More information about the program and logistics coming soon!

Call for Participation: ArchivesSpace Code of Conduct Working Group


We?re looking for volunteers to serve on the ArchivesSpace Code of Conduct working group.  The Working Group?s mission is to draft a code of conduct that addresses both online and in person interaction and appropriate responses to violations.  The working group will draft a Code of Conduct to present to the ArchivesSpace community for comment before implementation. Contact Jessica at jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org> to volunteer.

Call for Participation: Upcoming Webinar: From Archon to ArchivesSpace


Is your institution a former user of Archon now using ArchivesSpace?  Have you adapted workflows, workarounds or tricks for your implementation of ArchivesSpace to account for what you miss in Archon?  We will be hosting an upcoming webinar geared specifically for former Archon users who are looking to adapt workflows for ArchivesSpace.  If you would like to present at this webinar, contact Jessica at jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>. More information on the webinar itself will be available later in the year.

Membership Update

We are excited to welcome our newest members to our community! Our new members since April 30  include:

  *   Elizabethtown College (Elizabethtown, PA)
  *   Hauser and Wirth Institute (New York, NY)
  *   Los Alamos National Laboratory (Los Alamos, NM)
  *   Ohio History Connection (Columbus, OH)
  *   Ripon College (Ripon, WI)
  *   Trevecca Nazarene University (Nashville, TN)

As a reminder, we will soon be sending out membership renewals for 2019-2020.  If you need to update your billing contact information or if you would like to receive your invoice early, email ArchivesSpaceHome at lyrasis.org.

As of May 30, we have 387 General members, 19 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<mailto: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 Tools 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.



Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
Skype: jdowdcrouch

[page1image482511520]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190531/f623ea08/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 19859 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190531/f623ea08/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 29058 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190531/f623ea08/attachment-0001.jpg>

From dfwalton at ua.edu  Fri May 31 12:10:59 2019
From: dfwalton at ua.edu (Walton, Donnelly)
Date: Fri, 31 May 2019 16:10:59 +0000
Subject: [Archivesspace_Users_Group] anyone using CAIASoft with
	ArchivesSpace?
Message-ID: <9178d733e39f4c0597a63030b67c429a@ua.edu>

Hi,

Is anyone using CAIASoft with ArchivesSpace? My library is going to use CAIASoft as our library storage management software for a new off-site storage facility. I saw that CAIA just updated their list of supported systems (re: APIs), and ArchivesSpace is now on the list. Our planning group is putting together questions for the CAIA team, so we?ll be talking to them about this soon. But I?d love to talk to anyone who is using CAIA with ArchivesSpace.

Thanks,

Donnelly Lancaster Walton
Archival Access Coordinator, Special Collections
University Libraries
The University of Alabama<https://www.ua.edu/>
W. S. Hoole Library, Mary Harmon Bryant Hall
Box 870266
Tuscaloosa, AL 35487
Office 205-348-0505<tel:205-348-0505>
dfwalton at ua.edu<mailto:dfwalton at ua.edu> | https://www.lib.ua.edu/libraries/hoole/
[The University of Alabama]<https://www.ua.edu/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190531/0adbe849/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 6052 bytes
Desc: image001.gif
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190531/0adbe849/attachment.gif>

From blake.carver at lyrasis.org  Fri May 31 12:56:03 2019
From: blake.carver at lyrasis.org (Blake Carver)
Date: Fri, 31 May 2019 16:56:03 +0000
Subject: [Archivesspace_Users_Group] Plugin problems: want the Notes
 section	to default to open
In-Reply-To: <2329bb709747e7653fc2af9be42e985a55c2b0e3.camel@cam.ac.uk>
References: <2329bb709747e7653fc2af9be42e985a55c2b0e3.camel@cam.ac.uk>
Message-ID: <DM5PR22MB08114EA8BC4869DB41E061E19F190@DM5PR22MB0811.namprd22.prod.outlook.com>

Hi Nick,
Did you ever get this one figured out?
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Nick Butler <npwb2 at cam.ac.uk>
Sent: Tuesday, May 21, 2019 10:10 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Plugin problems: want the Notes section to default to open

Hi all,

We're trying to write a plugin to default the Notes section of the new and edit resources pages to being open (i.e. as if the "Add Note" button had been clicked automatically when the page loaded).

I've got a layout_head.html.erb file which loads the appropriate js file in the correct page, my difficulty just comes from getting the button to click without creating errors. Here are the contents of my js file:

$(function () {
  var click_the_button = function () {
    var button = document.querySelector('.btn.btn-sm.btn-default.pull-right.add-note');
    button.click();
  };
  click_the_button();
});

When the page loads I get the error messages seen in my attached screenshot. I've also tried requiring notes.crud.js and simply running the createTopLevelNote function, but this gives precisely the same error messages. Note that the URL for creating a new resource is https://arcspace-dev.lib.cam.ac.uk/staff/resources/new, but when the error messages appear this changes to https://arcspace-dev.lib.cam.ac.uk/staff/resources.

As a test I've changed the click_the_button function to perform another task instead:

var click_the_button = function () {
    var button = document.querySelector('.btn.btn-sm.btn-default.pull-right.add-note');
   button.style.backgroundColor = 'green';
  };

This works exactly as expected, changing the button colour to green. No error messages appear and the URL stays as expected.

I haven't found any other plugins that do something like this (and I know very little Javascript!) so I'm at a loss here. Any advice or links to relevant documentation would be greatly appreciated.

Many thanks,
Nick

--

Nick Butler
Software Developer
Digital Services
Cambridge University Library
West Road
Cambridge CB3 9DR, UK

npwb2 at cam.ac.uk<mailto:npwb2 at cam.ac.uk>

Internal tel: 33067
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190531/a6cf39ef/attachment.html>