[Archivesspace_Users_Group] ArchivesSpace weird behavior

[Galligan, Patrick]

Hi all,

We've run across a new (to me) issue in ArchivesSpace that I wanted to see if 
anyone else had encountered before: very sporadically AS will redirect an 
archivist to a different archival object after saving work in a finding aid in 
the Staff Interface. The changes will be saved and reflected, but the user will 
be taken to a different object instead of staying on the same one as intended. 
This is apparently happening at random, and not consistently happening on every 
finding aid or for every user, which makes it hard to troubleshoot.

Anyone run into this before? Have any solutions or thoughts? It seems to happen 
most often with large finding aids.

Thanks,
Patrick Galligan
Rockefeller Archive Center
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Performance hits with updated agents module?

[Galligan, Patrick]

Hi all,

Has anyone done any performance benchmarking between AS version 2.x and AS 
version 3.1.x? We’ve updated a few months ago and some of our GET requests are 
taking way longer than we’d expect.

This request: GET /agents/people?all_ids=True_size=100=1 took about 
2.5 minutes to complete.

D, [2022-02-02T13:55:04.329994 #1804489] DEBUG -- : Thread-65736: Responded 
with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, 
must-revalidate, max-age=0", "Content-Length"=>"321644"}, 
["{\"first_page\":1,\"last_page\":12,\"this_page\":1,\"total\":1176,\"results\":[{\"lock_version\":0,\"publish\":false,\"create_time\":\"2014-12-05T20:32:16Z\",\"system_mtime\":\"2021-12-03T21:53:20Z\",\"user_mtime\":\"2014-12-05T20:32:16Z\",\"is_slug_auto\":false,\"jsonmodel_type\":\"agent_person\",\"agent_contacts\":[],\"agent_record_controls\":[],\"agent_alternate_sets\":[],\"age...
 in 154446ms

Has anyone else experienced this? It seems to have started after we upgraded.

-Patrick
Rockefeller Archive Center
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Repeating error message

[Galligan, Patrick]

Blake,

Sorry for the delayed response, we needed to wait for this issue to crop up 
again before I could get the full error message. I’ve grabbed two messages that 
were available from the tail and happening nonstop. The last 3000 lines of the 
log file were basically these two errors repeating.

I’ve attached a doc with the messages. Be warned, it’s like 43 pages long.

We think it’s cropping up during high CPU usage on the server.

Thanks
Patrick Galligan
RAC

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Date: Tuesday, January 4, 2022 at 10:58 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Repeating error message
***External*** This email originated from outside of the organization. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.***


Can you share way more of the area around those errors?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Galligan, Patrick 
Sent: Tuesday, January 4, 2022 10:53 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Repeating error message


All,



We’ve been getting the below error message about once a week for the past few 
weeks, which has required a restart of the AS system, but we’ve been unable to 
track down what’s causing it. We’re on AS version 3.1.1. When the messages 
start showing up, we’re unable to load resources or accessions. We are also 
using an external Solr index that is located on a different server.



Any ideas on where to start?



ERROR -- : Thread-2956: uri:classloader:/jsonmodel_client.rb:490:in `all'

/archivesspace/data/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/WEB-INF/app/main.rb:32:in
 `block in main'



There are a lot of other messages in about ruby gems and the indexer like so:



archivesspace.gems.gems.sinatra_minus_2_dot_0_dot_5.lib.sinatra.base.RUBY$method$call$0(/archivesspace/gems/gems/sinatra-2.0.5/lib/sinatra/base.rb:194)

archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.main.invokeOther31:call(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:320)



There’s a lot going on in the messages, so any insight from someone that has 
seen this type of error message before would be helpful.



Patrick Galligan

Rockefeller Archive Center






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

[Archivesspace_Users_Group] Repeating error message

[Galligan, Patrick]

All,

We’ve been getting the below error message about once a week for the past few 
weeks, which has required a restart of the AS system, but we’ve been unable to 
track down what’s causing it. We’re on AS version 3.1.1. When the messages 
start showing up, we’re unable to load resources or accessions. We are also 
using an external Solr index that is located on a different server.

Any ideas on where to start?

ERROR -- : Thread-2956: uri:classloader:/jsonmodel_client.rb:490:in `all'
/archivesspace/data/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/WEB-INF/app/main.rb:32:in
 `block in main'

There are a lot of other messages in about ruby gems and the indexer like so:

archivesspace.gems.gems.sinatra_minus_2_dot_0_dot_5.lib.sinatra.base.RUBY$method$call$0(/archivesspace/gems/gems/sinatra-2.0.5/lib/sinatra/base.rb:194)
archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.main.invokeOther31:call(/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:320)

There’s a lot going on in the messages, so any insight from someone that has 
seen this type of error message before would be helpful.

Patrick Galligan
Rockefeller Archive Center


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

[Archivesspace_Users_Group] ArchivesSpace-Aeon add-on in AS verision 3.1.1

[Galligan, Patrick]

Hi all,

Can anyone confirm that the ArchivesSpace-Aeon Client 
addon works in 
ArchivesSpace version 3.1.1? We’ve recently updated and are having an issue 
with interacting with the interface through the Aeon client.

Thanks!
Patrick Galligan
Rockefeller Archive Center
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Optimistic locking error

[Galligan, Patrick]

Trevor,

After some help from Mark Triggs, and some digging into logs, it looks like our 
issue is overlapping login sessions from an application authenticating really 
often.

-Patrick

From: Galligan, Patrick 
Date: Thursday, December 2, 2021 at 1:48 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Optimistic locking error
We’re on version 2.8.0, and we were going to upgrade to 3.1.1 over the weekend.

Can confirm that it’s not causing performance issues, but is inflating the logs 
like crazy.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Trevor 
Thornton 
Date: Thursday, December 2, 2021 at 1:46 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Optimistic locking error
***External*** This email originated from outside of the organization. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.***

I can confirm that this is a thing, at least it's happening to me as well 
(we're on v2.8.1 still). It isn't affecting performance from what I can tell, 
but the lock_version value for the user keeps getting higher (currently over 
37). At some point I shut down AS, reset the lock_version to 0, and 
restarted, and it just started doing it again.

It doesn't seem to be causing any other problems, but it does fill up the logs, 
and it's annoying. What version are you on? We're getting ready to upgrade and 
I was hoping the problem would magically go away when we did.

On Thu, Dec 2, 2021 at 1:11 PM Galligan, Patrick 
mailto:pgalli...@rockarch.org>> wrote:
Peter,

Unfortunately that’s an empty set. It seems like the lock_version is constantly 
changing for this record. I’m not sure why.

-Patrick

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Peter Heiner mailto:ph...@cam.ac.uk>>
Date: Thursday, December 2, 2021 at 12:41 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Optimistic locking error
***External*** This email originated from outside of the organization. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.***

Hi Patrick,

What does
SELECT * FROM `user` WHERE ((`id` = 113) AND (`lock_version` = 1271));
say?

p


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Galligan, Patrick 
mailto:pgalli...@rockarch.org>>
Sent: 02 December 2021 16:57
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Optimistic locking error


Hi all,



I’m trying to diagnose and fix a warning I’m seeing in our AS log files every 
12 or 13 seconds:



Got an optimistic locking error when updating user: Attempt to update object 
did not result in a single row modification (SQL: UPDATE `user` SET 
`system_mtime` = '2021-12-02 16:52:37', `user_mtime` = '2021-12-02 16:52:37', 
`lock_version` = 1272 WHERE ((`id` = 113) AND (`lock_version` = 1271)) LIMIT 1)



I can delete the user, but if I remake it with the same username, the warning 
comes back. If I leave the user open for editing, I get the “This record has 
been updated by another user. Please refresh the page to access the latest 
version,” message in the UI.



Any idea how to fix this issue? I’d prefer to be able to keep the username the 
same. I’m not sure why the system thinks there are two different lock versions 
associated with the record.



Thanks,

Patrick Galligan

Rockefeller Archive Center
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org<mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Optimistic locking error

[Galligan, Patrick]

We’re on version 2.8.0, and we were going to upgrade to 3.1.1 over the weekend.

Can confirm that it’s not causing performance issues, but is inflating the logs 
like crazy.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Trevor 
Thornton 
Date: Thursday, December 2, 2021 at 1:46 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Optimistic locking error
***External*** This email originated from outside of the organization. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.***

I can confirm that this is a thing, at least it's happening to me as well 
(we're on v2.8.1 still). It isn't affecting performance from what I can tell, 
but the lock_version value for the user keeps getting higher (currently over 
37). At some point I shut down AS, reset the lock_version to 0, and 
restarted, and it just started doing it again.

It doesn't seem to be causing any other problems, but it does fill up the logs, 
and it's annoying. What version are you on? We're getting ready to upgrade and 
I was hoping the problem would magically go away when we did.

On Thu, Dec 2, 2021 at 1:11 PM Galligan, Patrick 
mailto:pgalli...@rockarch.org>> wrote:
Peter,

Unfortunately that’s an empty set. It seems like the lock_version is constantly 
changing for this record. I’m not sure why.

-Patrick

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Peter Heiner mailto:ph...@cam.ac.uk>>
Date: Thursday, December 2, 2021 at 12:41 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Optimistic locking error
***External*** This email originated from outside of the organization. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.***

Hi Patrick,

What does
SELECT * FROM `user` WHERE ((`id` = 113) AND (`lock_version` = 1271));
say?

p


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Galligan, Patrick 
mailto:pgalli...@rockarch.org>>
Sent: 02 December 2021 16:57
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Optimistic locking error


Hi all,



I’m trying to diagnose and fix a warning I’m seeing in our AS log files every 
12 or 13 seconds:



Got an optimistic locking error when updating user: Attempt to update object 
did not result in a single row modification (SQL: UPDATE `user` SET 
`system_mtime` = '2021-12-02 16:52:37', `user_mtime` = '2021-12-02 16:52:37', 
`lock_version` = 1272 WHERE ((`id` = 113) AND (`lock_version` = 1271)) LIMIT 1)



I can delete the user, but if I remake it with the same username, the warning 
comes back. If I leave the user open for editing, I get the “This record has 
been updated by another user. Please refresh the page to access the latest 
version,” message in the UI.



Any idea how to fix this issue? I’d prefer to be able to keep the username the 
same. I’m not sure why the system thinks there are two different lock versions 
associated with the record.



Thanks,

Patrick Galligan

Rockefeller Archive Center
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org<mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Optimistic locking error

[Galligan, Patrick]

Peter,

Unfortunately that’s an empty set. It seems like the lock_version is constantly 
changing for this record. I’m not sure why.

-Patrick

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Peter 
Heiner 
Date: Thursday, December 2, 2021 at 12:41 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Optimistic locking error
***External*** This email originated from outside of the organization. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.***

Hi Patrick,

What does
SELECT * FROM `user` WHERE ((`id` = 113) AND (`lock_version` = 1271));
say?

p


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Galligan, Patrick 
Sent: 02 December 2021 16:57
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Optimistic locking error


Hi all,



I’m trying to diagnose and fix a warning I’m seeing in our AS log files every 
12 or 13 seconds:



Got an optimistic locking error when updating user: Attempt to update object 
did not result in a single row modification (SQL: UPDATE `user` SET 
`system_mtime` = '2021-12-02 16:52:37', `user_mtime` = '2021-12-02 16:52:37', 
`lock_version` = 1272 WHERE ((`id` = 113) AND (`lock_version` = 1271)) LIMIT 1)



I can delete the user, but if I remake it with the same username, the warning 
comes back. If I leave the user open for editing, I get the “This record has 
been updated by another user. Please refresh the page to access the latest 
version,” message in the UI.



Any idea how to fix this issue? I’d prefer to be able to keep the username the 
same. I’m not sure why the system thinks there are two different lock versions 
associated with the record.



Thanks,

Patrick Galligan

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

[Archivesspace_Users_Group] Optimistic locking error

[Galligan, Patrick]

Hi all,

I’m trying to diagnose and fix a warning I’m seeing in our AS log files every 
12 or 13 seconds:

Got an optimistic locking error when updating user: Attempt to update object 
did not result in a single row modification (SQL: UPDATE `user` SET 
`system_mtime` = '2021-12-02 16:52:37', `user_mtime` = '2021-12-02 16:52:37', 
`lock_version` = 1272 WHERE ((`id` = 113) AND (`lock_version` = 1271)) LIMIT 1)

I can delete the user, but if I remake it with the same username, the warning 
comes back. If I leave the user open for editing, I get the “This record has 
been updated by another user. Please refresh the page to access the latest 
version,” message in the UI.

Any idea how to fix this issue? I’d prefer to be able to keep the username the 
same. I’m not sure why the system thinks there are two different lock versions 
associated with the record.

Thanks,
Patrick Galligan
Rockefeller Archive Center
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Duplicated agent dates in migration to 3.0.1

[Galligan, Patrick]

Hi all,

We’ve noticed that in our test migration from ArchivesSpace version 2.8.0 to 
3.0.1 that the agent migration was sometimes creating two separate structured 
dates based on whether there was an existing date expression or not in the 
dates of existence section.

Here is the JSON before migration:

"dates_of_existence": [
{
"lock_version": 0,
"expression": "1915-2017",
"begin": "1915",
"end": "2017",
"created_by": "pgalligan",
"last_modified_by": "pgalligan",
"create_time": "2019-12-04T14:24:11Z",
"system_mtime": "2019-12-04T14:24:11Z",
"user_mtime": "2019-12-04T14:24:11Z",
"date_type": "range",
"label": "existence",
"jsonmodel_type": "date"
}
],


Here is the JSON post-migration:

"dates_of_existence": [
{
"create_time": "2021-06-16T19:12:16Z",
"system_mtime": "2021-06-16T19:12:16Z",
"user_mtime": "2021-06-16T19:12:16Z",
"lock_version": 0,
"date_label": "existence",
"date_type_structured": "single",
"jsonmodel_type": "structured_date_label",
"structured_date_single": {
"date_expression": "1915-2017",
"create_time": "2021-06-16T19:12:16Z",
"system_mtime": "2021-06-16T19:12:16Z",
"user_mtime": "2021-06-16T19:12:16Z",
"lock_version": 0,
"date_role": "begin",
"date_standardized_type": "standard",
"jsonmodel_type": "structured_date_single"
}
},
{
"create_time": "2021-06-16T19:12:16Z",
"system_mtime": "2021-06-16T19:12:16Z",
"user_mtime": "2021-06-16T19:12:16Z",
"lock_version": 0,
"date_label": "existence",
"date_type_structured": "range",
"jsonmodel_type": "structured_date_label",
"structured_date_range": {
"begin_date_standardized": "1915",
"end_date_standardized": "2017",
"create_time": "2021-06-16T19:12:16Z",
"system_mtime": "2021-06-16T19:12:16Z",
"user_mtime": "2021-06-16T19:12:16Z",
"lock_version": 0,
"begin_date_standardized_type": "standard",
"end_date_standardized_type": "standard",
"jsonmodel_type": "structured_date_range"
}
}
],

It also seems to be creating a structured singular date instead of a date 
range. It’s parsing the expression correctly into separate dates, but it’s 
entirely unnecessary and creates and incorrect duplication.

This seems like a bug and would stop us from updating because it’d be a hassle 
to go in and remove these.

Is this intended behavior for this migration? There may be something I’m not 
understanding about MARC or EAC-CPF that makes this desirable, but it seems 
like a bug to me.

Thanks,
Patrick Galligan
Rockefeller Archive Center
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Manage Top Containers endpoints

[Galligan, Patrick]

Hey everyone,

Does anyone have experience getting search results from the Manage Top 
Containers functionality through the API?

I’m looking to do some response testing and was wondering how to structure 
requests against this page. Are the endpoints documented somewhere?

Thanks,
Patrick Galligan
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Running ArchivesSpace against Solr 8.8.1

[Galligan, Patrick]

Thank you! I’ll give this a shot.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Schanz, 
Megan 
Date: Thursday, February 25, 2021 at 1:49 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Running ArchivesSpace against Solr 
8.8.1
***External*** This email originated from outside of the organization. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.***

I ran into that exact problem. You need to make a change to the solrconfig.xml 
and schema.xml to have it load the ICU filter. Here is links to the exact 
changes you need to make to the file:

https://gitlab.msu.edu/msu-libraries/public/archivesspace-docker/-/blob/master/solr/solrconfig.xml.patch<https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.msu.edu_msu-2Dlibraries_public_archivesspace-2Ddocker_-2D_blob_master_solr_solrconfig.xml.patch=DwMF-g=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM=Y-nkcMVA8HUy414mqqPzYKQHoWcbkObHpxMl8sVQL2I=jZ-PtsJXeFM_K2ZYaq4wXMxmx42rh9bV0TOxKOLZedQ=tLnzlK7vU1xbDccAH0xe4LiKotMucSGVy_CBrb-0Kg8=>

https://gitlab.msu.edu/msu-libraries/public/archivesspace-docker/-/blob/master/solr/schema.xml.patch<https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.msu.edu_msu-2Dlibraries_public_archivesspace-2Ddocker_-2D_blob_master_solr_schema.xml.patch=DwMF-g=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM=Y-nkcMVA8HUy414mqqPzYKQHoWcbkObHpxMl8sVQL2I=jZ-PtsJXeFM_K2ZYaq4wXMxmx42rh9bV0TOxKOLZedQ=HOvLvcsK6xENK_o7SF8xwbDCFtH1F_Vz5Tl_Lu_UcgU=>

This is the commands you could run to have it apply those patches if it helps: 
https://gitlab.msu.edu/msu-libraries/public/archivesspace-docker/-/blob/master/solr/Dockerfile#L35<https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.msu.edu_msu-2Dlibraries_public_archivesspace-2Ddocker_-2D_blob_master_solr_Dockerfile-23L35=DwMF-g=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM=Y-nkcMVA8HUy414mqqPzYKQHoWcbkObHpxMl8sVQL2I=jZ-PtsJXeFM_K2ZYaq4wXMxmx42rh9bV0TOxKOLZedQ=YpdUXFgiX4WzNhuQZS1M7XGMlGajoYasGWaJfFpB7dw=>

I hope this gets it working for you!

- Megan


Megan Schanz
Michigan State University Libraries

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Galligan, Patrick 
Sent: Thursday, February 25, 2021 1:42 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Running ArchivesSpace against Solr 8.8.1


Hey everyone,



I’m trying to test out running AS against Solr 8.8.1, but I’m having trouble 
getting the core set up properly with the files in the AS Solr 
directory.<https://urldefense.proofpoint.com/v2/url?u=https-3A__urldefense.com_v3_-5F-5Fhttps-3A__github.com_archivesspace_archivesspace_tree_master_solr-5F-5F-3B-21-21HXCxUKc-21j-5FDgJzAPfLaI9rnYyaJdQBL-2D4MdM-2DONfKV6-2D3CC9S2dhLBL80vOS5CLm0Qo7ctg-24=DwMF-g=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM=Y-nkcMVA8HUy414mqqPzYKQHoWcbkObHpxMl8sVQL2I=jZ-PtsJXeFM_K2ZYaq4wXMxmx42rh9bV0TOxKOLZedQ=5I7EWxe8uIXxqWqaJ0mQB7YjpWiWqKwRJuXrhwKI6Gw=>



I make the Solr directory on the server with /conf and /data, generally 
following the instructions on running Archives with external 
Solr<https://urldefense.proofpoint.com/v2/url?u=https-3A__urldefense.com_v3_-5F-5Fhttps-3A__archivesspace.github.io_tech-2Ddocs_provisioning_solr.html-5F-5F-3B-21-21HXCxUKc-21j-5FDgJzAPfLaI9rnYyaJdQBL-2D4MdM-2DONfKV6-2D3CC9S2dhLBL80vOS5CLmlDXwdMM-24=DwMF-g=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM=Y-nkcMVA8HUy414mqqPzYKQHoWcbkObHpxMl8sVQL2I=jZ-PtsJXeFM_K2ZYaq4wXMxmx42rh9bV0TOxKOLZedQ=wNPJWsHbHjls1n2LYbcdMYquWXzCFcD1Kb1KUhsHHJM=>.



I’m getting this error when trying to actually create and initialize the core:



archivesspace: 
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
Could not load conf for core archivesspace: Can't load schema 
/solr-8.8.1/server/solr/archivesspace/conf/schema.xml: Plugin init failure for 
[schema.xml] fieldType "sort_icu": Plugin init failure for [schema.xml] 
analyzer/filter: Error loading class 'solr.ICUCollationKeyFilterFactory'





I read through this 
thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__urldefense.com_v3_-5F-5Fhttps-3A__www.drupal.org_project_search-5Fapi-5Fsolr_issues_3015993-5F-5F-3B-21-21HXCxUKc-21j-5FDgJzAPfLaI9rnYyaJdQBL-2D4MdM-2DONfKV6-2D3CC9S2dhLBL80vOS5CLmzeKzXQU-24=DwMF-g=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM=Y-nkcMVA8HUy414mqqPzYKQHoWcbkObHpxMl8sVQL2I=jZ-PtsJXeFM_K2ZYaq4wXMxmx42rh9bV0TOxKOLZedQ=W-pJ0wxUkn_vWJeG5OU22njnkdeobduznM5GWpFhbCY=>
 about the issue, but haven’t gotten anything to work yet.



Has anyone had experience with running external Solr that might have advice on 
what to do here?



Thanks,

Patrick Galligan

Rockefeller Archive Center

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

[Archivesspace_Users_Group] Running ArchivesSpace against Solr 8.8.1

[Galligan, Patrick]

Hey everyone,

I’m trying to test out running AS against Solr 8.8.1, but I’m having trouble 
getting the core set up properly with the files in the AS Solr 
directory.

I make the Solr directory on the server with /conf and /data, generally 
following the instructions on running Archives with external 
Solr.

I’m getting this error when trying to actually create and initialize the core:

archivesspace: 
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
Could not load conf for core archivesspace: Can't load schema 
/solr-8.8.1/server/solr/archivesspace/conf/schema.xml: Plugin init failure for 
[schema.xml] fieldType "sort_icu": Plugin init failure for [schema.xml] 
analyzer/filter: Error loading class 'solr.ICUCollationKeyFilterFactory'


I read through this 
thread about the 
issue, but haven’t gotten anything to work yet.

Has anyone had experience with running external Solr that might have advice on 
what to do here?

Thanks,
Patrick Galligan
Rockefeller Archive Center
Digital Archivist
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Separating Solr index to separate server?

[Galligan, Patrick]

Hey all,

We’re considering separating our Solr Index to a separate server for space and 
performance issues. Does anyone run AS and the index on separate servers, and 
if so, have you seen substantial AS performance increases from doing so? We’ve 
found that sometimes our installation slows down after running for a couple of 
months on the same server as the index.

Patrick Galligan
Digital Archivist
Rockefeller Archive Center
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Jobs indexing error

[Galligan, Patrick]

Blake,

Yeah, I’m guessing that the `asck` plugin we installed to check data a year ago 
makes those jobs invalid if the plugin isn’t installed.

Which is annoying.

Thanks for the help!

From:  on behalf of 
Blake Carver 
Reply-To: Archivesspace Users Group 

Date: Tuesday, August 25, 2020 at 9:31 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Jobs indexing error

***External*** This email originated from outside of the organization. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.***


 You could just get rid of the aspace_check_job jobs. (back up the DB just in 
case)

select * job where job_blob like '%aspace_check_job%';

Then:

delete FROM job where job_blob like '%aspace_check_job%';




From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Galligan, Patrick 
Sent: Tuesday, August 25, 2020 9:05 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Jobs indexing error


Hi all,



Posting here in the off chance someone has run into this before. We’re testing 
out AS version 2.8, coming from 2.6.0 and running into a weird issue.



Indexing works fine until we get to the job records section of indexing, and 
then we run into an unhandled exception ultimately stops indexing from 
finishing, and it just starts up again at resource records after finishing the 
jobs.



I’ve attached the relevant section of our log.



Any ideas on how to fix this? I could just delete all of our job records from 
the table, but that seems like a bad solution to this issue.



Thanks,

Patrick Galligan

He/Him

Digital Archivist

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

[Archivesspace_Users_Group] Jobs indexing error

[Galligan, Patrick]

Hi all,

Posting here in the off chance someone has run into this before. We’re testing 
out AS version 2.8, coming from 2.6.0 and running into a weird issue.

Indexing works fine until we get to the job records section of indexing, and 
then we run into an unhandled exception ultimately stops indexing from 
finishing, and it just starts up again at resource records after finishing the 
jobs.

I’ve attached the relevant section of our log.

Any ideas on how to fix this? I could just delete all of our job records from 
the table, but that seems like a bad solution to this issue.

Thanks,
Patrick Galligan
He/Him
Digital Archivist
Rockefeller Archive Center


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

[Archivesspace_Users_Group] Indexing never finishes?

[Galligan, Patrick]

Hey all,

We recently ran into something that we thought was an indexing issue in AS 
version 2.6.0, so we decided to delete our index and restart.

However, we’ve now run into an issue where the resources never finish indexing. 
I am seeing some errors in the log with indexer worker threads failing, but 
we’re not sure why, or how to fix it.

Any thoughts would be appreciated, because it’s starting to impact staff work.

Thanks!

Here’s an example of one of the errors:

E, [2019-11-05T13:31:27.413746 #10252] ERROR -- : Thread-2022: 
uri:classloader:/jsonmodel_client.rb:489:in `all'
/as_2.6.0/archivesspace/data/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/WEB-INF/app/lib/periodic_indexer.rb:231:in
 `fetch_records'
/as_2.6.0/archivesspace/data/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/WEB-INF/app/lib/periodic_indexer.rb:57:in
 `block in start_worker_thread'
/as_2.6.0/archivesspace/data/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/WEB-INF/app/lib/indexer_timing.rb:33:in
 `time_block'
/as_2.6.0/archivesspace/data/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/WEB-INF/app/lib/periodic_indexer.rb:56:in
 `block in start_worker_thread'
E, [2019-11-05T13:31:27.414622 #10252] ERROR -- : Thread-2022: #___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ArchivesSpace Integrations Survey

[Galligan, Patrick]

Hi all,

The ArchivesSpace Technical Advisory Council’s Integrations subteam has been 
working on a survey to gather more information about desired systems 
integrations with ArchivesSpace and we’d be extremely grateful if you filled it 
out. The survey should only take 10-15 minutes at most.

You can find the survey here: https://forms.gle/VR6UwqqQ4SXfyKav6

Please fill out this survey if you have any interest at all in ASpace software 
integrations. You do not have to be a member institution or currently be using 
ASpace.

The results of this survey will help you and the ASpace community. Our goals 
are to:
 1) produce anonymized public findings about what integrations the 
community wants and
 2) identify and facilitate integrations collaborations with partners.

It's important to note that the results of this survey alone will not determine 
what integrations work gets done and by whom. But, we have high hopes that the 
results will inform and drive future community work.

Once again, you can find the survey here.

Let us know if you have any questions or concerns. Thanks!

--
Patrick Galligan
Digital Archivist
Rockefeller Archive Center
(914) 366-6386
He/Him/His
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] TAC Integrations Introduction

[Galligan, Patrick]

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?”
 page, and we have a few examples of existing integrations on our team’s 
“Integrations”
 page. We also have documentation about 
“How”
 and 
“Why”
 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_integrati...@lyralists.lyrasis.org
 or fill out our ArchivesSpace Integrations 
Form.


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
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] External identifiers in agents

[Galligan, Patrick]

Corey,

Looks like the record ids in the model have basically the same model as 
external ids. Do you know if there’s a timeline for this development?

-Patrick

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

Date: Wednesday, April 10, 2019 at 3:16 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] External identifiers in agents


Patrick,



The upcoming Agents module revision 
(https://archivesspace.atlassian.net/browse/ANW-429) includes an Alternative 
Set section that allow links to other authority records, which might be useful 
when it is finished. If you are just interested in a simple link, though, the 
External Documents section does allow recording a link that is currently 
available in the PUI display. Do either of these approaches meet your need, or 
what else might be needed?



When you mentioned that there is a place for recording external identifiers for 
terms, was this in the Subjects module? There is a pending ticket to allow URIs 
to be recorded for controlled terms 
(https://archivesspace.atlassian.net/browse/ANW-355​), but I hadn't heard that 
there had been any progress in this area.



Best,



Cory Nimer

University Archivist

Brigham Young University

801-422-6091


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Galligan, Patrick 
Sent: Wednesday, April 10, 2019 8:28 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] External identifiers in agents

Hey all,

We were just looking at the models in AS and noticed that the backend models 
for Terms, Resources, Objects, etc. supported external identifiers (even if the 
GUI doesn’t), and we found it kind of weird that the Agents module doesn’t.

We’d love to have the ability to link out to a DBPedia or Wikidata entry for an 
agent without having to add an extraneous Name Form and Source just for that 
information. It doesn’t feel like a good way to go about doing that. Can anyone 
foresee any issues with something like this? Would you be in support of this 
being added to the Agents model? It appears to be a fairly easy change, even if 
it is a database change.

Thoughts?

-Patrick

--
Patrick Galligan
Digital Archivist
Rockefeller Archive Center
(914) 366-6386
He/Him/His
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] External identifiers in agents

[Galligan, Patrick]

Hey all,

We were just looking at the models in AS and noticed that the backend models 
for Terms, Resources, Objects, etc. supported external identifiers (even if the 
GUI doesn’t), and we found it kind of weird that the Agents module doesn’t.

We’d love to have the ability to link out to a DBPedia or Wikidata entry for an 
agent without having to add an extraneous Name Form and Source just for that 
information. It doesn’t feel like a good way to go about doing that. Can anyone 
foresee any issues with something like this? Would you be in support of this 
being added to the Agents model? It appears to be a fairly easy change, even if 
it is a database change.

Thoughts?

-Patrick

--
Patrick Galligan
Digital Archivist
Rockefeller Archive Center
(914) 366-6386
He/Him/His
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Thai names in Finding Aid PDF

[Galligan, Patrick]

Ed,

I believe there have been other issues regarding diacritics in general, but we 
can always merge tickets if you submit another.

This is very bad.

-Patrick Galligan
Digital Archivist
Rockefeller Archive Center

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Busch, 
Edward
Sent: Thursday, January 24, 2019 12:53 PM
To: 'archivesspace_users_group@lyralists.lyrasis.org' 

Subject: [Archivesspace_Users_Group] Thai names in Finding Aid PDF

I'm not sure if there is an open ticket on this or not; a quick search didn't 
reveal anything directly.

Agents with Thai names and diacritics look correct in ASpace but when generated 
into a PDF finding aid, do not. They end up like:
Saph# K#ns#ks# h#ng Ch#t

I can create a ticket if needed.

Ed Busch, MLIS
Electronic Records Archivist
Michigan State University Archives
Conrad Hall
943 Conrad Road, Room 101
East Lansing, MI 48824
517-884-6438
busch...@msu.edu

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

Re: [Archivesspace_Users_Group] Mismatch between index logs and Staff UI

[Galligan, Patrick]

We only have one repo, so definitely not. But some were made through the API. 
However, some were made by hand. No real ideas from our end except the indexer 
just messed up?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Tang, 
Lydia
Sent: Monday, December 03, 2018 2:22 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Mismatch between index logs and Staff 
UI

Just a quick note to say that we have a couple of *collections* that have this 
same issue.  Every time we upgrade, I know that I need to dig through transfer 
logs (at some point, I had transferred them between our students’ data entry 
locked down repository to our production repo and since then, they always 
“disappear”) and have to edit and save them.   Did any of those Dos happen to 
do a repo transfer?
:/
Lydia
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Mismatch between index logs and Staff UI

[Galligan, Patrick]

All,

Bear with me because I am an indexing neophyte.

We just upgraded to AS 2.5.1 and did a complete re-index of our repository. The 
logs of the index show everything completing successfully, however, the staff 
UI shows 25 fewer digital objects than the amount the index showed. 
Additionally, the staff UI does not show objects that we know are there. We can 
go to specific linked archival objects, and digital objects are associated with 
them that don’t show up in the browse panel.


  *   I, [2018-11-30T17:09:51.953278 #25679]  INFO -- : Thread-2016: Staff 
Indexer [2018-11-30 17:09:51 -0500] Indexed 2346 records in 18 seconds
  *   However the UI shows 2321 available digital objects

Everything is published, so nothing should be hidden. Additionally, if we 
manually edit and then save the “missing” objects, the indexer picks them up 
and they show up in the browse pane. We think the system could have just messed 
up on these, but we want to be sure.

These are also the 25 most recent Digital Objects as far as we can tell. We 
haven’t seen any errors in the indexer related to this either.

Has anyone else run into anything like this before? Is it possible to re-index 
just the Digital Objects, or do we have to perform a complete re-index?

Patrick Galligan
Rockefeller Archive Center


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

Re: [Archivesspace_Users_Group] Manage User Access version 2.5.0

[Galligan, Patrick]

Yeah, that looks like it.

Thanks for pointing me in the right direction! Just noticed it and wanted to 
make sure it was expected!

From:  on behalf of 
Dallas Pillen 
Reply-To: Archivesspace Users Group 

Date: Friday, September 14, 2018 at 11:29 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Manage User Access version 2.5.0

Hi Patrick,

Are the only users for which you are unable to "Edit groups" other 
administrators? If so, it looks like this was a change introduced by this pull 
request: 
https://github.com/archivesspace/archivesspace/commit/29bd91135626fb6a911bf65269167f6a9c4d79cd#diff-a3896310fef308a3755090d3590e0ce7

From the commit message:

"Prevents group assignment for 'admin' users. They already have all the
privileges so groups are unnecessary, but this prevents a side effect
where an 'admin' user (including the global admin) can lose admin group
permissions if they are assigned to a group by another admin level user."





On Fri, Sep 14, 2018 at 11:18 AM, Galligan, Patrick 
mailto:pgalli...@rockarch.org>> wrote:
Blake,

Interesting. We’re still on 2.3.2 on production, and we were going to skip 2.4 
entirely, so I haven’t done any testing on those versions.

I should have attached a screenshot, so I have now. Any insight on why this 
might be happening?

-Patrick

On 9/14/18, 11:12 AM, 
"archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 on behalf of Blake Carver" 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 on behalf of blake.car...@lyrasis.org<mailto:blake.car...@lyrasis.org>> wrote:

I do see that same thing under 2.4.1 as well. I have the same DB running 
under 2.5 and 2.41 and I can't touch the same users in both versions.


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Galligan, Patrick 
mailto:pgalli...@rockarch.org>>
Sent: Friday, September 14, 2018 10:54:55 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0

Hi all,

I’m testing out version 2.5.0 and I’m noticing that I can’t “Edit Groups” 
for some members under the “Manage User Access” page. I am logged in as an 
admin user, and logging in as a different admin user doesn’t help.

I also checked on the 
sandbox.archivesspace.org<http://sandbox.archivesspace.org> installation and 
noticed that the one user available can’t edit their own groups either.

Anyone else seeing this?

Thanks,
Patrick Galligan
___
Archivesspace_Users_Group mailing list

Archivesspace_Users_Group@lyralists.lyrasis.org<mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


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



--
Dallas Pillen
Archivist for Metadata and Digital Projects

[https://webapps.lsa.umich.edu/dean/lsa_emails/bentley-sig-em.png]
  Bentley Historical Library<http://bentley.umich.edu/>
  1150 Beal Avenue
  Ann Arbor, Michigan 48109-2113
  734.647.3559
  Twitter<https://twitter.com/umichBentley> Facebook 
<https://www.facebook.com/bentleyhistoricallibrary>
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Manage User Access version 2.5.0

[Galligan, Patrick]

Blake,

Interesting. We’re still on 2.3.2 on production, and we were going to skip 2.4 
entirely, so I haven’t done any testing on those versions.

I should have attached a screenshot, so I have now. Any insight on why this 
might be happening?

-Patrick

On 9/14/18, 11:12 AM, "archivesspace_users_group-boun...@lyralists.lyrasis.org 
on behalf of Blake Carver" 
 wrote:

I do see that same thing under 2.4.1 as well. I have the same DB running 
under 2.5 and 2.41 and I can't touch the same users in both versions.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Galligan, Patrick 
Sent: Friday, September 14, 2018 10:54:55 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Manage User Access version 2.5.0

Hi all,

I’m testing out version 2.5.0 and I’m noticing that I can’t “Edit Groups” 
for some members under the “Manage User Access” page. I am logged in as an 
admin user, and logging in as a different admin user doesn’t help.

I also checked on the sandbox.archivesspace.org installation and noticed 
that the one user available can’t edit their own groups either.

Anyone else seeing this?

Thanks,
Patrick Galligan
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


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

[Archivesspace_Users_Group] Manage User Access version 2.5.0

[Galligan, Patrick]

Hi all,

I’m testing out version 2.5.0 and I’m noticing that I can’t “Edit Groups” for 
some members under the “Manage User Access” page. I am logged in as an admin 
user, and logging in as a different admin user doesn’t help.

I also checked on the sandbox.archivesspace.org installation and noticed that 
the one user available can’t edit their own groups either.

Anyone else seeing this?

Thanks,
Patrick Galligan
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Tell us about your integrations

[Galligan, Patrick]

All,

Besides gathering information about desired integrations, the TAC integrations 
subteam is interested in hearing you talk about an integration you’re currently 
working on.

Doing integrations work currently? Planning to start an integration? We want to 
hear about it. Integrations would love to have you on one of our monthly calls 
to talk about how we can help you with your work.

Shoot me an email off list 
(pgalli...@rockarch.org) if you’re interested! 
We tried this with Litchfield Historical Society and thought it’d be great to 
get more people involved.

Thanks,
Patrick Galligan
Integrations Chair
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] ArchivesSnake Needs Your Help!

[Galligan, Patrick]

Just a reminder that ArchivesSnake is still looking for contributions to 
Github. We have about 2 weeks until our information gathering stage ends.

Please email if you have any questions at all.

-Patrick

From: "Galligan, Patrick" <pgalli...@rockarch.org>
Date: Thursday, December 7, 2017 at 2:13 PM
To: Archivesspace Users Group <Archivesspace_Users_Group@lyralists.lyrasis.org>
Subject: ArchivesSnake Needs Your Help!

Hi all,

I’m heading up a collaborative project that we’re calling ArchivesSnake. 
ArchivesSnake is attempting to create a Python Library of scripts for working 
with the ArchivesSpace API.

We’ve got a great team going, and we’re currently in the information gathering 
stage. If you’ve written a Python script to work with the AS API, we want to 
hear about it! We have a Github page: 
https://github.com/archivesspace-labs/ArchivesSnake, but you’ll need access to 
write to it.

We’re currently taking the approach of adding links to scripts in github repos, 
and you can use the RAC 
(https://github.com/archivesspace-labs/ArchivesSnake/blob/master/RAC_links.md) 
or U of Albany 
(https://github.com/archivesspace-labs/ArchivesSnake/blob/master/ualbanyExample.md)
 links for examples. If your code is not in Github yet, but you’re willing to 
share it, we’ll put it up on ArchivesSnake. If you want to add links yourself, 
please email me and I’ll add you as a Github collaborator. If you lack the time 
to add links yourself, or you’re just baffled by Github, email me links to your 
code, and I can put them up myself.

We’re closing the information-gathering stage on January 31st, 2018. Please 
contact us before then.

After we’ve gathered sufficient examples, we’ll start grouping like functions 
and try to find the best way to do everything. After which point we’ll start 
work on creating the open Python library for all your needs.

Let me know if you have any questions!

Best,
Patrick Galligan
Rockefeller Archive Center
Digital Archivist
pgalli...@rockarch.org
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ArchivesSnake Needs Your Help!

[Galligan, Patrick]

Hi all,

I’m heading up a collaborative project that we’re calling ArchivesSnake. 
ArchivesSnake is attempting to create a Python Library of scripts for working 
with the ArchivesSpace API.

We’ve got a great team going, and we’re currently in the information gathering 
stage. If you’ve written a Python script to work with the AS API, we want to 
hear about it! We have a Github page: 
https://github.com/archivesspace-labs/ArchivesSnake, but you’ll need access to 
write to it.

We’re currently taking the approach of adding links to scripts in github repos, 
and you can use the RAC 
(https://github.com/archivesspace-labs/ArchivesSnake/blob/master/RAC_links.md) 
or U of Albany 
(https://github.com/archivesspace-labs/ArchivesSnake/blob/master/ualbanyExample.md)
 links for examples. If your code is not in Github yet, but you’re willing to 
share it, we’ll put it up on ArchivesSnake. If you want to add links yourself, 
please email me and I’ll add you as a Github collaborator. If you lack the time 
to add links yourself, or you’re just baffled by Github, email me links to your 
code, and I can put them up myself.

We’re closing the information-gathering stage on January 31st, 2018. Please 
contact us before then.

After we’ve gathered sufficient examples, we’ll start grouping like functions 
and try to find the best way to do everything. After which point we’ll start 
work on creating the open Python library for all your needs.

Let me know if you have any questions!

Best,
Patrick Galligan
Rockefeller Archive Center
Digital Archivist
pgalli...@rockarch.org
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] batch delete dates saga continues

[Galligan, Patrick]

Hey all,

I think a great place to get started learning about Python, APIs, and 
ArchivesSpace would be some of the API tutorials that members of the 
ArchivesSpace community have taught.

Lora Woodford from JHU taught a workshop about 4 months ago and made the 
materials available on Github: 
https://github.com/jhu-archives-and-manuscripts/ASpace_API_Workshop.

Personally, I’ve found that I learn best by doing. So I learned what I did 
about the AS JSON responses by downloading Postman 
(https://www.getpostman.com/) and performing a few API calls against our 
development database. Also, back in 2014, Maureen Callahan and a few other 
archivists ran a blog about dealing with legacy data. They have some posts 
about AS API work. I personally liked this post as a beginner: 
https://icantiemyownshoes.wordpress.com/2014/08/01/a-very-brief-guide-to-deleting-records-with-the-archivesspace-api-from-a-total-tyro/.

This is a great resource for learning python: 
https://automatetheboringstuff.com/.

I’m sure there are a ton of other resources out there, but those are the few 
off the top of my head. I’m willing to jump in and give some more 
recommendations as needed.

-Patrick Galligan

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Margaret Kidd
Sent: Friday, November 10, 2017 5:31 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

I second that last part of Lydia's remarks about where to begin learning more 
about XML, JSON, python, ruby, etc. and applying it to ArchivesSpace. I want to 
learn, but it is overwhelming to know where to begin and my time to devote to 
it is rather limited. Every time I start trying to teach myself I have other 
work priorities that take up all my time and soon forget whatever progress I 
have made.

Thanks,

Margaret




Margaret T. Kidd

Project Archivist, Special Collections & Archives

VCU Libraries | Tompkins-McCaw Library for the Health Sciences

509 N. 12th Street / Box 980582, Richmond, VA 23298-0582

(804) 828-3152
[em_twitter.png][em_fb.png]


[http://identity.vcu.edu/images/photos/vcu_brand_mark_email_sig.jpg]
 
[http://pages.shanti.virginia.edu/Virginia_Heritage/files/2013/01/vhpban.jpg] 



On Fri, Nov 10, 2017 at 12:02 PM, Tang, Lydia 
> wrote:
Mark,
Thank you for identifying my problem!  Just for the sake of technological 
dummies like me, what should I do?  Everything there (besides removing the 
 tags is exactly as it spat out of ArchivesSpace, so I wonder if the 
export allowed the invalid characters?  I also wonder if the importing process 
could be improved within the ArchivesSpace code to search for “aspace_" and not 
batch add it as well as recognize (or not export out in the first place) the 
"Linear Feet" / linear_feet controlled vocabulary?  Ideally, after establishing 
with the database that linear_feet should publish as Linear Feet, I wish it 
would continue to recognize that rule when new stuff is imported in.
I was also meaning poll people on “how do I even get started” with learning 
more about working the ArchivesSpace guts?  I can understand EAD but obviously 
don’t know the wizardry possible with XML, there’s JSON, python, etc, and I 
would be interested in starting courses with Code Academy to learn, but I don’t 
even know where to begin.  Advice appreciated!
Lydia

From: 
>
 on behalf of "Custer, Mark" >
Reply-To: Archivesspace Users Group 
>
Date: Friday, November 10, 2017 at 11:50 AM
To: Archivesspace Users Group 
>
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

Lydia,

In the EAD files that you attached, both have invalid XML characters in them 
(Unicode: 0x14).  Those are easy to remove before re-importing in an XML editor 
like oXygen, but I'm curious how they got into ASpace in the first place?   In 
any event, it's possible that that's what's blocking your imports this time 
around, and if that's the issue, if you just fix on those issues, then the 
ASpace importer won't tell you about the next issue until it runs again.

In any event, I'd also suggest making  the following changes to your XML file 
before re-importing, so perhaps the snag is a good thing for now  :

· ASpace adds "aspace_" to all of the @id values in the EAD file upon 

Re: [Archivesspace_Users_Group] Deleting Empty Top Containers

[Galligan, Patrick]

Hey Suzanne,

We have automated this process for the most part.

If you want to have a method to just delete all orphaned top containers, you 
chan check out this Python script I wrote up really quickly: 
https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asDeleteOrphanContainers.py

Let me know if you have any questions.

From:  on behalf of 
"Custer, Mark" 
Reply-To: Archivesspace Users Group 

Date: Sunday, September 17, 2017 at 2:09 PM
To: "archivesspace_users_group@lyralists.lyrasis.org" 

Subject: Re: [Archivesspace_Users_Group] Deleting Empty Top Containers


Hi, Suzanne.



Yep, that's exactly the way to do it, and exactly why the "unassociated" option 
was added.



Since top containers are scoped to repositories, though, if you have multiple 
repositories in your installation, then you'll need to perform this action 
within each repository.  We've assigned this cleanup task as something that our 
repository managers should do on a periodic basis.



We haven't decided to automate this task yet, however, which I guess gives us 
the opportunity to make sure that everything looks okay before activating the 
bulk delete option.  That said, I think that automating this on a periodic 
basis outside of normal business hours could be the way to go.  We had 
originally hoped that orphaned top containers could never be created in the 
staff application, but given that they can be associated with different 
resource, accession, and archival object records, it would be a bit tricky to 
do that, so orphaned, or unassociated, top containers will be created if an 
entire resource record is deleted, for instance.  Same thing happens right now 
for digital object records; the only difference there is that digital objects 
can also be created as stand-alone records in the staff interface, whereas you 
can't do that with top containers (without using the API).



Mark


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Stasiulatis, Suzanne 
Sent: Saturday, September 16, 2017 1:55:14 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Deleting Empty Top Containers

Hello,

I am working in ArchivesSpace version 1.5.4. I’d like to delete all of our 
empty top containers through the staff interface. By empty, I mean top 
containers that aren’t linked to any archival objects. I believe we created 
containers in the archival object page and then unlinked them at some point.

In Manage Top Containers, you can choose Yes for Unassociated containers and 
leave all other fields blank. This gives us a very long list. Can anyone 
confirm that this list includes all of our empty top containers and only our 
empty top containers?

[cid:image001.png@01D3305D.44B4D5B0]

Thanks!

Suzanne

Suzanne Stasiulatis | Archivist II
Pennsylvania Historical and Museum Commission | Pennsylvania State Archives
350 North Street | Harrisburg, PA 17120-0090
www.phmc.pa.gov/Archives
sustasi...@pa.gov

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

Re: [Archivesspace_Users_Group] Python ArchivesSpace scripting library

[Galligan, Patrick]

Thanks for all the feedback and offers of help!

I’m going to talk to Christine and Laney hopefully sometime this week, and then 
we can get started for real. I think Dave’s on the right track that the first 
thing would be to gather a corpus of examples/functionality that we’d like to 
include.

I’ll update everyone soon.

Thanks,
Patrick

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Max Eckard
Sent: Monday, August 07, 2017 11:25 AM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Python ArchivesSpace scripting library

This is an idea we've toyed around with as well--I'm sure one or more of us 
could contribute, too. Keep us posted!
Max

On Thu, Aug 3, 2017 at 1:48 PM, Jason Loeffler 
<j...@minorscience.com<mailto:j...@minorscience.com>> wrote:
Don't want to add any overhead to this but at one point late last year I recall 
a proposal from Max Eckard, Esmé, Sally V., et al. for an 
Awesome<https://github.com/sindresorhus/awesome>-style list to house these 
kinds of projects. Establishing such a list and collecting the prior art there 
might be a good way to help set both projects in motion.

And +1, I can contribute.

On Thu, Aug 3, 2017 at 11:48 AM, Majewski, Steven Dennis (sdm7g) 
<sd...@virginia.edu<mailto:sd...@virginia.edu>> wrote:

+1 :  I can contribute as well.



-- Steve Majewski / UVA Alderman Library

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
<archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Seth Shaw <seth.s...@unlv.edu<mailto:seth.s...@unlv.edu>>
Sent: Thursday, August 3, 2017 11:38:20 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Python ArchivesSpace scripting library

I'm interested in this too. I was doing some python scripting just
this week 
(https://github.com/seth-shaw-unlv/small-stuff/blob/master/as-coll-mint/as_coll_mint.py#L85-L117),
if you want to throw that on the prior art pile.

Also for the prior art pile: I know the folks at the Rubenstein (Duke)
have also done a good deal of ArchivesSpace python scripting (see
http://blogs.library.duke.edu/bitstreams/2016/09/21/archivesspace-api-fun/
and 
https://github.com/duke-libraries/archivesspace-duke-scripts/tree/master/python).

On Thu, Aug 3, 2017 at 6:47 AM, Mayo, Dave 
<dave_m...@harvard.edu<mailto:dave_m...@harvard.edu>> wrote:
> One thing I think might be useful, especially in planning stages, is
> collecting the “prior art” in one place to look at – because there are a lot
> of scripts people have built around the API, and they probably capture at
> least a fair bit of “what people want to do most with the API.”
>
> So, whenever the github is set up, we should do this.
>
> - Dave
>
>
>
> From: 
> <archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
>  on behalf of
> "rsdo...@caltech.edu<mailto:rsdo...@caltech.edu>" 
> <rsdo...@library.caltech.edu<mailto:rsdo...@library.caltech.edu>>
> Reply-To: "rsdo...@caltech.edu<mailto:rsdo...@caltech.edu>" 
> <rsdo...@caltech.edu<mailto:rsdo...@caltech.edu>>, Archivesspace Users
> Group 
> <archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Date: Thursday, August 3, 2017 at 9:21 AM
> To: Archivesspace Users Group
> <archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: Re: [Archivesspace_Users_Group] Python ArchivesSpace scripting
> library
>
>
>
> Hello Patrick,
>
>
>
> I have written some tools in go and mocked up functionaity in Python a few
> years ago I'd be interested in the project.
>
>
>
> Robert Doiel
>
> Caltech Library
>
> rsdo...@caltech.edu<mailto:rsdo...@caltech.edu>
>
>
>
> On Aug 3, 2017 6:10 AM, "Galligan, Patrick" 
> <pgalli...@rockarch.org<mailto:pgalli...@rockarch.org>> wrote:
>
> Hi all,
>
>
>
> For a while now the RAC has been bouncing around the idea of developing an
> AS Python library that would hold a lot of the functions we find ourselves
> working with a lot when scripting against the AS API. I know Greg Wiedeman
> at U Albany has done some work to this end, but I wanted to send a blast out
> to the list to see who else might be interested. We’d love to make this as
> collaborative and exhaustive as poss

Re: [Archivesspace_Users_Group] Issue with 2.1.0 upgrade

[Galligan, Patrick]

Christine,

I don’t know if it was our server running slow or something, but I just tested 
our first initial upgrade to 2.1.0 from 2.0, and the indexing took almost a 
full week. In the past it used to take 36-48 hours and we could be done over 
the weekend.

I think I’d like to test everything again before conclusively saying that’s how 
long it takes, but it seemed like a drastic increase in time.

-Patrick Galligan

From:  on behalf of 
Christine Di Bella 
Reply-To: Archivesspace Users Group 

Date: Friday, August 4, 2017 at 5:26 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Issue with 2.1.0 upgrade

Hi Dale,

Just to let you know, the ArchivesSpace team is looking into this and a few 
other reports about performance or difficulty indexing when upgrading to 2.1.0. 
We hope to have more information soon, though so far these are somewhat 
isolated incidents. We’re definitely interested to hear if others are having 
similar experiences when upgrading to 2.1.0.

We do know that the initial indexing period takes longer with 2.1.0, and we 
know of at least one institution that need to do a small amount of data cleanup 
because some bad data that was ignored in previous versions was preventing 
indexing from completing.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[SpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Poulter, Dale
Sent: Tuesday, August 1, 2017 8:37 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Issue with 2.1.0 upgrade

Good evening,

We upgraded from 2.0.1 to 2.1.0 earlier today.  The upgrade appeared to go well 
with no errors generated during the database setup stage.  However,  it still 
seems to be generating many calls to the database.  Is this expected behavior? 
When we upgraded to 2.0.1 the we had similar behavior but that only lasted for 
an hour or less.

Thank you for your help!


--Dale

---
Dale Poulter
Coordinator, Search and Core Services
Library Digital Services
Vanderbilt University
419 21st Avenue South, Room 812
Nashville, TN  37203-2427
(615)343-5388
(615)207-9705 (cell)
dale.poul...@vanderbilt.edu


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

Re: [Archivesspace_Users_Group] Travis CI and ArchivesSpace

[Galligan, Patrick]

Jason,

Cool! I’m thinking that we’d probably be forking AS based upon our own codebase 
because of some pretty minor local customizations that are set up as plugins. 
We have some things that change layouts, changes to exporters, etc., and we 
want to do our due diligence in making sure that we’re not unexpectedly 
breaking something with each new release. Thought we could do it through 
automated methods rather than checking each plugin by hand each time.

-Patrick

From: <archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of 
Jason Loeffler <j...@minorscience.com>
Reply-To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org>
Date: Friday, July 28, 2017 at 9:22 PM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Travis CI and ArchivesSpace

Hi Patrick,

I use a CI test harness regularly with Drupal development. Are you looking to 
fork AS and customize your code base and deploy that or do you simply want to 
write tests for the existing production branch?

--
Jason Loeffler
Technology Consultant | The American Academy in Rome
Minor Science | Application Development & Metadata Strategy
Brooklyn, New York
ja...@minorscience.com<mailto:ja...@minorscience.com>
(347) 405-0826
minorscience (Skype)
_________
From: Galligan, Patrick <pgalli...@rockarch.org<mailto:pgalli...@rockarch.org>>
Sent: Friday, July 28, 2017 16:07
Subject: [Archivesspace_Users_Group] Travis CI and ArchivesSpace
To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>



Hey List,

I’m pretty new to Continuous Integration and scripted testing, so I thought I’d 
email the list. Anyone using TravisCI to create automated tests and to 
integrate with their ArchivesSpace production? I’m trying to up our software 
deployment game and could use some tips and tricks if you have them.

Let me know!

Patrick Galligan
Rockefeller Archive Center

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

[Archivesspace_Users_Group] Travis CI and ArchivesSpace

[Galligan, Patrick]

Hey List,

I’m pretty new to Continuous Integration and scripted testing, so I thought I’d 
email the list. Anyone using TravisCI to create automated tests and to 
integrate with their ArchivesSpace production? I’m trying to up our software 
deployment game and could use some tips and tricks if you have them.

Let me know!

Patrick Galligan
Rockefeller Archive Center
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] merging/fixing duplicate top containers

[Galligan, Patrick]

Ben,

So, uh, we had some of the same issue. We generally identified that you need at 
least one barcode to realistically do it in our case. We have two scripts.

1. This one is for resources where the Box numbers don't restart at 1 every 
series. It won't work if you have two separate box 1s. We know the script is a 
little messy, but we haven't had the chance to test a refactor. It basically 
matches based on logic around our barcodes. You could change this to match 
around other logic as necessary. Like you might be able to split your 
indicators and match based off of those. We did barcodes because we had faux 
codes after migration and it was the easiest way to identify the "real" 
container. 
https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asAutoReplaceContainers.py

2. This you can use on resources that restart numbers. It's pretty manual, and 
you have to create a Csv first, but it gets the job done. 
https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asReplaceContainers.py

There should be documentation in the repo, but let me know if you get stuck.

-Patrick Galligan

Sent with BlackBerry Work
(www.blackberry.com)

From: Ben Goldman >
Date: Thursday, Jun 29, 2017, 3:52 AM
To: Archivesspace Users Group 
>
Subject: [Archivesspace_Users_Group] merging/fixing duplicate top containers

Hello,

Without realizing it, we migrated a considerable number of poorly encoded 
instances into ASpace 1.5 and its new container model. We're trying to figure 
out how best to deal cases like the one in the screenshot below, where 
historical practice has found us encoding box and folder numbers in a single 
instance, with values separated by a slash. Until a merge feature is 
implemented, it looks like we may have to do this through the API, and I'm 
wondering if anyone has tackled something similar and can possibly share a 
solution.

[cid:0adb6e00e3d922e8cd87529d47fe6d5a6e97f6b0@zimbra]

Thanks much,
Ben

Ben Goldman
Digital Records Archivist &
Sally W. Kalin Early Career Librarian for Technological Innovations
Penn State University Libraries
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Version 2.0.1 differences in indexing and display?

[Galligan, Patrick]

Laney,

Yep, it seems to work wrapped in quotations. Thanks for looking into this for 
us.

I’m definitely interested in hearing how that giant empty subject appeared.

-Patrick

From: Laney McGlohon <laney.mcglo...@lyrasis.org>
Date: Thursday, May 18, 2017 at 9:21 AM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Cc: "Galligan, Patrick" <pgalli...@rockarch.org>
Subject: Re: [Archivesspace_Users_Group] Version 2.0.1 differences in indexing 
and display?

Hey Patrick,

As you know, I have been looking into what you are seeing as described below.

I am still waiting for the indexing of the data for v2.0.1 to finish but would 
like to give you some information that I have discovered so far:

1.  Sorting order has changed, so now !Kung is interfiled with the K’s – 
see attached subjects list screen shot.

2.  In order to use search to find items that have been linked to the !Kung 
subject, it needs to be wrapped in quotes (“!Kung”), otherwise, solr interprets 
“!” as a logical NOT. When it is wrapped in quotes, you will also get results 
from other records with the string “Kung”. Can you try the search in your 
current version and make sure it works? Also, can you do the same search with 
an agent that starts with “!”? Since they do not display at the top of the 
subjects and agents browse, it is difficult for me to find examples.

I am looking into the empty subject. Once the indexing for v2.0.1 has finished, 
I can do more of an in-depth analysis of where that is coming from.

Stay tuned for more information!

Best,
Laney

Laney McGlohon
ArchivesSpace Tech Lead
laney.mcglo...@lyrasis.org<mailto:laney.mcglo...@lyrasis.org>
800.999.8558 x2927
laneymcglohon Skype



From: <archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of 
"Galligan, Patrick" <pgalli...@rockarch.org>
Reply-To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org>
Date: Tuesday, May 16, 2017 at 9:36 AM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Version 2.0.1 differences in indexing and 
display?

Hi all,

I finally finished getting a full index and installation of 2.0.1 on our 
development server up and running, and the record numbers (accession, 
resources, subjects, and agents) seem to match our production server exactly.

However, in a few cases with subjects and agents, I’m not seeing records 
starting with special characters showing up in the search index and don’t 
display in the list of all subjects. However, they are still attached to their 
respective resource records, and still have full subject or agent records in 
the system.

For instance, we have a subject “!Kung (African people)”. In version 1.5.3 this 
subject appears in the subject list, but in version 2.0.1 we just get an empty 
box, even though indexing has completed successfully. See the attached 
screenshots. And then when I click on this “empty” subject, I can see it’s 
attached to 1,024,044 different archival objects, which is definitely not 
correct (see attached screenshot).

We also seem to be missing any subjects or agents starting with quotation marks.

Was there a change in indexing/display behavior with the newest 2.0.1 releases? 
It’s fairly troubling to me that we wouldn’t be able to have special characters 
starting our subjects. And I have no idea why we would suddenly have an empty 
subject record attached to over 1 million archival objects.

We’d really like to move forward with our 2.0.1 upgrade, but we definitely 
couldn’t before working out these issues. It totally might be something weird 
on our end of the database, but we’d love to hear about a way to fix it!

Best,
Patrick Galligan
Rockefeller Archive Center
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Deleted resource record

[Galligan, Patrick]

I don’t know if it is an issue with 2.0.1, but we definitely ran into it once 
with 1.5.3.

Looks like it still exists.

-Patrick Galligan
Rockefeller Archive Center

From:  on behalf of 
"Mummey, Megan" 
Reply-To: Archivesspace Users Group 

Date: Wednesday, May 17, 2017 at 11:02 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Deleted resource record

Hi all,

UK upgraded to version 2.0.1 last Friday. This morning a student was working 
with a very large resource and hit refresh when Archivesspace timed out. This 
seems to have deleted the entire resource. I’m just wondering if this is a 
known issue with version 2.0.1. We are finding it very concerning, so any help 
would be appreciated.

Thanks,

Megan Mummey
Collections Management Archivist
Special Collections Research Center
University of Kentucky Libraries
Margaret I. King Library
Lexington, KY  40506-0039
megan.mum...@uky.edu|859.257.6942



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

Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

[Galligan, Patrick]

Bria,

I can’t tell you where exactly this is happening, but mismatch between 
indicators usually means that you have two different top container indicators 
assigned to the same barcode.

You’d have to look at the barcodes that are already in the system, and any 
indicators associated with the import. I don’t see anything wrong in the 
snippet you sent below, but I also don’t really know what’s already in your 
database.

We had a lot of these errors when we migrated to 1.5.0.

-Patrick Galligan

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Bria Lynn Parker
Sent: Tuesday, January 24, 2017 11:10 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

I should add:

I'm running 1.5.2, and I have checked for sneaky whitespaces within any of 
these attributes and have found none.

On Tue, Jan 24, 2017 at 11:06 AM, Bria Lynn Parker 
> wrote:
Hi all - I'm hoping someone has a tip or hint at where I'm going wrong:

We've finished cleaning up/normalizing our EAD (including implementing 
container attributes and the like for container management). The majority are 
importing fine, no errors (or, at least no errors I can't find and fix, like 
bad begin/ends). However, for some of our finding aids, I'm getting the 
following:

indicator_1 : Mismatch when mapping between indicator and indicator_1

No other info about location, etc. I've about torn my hair out trying to find 
any mismatch of container data - I've checked every instance's dummy barcode 
(which is constructed in part from the id), id, and parent against itself, 
crosschecked with the container indicator, and they all match within 
themselves. We're importing barcodes in the label attribute, which
works (except when it doesn't here?). The error message getting thrown is from 
this ruby function 
https://github.com/archivesspace/archivesspace/blob/5e1ca66f1f04f142f2695024efb7200825046325/backend/app/lib/aspace_json_to_managed_container_mapper.rb#L173

Help? If someone has encountered this and figured it out, let me know - I'd 
love some help. If you want to contact me off list, I can sent you a full xml 
file.
Here's an example from my xml:


  
Financial Records -- General -- Bound Volumes -- 
Financial Reports
1905-1908
1
1.0
  


   
  
Financial Records -- General -- Bound Volumes -- 
Financial Reports
1909
1
2.0
  



  
Financial Records -- General -- Bound Volumes -- 
Financial Reports
1910-1911
1
3.0
  


(historical background - some of our series restart box numbers at 1, and the 
container ids reflect that, so 89.1 is the 89th box in the collection, but 1st 
in the series. This is not causing the error as far as I can tell, since other 
collections with same numbering style import fine)


--
Bria L. Parker
Metadata Librarian

2200 McKeldin Library

University of Maryland

College Park, MD 20742-7011

(301) 405-9067

blpar...@umd.edu



--
Bria L. Parker
Metadata Librarian

2200 McKeldin Library

University of Maryland

College Park, MD 20742-7011

(301) 405-9067

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

[Archivesspace_Users_Group] Container type in EAD export

[Galligan, Patrick]

Hi all,

We've noticed that when no container type is selected in version 1.5.1, the EAD 
exporter automatically assigns the container a type of 'box'.

Is this intended behavior? I'd guess not since the container type is not a 
required field in the top container functionality.

Patrick Galligan
Rockefeller Archive Center
Digital Archivist
914-366-6386

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

Re: [Archivesspace_Users_Group] OAI-PMH?

[Galligan, Patrick]

Thanks!

Patrick Galligan
Rockefeller Archive Center
Assistant Digital Archivist
914-366-6386

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Brad Westbrook
Sent: Friday, August 12, 2016 10:36 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] OAI-PMH?

It does not, Patrick.

We have the BYU specification but have not been able to move forward with it.

Brad


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Galligan, Patrick
Sent: Friday, August 12, 2016 10:26 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] OAI-PMH?

Hi all,

I saw this JIRA ticket recently: 
https://archivesspace.atlassian.net/browse/AR-803 but it looks like it's still 
unresolved.

Can someone confirm that AS does not currently support OAI-PMH for me?

Thanks,

Patrick Galligan
Rockefeller Archive Center
Assistant Digital Archivist
914-366-6386

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