Re: [Archivesspace_Users_Group] Odd data modifications during aspace updates.

[Donald Mennerich]

Thank you James.

On Tuesday, March 10, 2020, James Bullen  wrote:
>
> Hi Don,
> Nested subrecords get recreated on every update. They arguably shouldn’t
have those audit fields.
>
> Cheers,
> James
>
> On Mar 11, 2020, at 8:45 AM, Donald Mennerich 
wrote:
> Hello,
>
> While testing a script that was updating a resource's ead_id via the api
I noticed that the timestamps for  most sub-records of the resource, e.g.
instances, extents, langmaterials, etc., that wern't part of the update
were havign their timesstamps, includeing create_time and created_by,
updated as well. I naturally assumed there was something wrong with my
code, but when we tested updating a resource record from the staff
interface the same thing happening was observed.
>
> For example, the fields belonging to the Resource model updated as
expected, the creation_time and created_by were not modified, while the
last_modified_by and mtimes were:
>
> Before
>>
>> {
>>   "lock_version": 1,
>>   "title": "Test Collection",
>>   "publish": true,
>>   "restrictions": false,
>>   "created_by": "admin",
>>
>>   "last_modified_by": "user1",
>>   "create_time": "2016-07-14T23:50:37Z",
>>   "system_mtime": "2018-03-29T22:05:59Z",
>>   "user_mtime": "2017-02-02T18:15:58Z",
>>
>>  ...
>
> After
>>
>> {
>> "lock_version": 2,
>>   "title": "Test Collection",
>>   "publish": true,
>>   "restrictions": false,
>>
>>   "ead_id": "test_999",
>>   "created_by": "admin",
>>
>>   "last_modified_by": "user2",
>>   "create_time": "2016-07-14T23:50:37Z",
>>   "system_mtime": "2020-03-10T17:29:46Z",
>>   "user_mtime": "2020-03-10T17:29:46Z",
>> ...
>
> But in most of the subrecords of the resource the timestamps have all
updated to the time of the update of the resource record. In this case the
only thing that was updated was in the resource record was the eadid, but
the instance subrecords had their timestamps updated even though not at all
part of the update. Note that while data was changed in the sub record the
lock_version is still at 0. Again, this was done with an update via the
staff interface.
>
> Before
>>
>> "instances": [
>>   {
>> "lock_version": 0,
>> "created_by": "user1",
>> "last_modified_by": "user1",
>> "create_time": "2017-02-02T18:15:58Z",
>> "system_mtime": "2017-02-02T18:15:58Z",
>> "user_mtime": "2017-02-02T18:15:58Z",
>> "instance_type": "mixed_materials",
>> "jsonmodel_type": "instance",
>> "is_representative": false,
>> "sub_container": {
>>   "lock_version": 0,
>>   "created_by": "user1",
>>   "last_modified_by": "user1",
>>   "create_time": "2017-02-02T18:15:58Z",
>>   "system_mtime": "2017-02-02T18:15:58Z",
>>   "user_mtime": "2017-02-02T18:15:58Z",
>>   "jsonmodel_type": "sub_container",
>
> After
>>
>> "instances": [
>>   {
>> "lock_version": 0,
>> "created_by": "user2",
>> "last_modified_by": "user2",
>> "create_time": "2020-03-10T17:29:47Z",
>> "system_mtime": "2020-03-10T17:29:47Z",
>> "user_mtime": "2020-03-10T17:29:47Z",
>> "instance_type": "mixed_materials",
>> "jsonmodel_type": "instance",
>> "is_representative": false,
>> "sub_container": {
>>   "lock_version": 0,
>>   "created_by": "user2",
>>   "last_modified_by": "user2",,
>>   "create_time": "2020-03-10T17:29:47Z",
>>   "system_mtime": "2020-03-10T17:29:47Z",
>>   "user_mtime": "2020-03-10T17:29:47Z",
>>   "jsonmodel_type": "sub_container",
>
>
> I'm trying to determine if this is a local problem or if this is just
normally how aspace manages updates, and if so is it a bug. Would someone
with access to the API of their ArchivesSpace instance see if they could
reproduce this? I've tested this on installations of v2.7.0 and v2.7.1.
>
> Thanks,
>
> Don
> !DSPAM:5e680a81236307999538416!
___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
> !DSPAM:5e680a81236307999538416!
>
>

-- 
Donald R. Mennerich, digital archivist
New York University Libraries
don.menner...@nyu.edu (212) 992-6264
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Odd data modifications during aspace updates.

[James Bullen]

Hi Don,

Nested subrecords get recreated on every update. They arguably shouldn’t have 
those audit fields.


Cheers,
James


> On Mar 11, 2020, at 8:45 AM, Donald Mennerich  wrote:
> 
> Hello, 
> 
> While testing a script that was updating a resource's ead_id via the api I 
> noticed that the timestamps for  most sub-records of the resource, e.g. 
> instances, extents, langmaterials, etc., that wern't part of the update were 
> havign their timesstamps, includeing create_time and created_by, updated as 
> well. I naturally assumed there was something wrong with my code, but when we 
> tested updating a resource record from the staff interface the same thing 
> happening was observed. 
> 
> For example, the fields belonging to the Resource model updated as expected, 
> the creation_time and created_by were not modified, while the 
> last_modified_by and mtimes were:
> 
> Before
> {
>   "lock_version": 1,
>   "title": "Test Collection",
>   "publish": true,
>   "restrictions": false,
>   "created_by": "admin",
>   "last_modified_by": "user1",
>   "create_time": "2016-07-14T23:50:37Z",
>   "system_mtime": "2018-03-29T22:05:59Z",
>   "user_mtime": "2017-02-02T18:15:58Z",
>  ...
> 
> After
> {
>   "lock_version": 2,
>   "title": "Test Collection",
>   "publish": true,
>   "restrictions": false,
>   "ead_id": "test_999",
>   "created_by": "admin",
>   "last_modified_by": "user2",
>   "create_time": "2016-07-14T23:50:37Z",
>   "system_mtime": "2020-03-10T17:29:46Z",
>   "user_mtime": "2020-03-10T17:29:46Z",
> ...
> 
> 
> But in most of the subrecords of the resource the timestamps have all updated 
> to the time of the update of the resource record. In this case the only thing 
> that was updated was in the resource record was the eadid, but the instance 
> subrecords had their timestamps updated even though not at all part of the 
> update. Note that while data was changed in the sub record the lock_version 
> is still at 0. Again, this was done with an update via the staff interface.
> 
> Before
> "instances": [
>   {
> "lock_version": 0,
> "created_by": "user1",
> "last_modified_by": "user1",
> "create_time": "2017-02-02T18:15:58Z",
> "system_mtime": "2017-02-02T18:15:58Z",
> "user_mtime": "2017-02-02T18:15:58Z",
> "instance_type": "mixed_materials",
> "jsonmodel_type": "instance",
> "is_representative": false,
> "sub_container": {
>   "lock_version": 0,
>   "created_by": "user1",
>   "last_modified_by": "user1",
>   "create_time": "2017-02-02T18:15:58Z",
>   "system_mtime": "2017-02-02T18:15:58Z",
>   "user_mtime": "2017-02-02T18:15:58Z",
>   "jsonmodel_type": "sub_container",
> 
> After
> "instances": [
>   {
> "lock_version": 0,
> "created_by": "user2",
> "last_modified_by": "user2",
> "create_time": "2020-03-10T17:29:47Z",
> "system_mtime": "2020-03-10T17:29:47Z",
> "user_mtime": "2020-03-10T17:29:47Z",
> "instance_type": "mixed_materials",
> "jsonmodel_type": "instance",
> "is_representative": false,
> "sub_container": {
>   "lock_version": 0,
>   "created_by": "user2",
>   "last_modified_by": "user2",,
>   "create_time": "2020-03-10T17:29:47Z",
>   "system_mtime": "2020-03-10T17:29:47Z",
>   "user_mtime": "2020-03-10T17:29:47Z",
>   "jsonmodel_type": "sub_container",
> 
> 
> I'm trying to determine if this is a local problem or if this is just 
> normally how aspace manages updates, and if so is it a bug. Would someone 
> with access to the API of their ArchivesSpace instance see if they could 
> reproduce this? I've tested this on installations of v2.7.0 and v2.7.1.
> 
> Thanks, 
> 
> Don
> !DSPAM:5e680a81236307999538416! 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> 
> !DSPAM:5e680a81236307999538416!

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

[Archivesspace_Users_Group] Odd data modifications during aspace updates.

[Donald Mennerich]

 Hello,

While testing a script that was updating a resource's ead_id via the api I
noticed that the timestamps for  most sub-records of the resource, e.g.
instances, extents, langmaterials, etc., that wern't part of the update
were havign their timesstamps, includeing create_time and created_by,
updated as well. I naturally assumed there was something wrong with my
code, but when we tested updating a resource record from the staff
interface the same thing happening was observed.

For example, the fields belonging to the Resource model updated as
expected, the creation_time and created_by were not modified, while the
last_modified_by and mtimes were:

*Before*

> {  "lock_version": 1,  "title": "Test Collection",  "publish": true,  
> "restrictions": false,  "created_by": "admin",
>
>   "last_modified_by": "user1",  "create_time": "2016-07-14T23:50:37Z",  
> "system_mtime": "2018-03-29T22:05:59Z",  "user_mtime": "2017-02-02T18:15:58Z",
>
>  ...
>

*After*

> {
>   "lock_version": 2,  "title": "Test Collection",  "publish": true,  
> "restrictions": false,
>
>   "ead_id": "test_999",  "created_by": "admin",
>
>   "last_modified_by": "user2",  "create_time": "2016-07-14T23:50:37Z",  
> "system_mtime": "2020-03-10T17:29:46Z",  "user_mtime": "2020-03-10T17:29:46Z",
> ...
>
>

But in most of the subrecords of the resource the timestamps have all
updated to the time of the update of the resource record. In this case the
only thing that was updated was in the resource record was the eadid, but
the instance subrecords had their timestamps updated even though not at all
part of the update. Note that while data was changed in the sub record the
lock_version is still at 0. Again, this was done with an update via the
staff interface.

*Before*

> "instances": [
>   {
> "lock_version": 0,
> "created_by": "user1",
> "last_modified_by": "user1",
> "create_time": "2017-02-02T18:15:58Z",
> "system_mtime": "2017-02-02T18:15:58Z",
> "user_mtime": "2017-02-02T18:15:58Z",
> "instance_type": "mixed_materials",
> "jsonmodel_type": "instance",
> "is_representative": false,
> "sub_container": {
>   "lock_version": 0,
>   "created_by": "user1",
>   "last_modified_by": "user1",
>   "create_time": "2017-02-02T18:15:58Z",
>   "system_mtime": "2017-02-02T18:15:58Z",
>   "user_mtime": "2017-02-02T18:15:58Z",
>   "jsonmodel_type": "sub_container",
>

*After*

> "instances": [
>   {
> "lock_version": 0,
> "created_by": "user2",
> "last_modified_by": "user2",
> "create_time": "2020-03-10T17:29:47Z",
> "system_mtime": "2020-03-10T17:29:47Z",
> "user_mtime": "2020-03-10T17:29:47Z",
> "instance_type": "mixed_materials",
> "jsonmodel_type": "instance",
> "is_representative": false,
> "sub_container": {
>   "lock_version": 0,
>   "created_by": "user2",
>   "last_modified_by": "user2",,
>   "create_time": "2020-03-10T17:29:47Z",
>   "system_mtime": "2020-03-10T17:29:47Z",
>   "user_mtime": "2020-03-10T17:29:47Z",
>   "jsonmodel_type": "sub_container",
>


I'm trying to determine if this is a local problem or if this is just
normally how aspace manages updates, and if so is it a bug. Would someone
with access to the API of their ArchivesSpace instance see if they could
reproduce this? I've tested this on installations of v2.7.0 and v2.7.1.

Thanks,

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

[Archivesspace_Users_Group] LYRASIS NHPRC Small and Diverse Archival Organization Needs Assessment Survey

[Jessica Crouch]

[Posted on behalf of our colleagues at LYRASIS.  Please contact Leigh A. 
Grinstead (leigh.grinst...@lyrasis.org) 
with any questions.]

LYRASIS has been hired by the National Historical Publications and Records 
Commission (NHPRC) to develop a Small and Diverse Archival Organization Needs 
Assessment Survey. Thank you for your interest in the project—your support is 
critical to understanding the needs of small archives and supporting the field!
We believe that “small archives” are generally defined as those repositories 
with budgets of $100,000 or less and/or holdings of 1,000 cubic feet or 
less—these are not absolute figures—and repositories should not skip the survey 
if they have slightly larger budgets or holdings.

We recommend you review the form and your answers with your colleagues before 
beginning to answer the survey online; we hope to have one survey representing 
a single institution, and not multiple surveys from a single site.

The survey is available at https://www.surveymonkey.com/r/NHPRC2020
We are providing you with a PDF version of the survey to assist you in drafting 
answers and completing the survey prior to entering your information online. If 
you wish, you may print the survey 
NHPRC.pdf 
to review and discuss with your colleagues before completing online.

We estimate the survey will take no more than 20 minutes to complete. The 
survey is editable so that if you close or exit the browser before submitting 
your responses, you may finish later, but we encourage you to complete it in 
one sitting.

Confidentiality: Your responses are being collected and analyzed by LYRASIS, an 
independent, nonprofit, membership organization serving libraries, archives, 
and museums. They will be kept confidential. Only aggregate results will be 
reported. Please answer these questions to help us learn about Small and 
Diverse Archival Organization needs. To submit your answers, you must click on 
the “Done” button at the end of the survey form. Please submit the survey by 
March 25, 2020 at 5:00 Eastern time.

Thank you for your support with this important project.



Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.cro...@lyrasis.org
[page1image482511520]

___
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] Re: update of previous post archivesspace 'manage user access' pages give error

[Huebschen, Alan M]

There could be an entry in the hour that never happened within the user table 
as well.


-Alan



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Mike 
McDermott 
Sent: Tuesday, March 10, 2020 12:51 PM
To: Archivesspace Users Group
Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] update of previous post 
archivesspace 'manage user access' pages give error

Thanks for the help…
This makes sense for the Daniel’s case – where his error was:
Thread-10706: Error communicating with authentication source DBAuth: 
Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3
So the date glitch is probably in the auth_db table.
I checked my auth_db table and didn’t see any problematic dates.

My error in more context is:
Mar 10, 2020 1:01:52 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: An exception happened during JRuby-Rack startup
Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3

Any thoughts on how I figure out where my glitchy dates might be stored?

Thanks for any ideas…

Mike


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Blake 
Carver
Sent: Monday, March 9, 2020 2:49 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] update of previous post archivesspace 
'manage user access' pages give error

It's probably a problem brought on by the change of time this week.


Try this:

MySQL [archivesspace]> select * from auth_db;

+--+--+-+-+--+

| id   | username | create_time | system_mtime| pwhash  
 |

+--+--+-+-+--+

|1 | admin| 2016-03-09 07:10:13 | 2016-03-09 07:10:13 | 
$2a$10$Gp0oqAuyVXmG/M1s7XDcTuz8.6aTRooPxbf.AWNUuhxNvzsjTa7om |

|2 | search_indexer   | 2016-03-09 07:10:14 | 2019-10-05 08:33:40 | 
$2a$10$WEoh7JjTOFZ.m.ih9sbxPOHomfcReIBlnAoRQceAbwWFK0DuyC8Tm |

Take a look atsearch_indexer and the 2 times. The system_time is probably the 
one with the bad hour. You can just update that the current time and that 
should do it. So something like

update auth_db set system_mtime = NOW()where username = search_indexer.


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Daniel Sprouse 
mailto:dspro...@tsl.texas.gov>>
Sent: Monday, March 9, 2020 2:35 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] update of previous post archivesspace 
'manage user access' pages give error

new information added, and new log files attached.
I am homing in on the issue here, thinking it is a java version issue, or a 
java version recognition issue. If anyone has seen anything like this, any 
guidance would be appreciated.

after migrating from 2.7.0 to 2.7.1, and from mysqld  Ver 5.7.16 to mysqld  Ver 
8.0.16, from java 1.7 to 1.8
[root@tslac4avwebtest archivesspace]# java -version
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (build 1.8.0_232-b09)
OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode)
BUT...
when it was working, the output on the backend webpage showed java 1.7! (I 
think that not seeing java 1.8 is probably the issue)
backend_url http://aristest.tsl.texas.gov:8089
{ "databaseProductName": "MySQL", "databaseProductVersion": "8.0.16", 
"ruby_version": "2.3.0", "host_os": "linux", "host_cpu": "x86_64", "build": 
"java1.7", "archivesSpaceVersion": "v2.7.1" }
-
Archivesspace started normally several times on Friday, but I got errors when I 
went to user management pages.
archivesspace admin account 'System'->'manage users' and 'Repository 
Settings'->'manage user access' pages give error
http://arisint.tsl.texas.gov:8080/users
http://arisint.tsl.texas.gov:8080/users/manage_access
"We're sorry, but something went wrong."

I have not found any other pages that give this error.
attached is a tail -f of archivesspace.out while attempting to get to 
'System'->'manage users'
and a diagnostic spawned by archivesspace, aspace_diagnostic_1583775751.txt

[cid:image001.jpg@01D5F6DA.C9958360]

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

Re: [Archivesspace_Users_Group] update of previous post archivesspace 'manage user access' pages give error

[Mike McDermott]

Thanks for the help...
This makes sense for the Daniel's case - where his error was:
Thread-10706: Error communicating with authentication source DBAuth: 
Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3
So the date glitch is probably in the auth_db table.
I checked my auth_db table and didn't see any problematic dates.

My error in more context is:
Mar 10, 2020 1:01:52 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: An exception happened during JRuby-Rack startup
Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3

Any thoughts on how I figure out where my glitchy dates might be stored?

Thanks for any ideas...

Mike


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Blake 
Carver
Sent: Monday, March 9, 2020 2:49 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] update of previous post archivesspace 
'manage user access' pages give error

It's probably a problem brought on by the change of time this week.


Try this:

MySQL [archivesspace]> select * from auth_db;

+--+--+-+-+--+

| id   | username | create_time | system_mtime| pwhash  
 |

+--+--+-+-+--+

|1 | admin| 2016-03-09 07:10:13 | 2016-03-09 07:10:13 | 
$2a$10$Gp0oqAuyVXmG/M1s7XDcTuz8.6aTRooPxbf.AWNUuhxNvzsjTa7om |

|2 | search_indexer   | 2016-03-09 07:10:14 | 2019-10-05 08:33:40 | 
$2a$10$WEoh7JjTOFZ.m.ih9sbxPOHomfcReIBlnAoRQceAbwWFK0DuyC8Tm |

Take a look atsearch_indexer and the 2 times. The system_time is probably the 
one with the bad hour. You can just update that the current time and that 
should do it. So something like

update auth_db set system_mtime = NOW()where username = search_indexer.


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Daniel Sprouse 
mailto:dspro...@tsl.texas.gov>>
Sent: Monday, March 9, 2020 2:35 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] update of previous post archivesspace 
'manage user access' pages give error

new information added, and new log files attached.
I am homing in on the issue here, thinking it is a java version issue, or a 
java version recognition issue. If anyone has seen anything like this, any 
guidance would be appreciated.

after migrating from 2.7.0 to 2.7.1, and from mysqld  Ver 5.7.16 to mysqld  Ver 
8.0.16, from java 1.7 to 1.8
[root@tslac4avwebtest archivesspace]# java -version
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (build 1.8.0_232-b09)
OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode)
BUT...
when it was working, the output on the backend webpage showed java 1.7! (I 
think that not seeing java 1.8 is probably the issue)
backend_url http://aristest.tsl.texas.gov:8089
{ "databaseProductName": "MySQL", "databaseProductVersion": "8.0.16", 
"ruby_version": "2.3.0", "host_os": "linux", "host_cpu": "x86_64", "build": 
"java1.7", "archivesSpaceVersion": "v2.7.1" }
-
Archivesspace started normally several times on Friday, but I got errors when I 
went to user management pages.
archivesspace admin account 'System'->'manage users' and 'Repository 
Settings'->'manage user access' pages give error
http://arisint.tsl.texas.gov:8080/users
http://arisint.tsl.texas.gov:8080/users/manage_access
"We're sorry, but something went wrong."

I have not found any other pages that give this error.
attached is a tail -f of archivesspace.out while attempting to get to 
'System'->'manage users'
and a diagnostic spawned by archivesspace, aspace_diagnostic_1583775751.txt

[cid:image001.jpg@01D5F6DA.C9958360]

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

[Archivesspace_Users_Group] Forcing External Document links to open in new tab

[Nic Stanton-Roark]

Hey all,

Is there a way to do this within the staff interface? All of my attempts
just break the link.

Thanks.


*Nicholas Stanton-Roark*  |  Archivist  | Robert A. Nicholson University
Library
Anderson University  |  1100 E. Fifth St, Anderson, IN 46012
(765) 641-4285 <%28765%29%20641%204285>  |  ndro...@anderson.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] [EXTERNAL] Re: archivesspace admin account 'System'->'manage users' and 'Repository Settings'->'manage user access' pages give error

[Huebschen, Alan M]

Hi Mike,


This is an issue I faced during last year's DST switch and yesterday someone 
also ran into it here on the listserv. Blake had a well laid out response so 
I'll paste it below.

If anyone knows how to change the time indexing runs to 1am or 3am I think that 
would prevent this issue in the future as DST time change is at 2am.


>From Blake:


"It's probably a problem brought on by the change of time this week.

Try this:

MySQL [archivesspace]> select * from auth_db;
+--+--+-+-+--+
| id   | username | create_time | system_mtime| pwhash  
 |
+--+--+-+-+--+
|1 | admin| 2016-03-09 07:10:13 | 2016-03-09 07:10:13 | 
$2a$10$Gp0oqAuyVXmG/M1s7XDcTuz8.6aTRooPxbf.AWNUuhxNvzsjTa7om |
|2 | search_indexer   | 2016-03-09 07:10:14 | 2019-10-05 08:33:40 | 
$2a$10$WEoh7JjTOFZ.m.ih9sbxPOHomfcReIBlnAoRQceAbwWFK0DuyC8Tm |


Take a look atsearch_indexer and the 2 times. The system_time is probably the 
one with the bad hour. You can just update that the current time and that 
should do it. So something like
update auth_db set system_mtime = NOW()where username = search_indexer.  "


-Alan Huebschen

University of Illinois at Springfield

Brookens Library Information Systems



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Mike 
McDermott 
Sent: Tuesday, March 10, 2020 11:02 AM
To: Archivesspace Users Group
Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] archivesspace admin account 
'System'->'manage users' and 'Repository Settings'->'manage user access' pages 
give error

Greetings...
We began noticing issues with our ArchivesSpace installations yesterday. 
(version 2.6.0)
The significant error in log seems to be:

Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3

I notice this error coming up in your log output as well...

I'm thinking this is related to the Daylight Saving Time change? Is anyone else 
having problems since that change?

We're on Red Hat 7 - I've updated to the newest available versions of java and 
the oracle java mysql connector.

Mike McDermott
Bowdoin College Library

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Daniel 
Sprouse
Sent: Monday, March 9, 2020 12:38 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] archivesspace admin account 
'System'->'manage users' and 'Repository Settings'->'manage user access' pages 
give error

after migrating from 2.7.0 to 2.7.1, and from mysqld  Ver 5.7.16 to mysqld  Ver 
8.0.16.

archivesspace admin account 'System'->'manage users' and 'Repository 
Settings'->'manage user access' pages give error

http://arisint.tsl.texas.gov:8080/users
http://arisint.tsl.texas.gov:8080/users/manage_access
We're sorry, but something went wrong.

I have not found any other pages that give this error.

attached is a tail -f of archivesspace.out while attempting to get to 
'System'->'manage users'

[cid:image001.jpg@01D5F6D2.3AE30820]

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

Re: [Archivesspace_Users_Group] archivesspace admin account 'System'->'manage users' and 'Repository Settings'->'manage user access' pages give error

[Mike McDermott]

Greetings...
We began noticing issues with our ArchivesSpace installations yesterday. 
(version 2.6.0)
The significant error in log seems to be:

Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3

I notice this error coming up in your log output as well...

I'm thinking this is related to the Daylight Saving Time change? Is anyone else 
having problems since that change?

We're on Red Hat 7 - I've updated to the newest available versions of java and 
the oracle java mysql connector.

Mike McDermott
Bowdoin College Library

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Daniel 
Sprouse
Sent: Monday, March 9, 2020 12:38 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] archivesspace admin account 
'System'->'manage users' and 'Repository Settings'->'manage user access' pages 
give error

after migrating from 2.7.0 to 2.7.1, and from mysqld  Ver 5.7.16 to mysqld  Ver 
8.0.16.

archivesspace admin account 'System'->'manage users' and 'Repository 
Settings'->'manage user access' pages give error

http://arisint.tsl.texas.gov:8080/users
http://arisint.tsl.texas.gov:8080/users/manage_access
We're sorry, but something went wrong.

I have not found any other pages that give this error.

attached is a tail -f of archivesspace.out while attempting to get to 
'System'->'manage users'

[cid:image001.jpg@01D5F6D2.3AE30820]

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

Re: [Archivesspace_Users_Group] Search Across Repositories and Get EAD XML - ArchivesSpace API

[Corey Schmidt]

You're absolutely correct. I changed my endpoint and it's working wonderfully. 
Thank you so much!

-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Mayo, 
Dave
Sent: Tuesday, March 10, 2020 9:24 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Search Across Repositories and Get EAD 
XML - ArchivesSpace API

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]


So, (and sorry I didn't catch this before, I was focused on the narrower 
issues), I think your problem there is actually that you're using the wrong 
endpoint.  When the docs say "Search across repositories," they don't mean 
"Search for arbitrary records across all repositories," they mean "Search 
across all records of TYPE "repository" - so you're getting back nothing 
because there are no resources that are also repositories (

The actual "search for arbitrary things everywhere" URL is just "/search" - I 
think if you use that, you ought to get some results.

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer Harvard University > HUIT > LTS

On 3/10/20, 8:29 AM, "archivesspace_users_group-boun...@lyralists.lyrasis.org 
on behalf of Corey Schmidt" 
 wrote:

This is all great! I've adjusted my search query to use parameters you 
recommended and I'm getting a response back. Though my searches are not 
generating any results. I've tried searching for collection titles and random 
words, but nothing comes back in the results value. Would you have any 
recommendations?

client.get('search/repositories', params={"q": "Freeman collection", 
"page": 1, "type": ['resource']})

I've also adjusted my EAD xml endpoint call and saving the file as you 
recommended and it's working like a charm. It's interesting to note that in 
previous exports, the barcodes to containers were being attached to the "label" 
attribute for the container tag (label="Mixed Materials [5168852364844]"). Yet, 
these exports are generating the "physloc" element with the barcode as the 
value. This works for us, I just thought it was odd.

-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Mayo, 
Dave
Sent: Monday, March 9, 2020 12:46 PM
To: Archivesspace Users Group 

Subject: Re: [Archivesspace_Users_Group] Search Across Repositories and Get 
EAD XML - ArchivesSpace API

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]


Oh, I missed the second part:

So, that endpoint returns the XML directly as the body of the response in 
memory.  The JSONDecodeError you’re getting is due to trying to decode this 
body as JSON, when what you actually have is XML!

If you want to save it to the filesystem, you just need to write it out:

response = 
client.get('repositories/5/resource_descriptions/5734.xml?include_unpublished=false_daos=true_cs=true_pdf=false=false')
with open('myfile.xml', 'wb') as f:
file.write(response.content)

Keep in mind also the parameter-passing stuff from my other email, so the 
request there can be written as:

client.get('repositories/5/resource_descriptions/5734.xml', 
params={'include_unpublished': False, 'include_daos': True, 'numbered_cs': 
True, 'print_pdf': False, 'ead3': False})

Hope this helps!
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer Harvard University > HUIT > LTS

From:  on behalf 
of Corey Schmidt 
Reply-To: Archivesspace Users Group 

Date: Monday, March 9, 2020 at 10:39 AM
To: "archivesspace_users_group@lyralists.lyrasis.org" 

Subject: [Archivesspace_Users_Group] Search Across Repositories and Get EAD 
XML - ArchivesSpace API

Dear ArchivesSpace Members,

Hello, my name is Corey Schmidt and I’m working as the ArchivesSpace 
Project Manager at the University of Georgia. I hope you all are doing well and 
having a good start to your week.

I have two questions about how to utilize the ArchivesSpace API. First, I 
want to use the 
https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.github.io_archivesspace_api_-23search-2Dacross-2Drepositories=DwMFAg=WO-RGvefibhHBZq3fL85hQ=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE=B2y_0wn1HLyXldJyck05IgPrsrOCn8LyjRI8q5uSbtc=_eqqK2s6KdcWsYV9Ke0loG2mitQ-I_nV-F9VeT24-l0=
 API endpoint searching with the resource identifier and take the results to 
get the URI for that resource. How do I structure my call to the API using the 
ASnake client (in python)? I have tried the following code with response 400 
returned:

 client.get('search/repositories?type="resource"=ms954_ids=true')
 client.get('/search/repositories?q=ms954="resource"_ids=true')

Second, I want to download an EAD xml file directly from the API using this 
endpoint: 

Re: [Archivesspace_Users_Group] [EXTERNAL] Re: update of previous post archivesspace 'manage user access' pages give error

[Huebschen, Alan M]

Might there be some way of preventing indexing Sunday mornings or switching the 
time ran from 2am to 1 or 3am? It looks like solr indexing is behind this issue 
and this is the second DST switch that I've had to go into the db and switch a 
time entry manually.


I don't know much about solr or how it gets scheduled with an ASpace internal 
solr instance. I was looking at some of the solr docs and it looks like there 
is  an xml file for some solr settings but I wasn't able to locate one within 
ASpace's file structure.


-Alan Huebschen

University of Illinois at Springfield

Brookens Library Information Systems



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Monday, March 9, 2020 1:48 PM
To: Archivesspace Users Group
Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] update of previous post 
archivesspace 'manage user access' pages give error

It's probably a problem brought on by the change of time this week.


Try this:

MySQL [archivesspace]> select * from auth_db;
+--+--+-+-+--+
| id   | username | create_time | system_mtime| pwhash  
 |
+--+--+-+-+--+
|1 | admin| 2016-03-09 07:10:13 | 2016-03-09 07:10:13 | 
$2a$10$Gp0oqAuyVXmG/M1s7XDcTuz8.6aTRooPxbf.AWNUuhxNvzsjTa7om |
|2 | search_indexer   | 2016-03-09 07:10:14 | 2019-10-05 08:33:40 | 
$2a$10$WEoh7JjTOFZ.m.ih9sbxPOHomfcReIBlnAoRQceAbwWFK0DuyC8Tm |


Take a look atsearch_indexer and the 2 times. The system_time is probably the 
one with the bad hour. You can just update that the current time and that 
should do it. So something like

update auth_db set system_mtime = NOW()where username = search_indexer.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Daniel 
Sprouse 
Sent: Monday, March 9, 2020 2:35 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] update of previous post archivesspace 
'manage user access' pages give error

new information added, and new log files attached.
I am homing in on the issue here, thinking it is a java version issue, or a 
java version recognition issue. If anyone has seen anything like this, any 
guidance would be appreciated.

after migrating from 2.7.0 to 2.7.1, and from mysqld  Ver 5.7.16 to mysqld  Ver 
8.0.16, from java 1.7 to 1.8
[root@tslac4avwebtest archivesspace]# java -version
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (build 1.8.0_232-b09)
OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode)
BUT...
when it was working, the output on the backend webpage showed java 1.7! (I 
think that not seeing java 1.8 is probably the issue)
backend_url http://aristest.tsl.texas.gov:8089
{ "databaseProductName": "MySQL", "databaseProductVersion": "8.0.16", 
"ruby_version": "2.3.0", "host_os": "linux", "host_cpu": "x86_64", "build": 
"java1.7", "archivesSpaceVersion": "v2.7.1" }
-
Archivesspace started normally several times on Friday, but I got errors when I 
went to user management pages.
archivesspace admin account 'System'->'manage users' and 'Repository 
Settings'->'manage user access' pages give error
http://arisint.tsl.texas.gov:8080/users
http://arisint.tsl.texas.gov:8080/users/manage_access
"We're sorry, but something went wrong."

I have not found any other pages that give this error.
attached is a tail -f of archivesspace.out while attempting to get to 
'System'->'manage users'
and a diagnostic spawned by archivesspace, aspace_diagnostic_1583775751.txt


[cid:f31f7ef0-8e07-4602-9acc-c50afd47b573]

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

Re: [Archivesspace_Users_Group] Search Across Repositories and Get EAD XML - ArchivesSpace API

[Mayo, Dave]

So, (and sorry I didn't catch this before, I was focused on the narrower 
issues), I think your problem there is actually that you're using the wrong 
endpoint.  When the docs say "Search across repositories," they don't mean 
"Search for arbitrary records across all repositories," they mean "Search 
across all records of TYPE "repository" - so you're getting back nothing 
because there are no resources that are also repositories (

The actual "search for arbitrary things everywhere" URL is just "/search" - I 
think if you use that, you ought to get some results.

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

On 3/10/20, 8:29 AM, "archivesspace_users_group-boun...@lyralists.lyrasis.org 
on behalf of Corey Schmidt" 
 wrote:

This is all great! I've adjusted my search query to use parameters you 
recommended and I'm getting a response back. Though my searches are not 
generating any results. I've tried searching for collection titles and random 
words, but nothing comes back in the results value. Would you have any 
recommendations?

client.get('search/repositories', params={"q": "Freeman collection", 
"page": 1, "type": ['resource']})

I've also adjusted my EAD xml endpoint call and saving the file as you 
recommended and it's working like a charm. It's interesting to note that in 
previous exports, the barcodes to containers were being attached to the "label" 
attribute for the container tag (label="Mixed Materials [5168852364844]"). Yet, 
these exports are generating the "physloc" element with the barcode as the 
value. This works for us, I just thought it was odd.

-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Mayo, 
Dave
Sent: Monday, March 9, 2020 12:46 PM
To: Archivesspace Users Group 

Subject: Re: [Archivesspace_Users_Group] Search Across Repositories and Get 
EAD XML - ArchivesSpace API

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]


Oh, I missed the second part:

So, that endpoint returns the XML directly as the body of the response in 
memory.  The JSONDecodeError you’re getting is due to trying to decode this 
body as JSON, when what you actually have is XML!

If you want to save it to the filesystem, you just need to write it out:

response = 
client.get('repositories/5/resource_descriptions/5734.xml?include_unpublished=false_daos=true_cs=true_pdf=false=false')
with open('myfile.xml', 'wb') as f:
file.write(response.content)

Keep in mind also the parameter-passing stuff from my other email, so the 
request there can be written as:

client.get('repositories/5/resource_descriptions/5734.xml', 
params={'include_unpublished': False, 'include_daos': True, 'numbered_cs': 
True, 'print_pdf': False, 'ead3': False})

Hope this helps!
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer Harvard University > HUIT > LTS

From:  on behalf 
of Corey Schmidt 
Reply-To: Archivesspace Users Group 

Date: Monday, March 9, 2020 at 10:39 AM
To: "archivesspace_users_group@lyralists.lyrasis.org" 

Subject: [Archivesspace_Users_Group] Search Across Repositories and Get EAD 
XML - ArchivesSpace API

Dear ArchivesSpace Members,

Hello, my name is Corey Schmidt and I’m working as the ArchivesSpace 
Project Manager at the University of Georgia. I hope you all are doing well and 
having a good start to your week.

I have two questions about how to utilize the ArchivesSpace API. First, I 
want to use the 
https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.github.io_archivesspace_api_-23search-2Dacross-2Drepositories=DwMFAg=WO-RGvefibhHBZq3fL85hQ=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE=B2y_0wn1HLyXldJyck05IgPrsrOCn8LyjRI8q5uSbtc=_eqqK2s6KdcWsYV9Ke0loG2mitQ-I_nV-F9VeT24-l0=
 API endpoint searching with the resource identifier and take the results to 
get the URI for that resource. How do I structure my call to the API using the 
ASnake client (in python)? I have tried the following code with response 400 
returned:

 client.get('search/repositories?type="resource"=ms954_ids=true')
 client.get('/search/repositories?q=ms954="resource"_ids=true')

Second, I want to download an EAD xml file directly from the API using this 
endpoint: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.github.io_archivesspace_api_-23get-2Dan-2Dead-2Drepresentation-2Dof-2Da-2Dresource=DwMFAg=WO-RGvefibhHBZq3fL85hQ=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE=B2y_0wn1HLyXldJyck05IgPrsrOCn8LyjRI8q5uSbtc=xwd2j6qv-zYs8pDbLpLM23dcSeDYcPUkZSAuio8FEVQ=
 XML. How do I specify where the EAD xml file saves to? I’m not even sure if it 
is saving anywhere on my computer. However, my requests are successful, 
generating a 200 response. I tried turning the response into json (using 
ASnake’s .json()) and 

Re: [Archivesspace_Users_Group] Search Across Repositories and Get EAD XML - ArchivesSpace API

[Corey Schmidt]

We will have to set up our OAI configuration, but haven’t looked into that 
process yet. I will keep this in mind moving forward. Thanks!

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of 
Majewski, Steven Dennis (sdm7g)
Sent: Monday, March 9, 2020 12:43 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Search Across Repositories and Get EAD 
XML - ArchivesSpace API

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]
I would also add that if you want the EAD, it may be simpler to access it from 
the OAI endpoint, but only if OAI is configured properly. Try downloading a 
resource using oai_ead metadata from the oai/sample page, to see if it’s 
configured properly and what the resource URLs will look like.

— Steve M.




On Mar 9, 2020, at 10:39 AM, Corey Schmidt 
mailto:corey.schm...@uga.edu>> wrote:

Dear ArchivesSpace Members,

Hello, my name is Corey Schmidt and I’m working as the ArchivesSpace Project 
Manager at the University of Georgia. I hope you all are doing well and having 
a good start to your week.

I have two questions about how to utilize the ArchivesSpace API. First, I want 
to use the Search across 
repositories
 API endpoint searching with the resource identifier and take the results to 
get the URI for that resource. How do I structure my call to the API using the 
ASnake client (in python)? I have tried the following code with response 400 
returned:

 client.get('search/repositories?type="resource"=ms954_ids=true')
 client.get('/search/repositories?q=ms954="resource"_ids=true')

Second, I want to download an EAD xml file directly from the API using this 
endpoint: Get an EAD representation of a 
ResourceXML.
 How do I specify where the EAD xml file saves to? I’m not even sure if it is 
saving anywhere on my computer. However, my requests are successful, generating 
a 200 response. I tried turning the response into json (using ASnake’s .json()) 
and writing it, but I keep getting a JSONDecodeError. This is my request:

 request_ead = 
client.get('repositories/5/resource_descriptions/5734.xml?include_unpublished=false_daos=true_cs=true_pdf=false=false')

Any help would be greatly appreciated!

Sincerely,

Corey

Corey Schmidt
ArchivesSpace Project Manager | University of Georgia Libraries
Email: corey.schm...@uga.edu
Phone: +1-706-542-8151

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

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

Re: [Archivesspace_Users_Group] Search Across Repositories and Get EAD XML - ArchivesSpace API

[Corey Schmidt]

This is all great! I've adjusted my search query to use parameters you 
recommended and I'm getting a response back. Though my searches are not 
generating any results. I've tried searching for collection titles and random 
words, but nothing comes back in the results value. Would you have any 
recommendations?

client.get('search/repositories', params={"q": "Freeman collection", "page": 1, 
"type": ['resource']})

I've also adjusted my EAD xml endpoint call and saving the file as you 
recommended and it's working like a charm. It's interesting to note that in 
previous exports, the barcodes to containers were being attached to the "label" 
attribute for the container tag (label="Mixed Materials [5168852364844]"). Yet, 
these exports are generating the "physloc" element with the barcode as the 
value. This works for us, I just thought it was odd.

-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Mayo, 
Dave
Sent: Monday, March 9, 2020 12:46 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Search Across Repositories and Get EAD 
XML - ArchivesSpace API

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]


Oh, I missed the second part:

So, that endpoint returns the XML directly as the body of the response in 
memory.  The JSONDecodeError you’re getting is due to trying to decode this 
body as JSON, when what you actually have is XML!

If you want to save it to the filesystem, you just need to write it out:

response = 
client.get('repositories/5/resource_descriptions/5734.xml?include_unpublished=false_daos=true_cs=true_pdf=false=false')
with open('myfile.xml', 'wb') as f:
file.write(response.content)

Keep in mind also the parameter-passing stuff from my other email, so the 
request there can be written as:

client.get('repositories/5/resource_descriptions/5734.xml', 
params={'include_unpublished': False, 'include_daos': True, 'numbered_cs': 
True, 'print_pdf': False, 'ead3': False})

Hope this helps!
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer Harvard University > HUIT > LTS

From:  on behalf of 
Corey Schmidt 
Reply-To: Archivesspace Users Group 

Date: Monday, March 9, 2020 at 10:39 AM
To: "archivesspace_users_group@lyralists.lyrasis.org" 

Subject: [Archivesspace_Users_Group] Search Across Repositories and Get EAD XML 
- ArchivesSpace API

Dear ArchivesSpace Members,

Hello, my name is Corey Schmidt and I’m working as the ArchivesSpace Project 
Manager at the University of Georgia. I hope you all are doing well and having 
a good start to your week.

I have two questions about how to utilize the ArchivesSpace API. First, I want 
to use the 
https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.github.io_archivesspace_api_-23search-2Dacross-2Drepositories=DwMFAg=WO-RGvefibhHBZq3fL85hQ=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE=B2y_0wn1HLyXldJyck05IgPrsrOCn8LyjRI8q5uSbtc=_eqqK2s6KdcWsYV9Ke0loG2mitQ-I_nV-F9VeT24-l0=
 API endpoint searching with the resource identifier and take the results to 
get the URI for that resource. How do I structure my call to the API using the 
ASnake client (in python)? I have tried the following code with response 400 
returned:

 client.get('search/repositories?type="resource"=ms954_ids=true')
 client.get('/search/repositories?q=ms954="resource"_ids=true')

Second, I want to download an EAD xml file directly from the API using this 
endpoint: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.github.io_archivesspace_api_-23get-2Dan-2Dead-2Drepresentation-2Dof-2Da-2Dresource=DwMFAg=WO-RGvefibhHBZq3fL85hQ=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE=B2y_0wn1HLyXldJyck05IgPrsrOCn8LyjRI8q5uSbtc=xwd2j6qv-zYs8pDbLpLM23dcSeDYcPUkZSAuio8FEVQ=
 XML. How do I specify where the EAD xml file saves to? I’m not even sure if it 
is saving anywhere on my computer. However, my requests are successful, 
generating a 200 response. I tried turning the response into json (using 
ASnake’s .json()) and writing it, but I keep getting a JSONDecodeError. This is 
my request:

 request_ead = 
client.get('repositories/5/resource_descriptions/5734.xml?include_unpublished=false_daos=true_cs=true_pdf=false=false')

Any help would be greatly appreciated!

Sincerely,

Corey

Corey Schmidt
ArchivesSpace Project Manager | University of Georgia Libraries
Email: mailto:corey.schm...@uga.edu
Phone: +1-706-542-8151


___
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