Re: [Archivesspace_Users_Group] Oddities when updating Agents via the API

2019-10-15 Thread Rachel Donahue
< > archivesspace_users_group@lyralists.lyrasis.org> > Date: Friday, October 11, 2019 at 11:52 AM > To: "archivesspace_users_group@lyralists.lyrasis.org" < > archivesspace_users_group@lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] Oddities when updating Agen

Re: [Archivesspace_Users_Group] Oddities when updating Agents via the API

2019-10-13 Thread Mayo, Dave
From: on behalf of Rachel Donahue Reply-To: Archivesspace Users Group Date: Friday, October 11, 2019 at 11:52 AM To: "archivesspace_users_group@lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Oddities when updating Agents via the API Hi all, I'm running some bulk u

Re: [Archivesspace_Users_Group] Oddities when updating Agents via the API

2019-10-11 Thread Detelich, Alicia
, 2019 at 11:52 AM To: "archivesspace_users_group@lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Oddities when updating Agents via the API Hi all, I'm running some bulk updates to Agents (in this case people) via the API and noticed some rather odd changes to sub-records wh

[Archivesspace_Users_Group] Oddities when updating Agents via the API

2019-10-11 Thread Rachel Donahue
Hi all, I'm running some bulk updates to Agents (in this case people) via the API and noticed some rather odd changes to sub-records when I check the JSON after successfully running the update. 1. Every sub-record (e.g. names, telephones) has replaced "created_by" with the user authenticated by