Re: [Archivesspace_Users_Group] Microfilm Numbers

2020-04-21 Thread Rachel Donahue
Hi Patsy, I would probably put the microfilm number in as an External Document. The Location doesn't *have* to be a URL, even if it's preferred. --Rachel On Mon, Apr 20, 2020 at 12:07 PM Hand, Sarit wrote: > HI, > > > > Are you creating Resource Records or Archival Object records for the >

Re: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1

2019-12-17 Thread Rachel Donahue
I'm having trouble logging in to comment (or even viewing issues, what's up, Atlassian??), so I'll respond here. *769: *Yes, please! *773: *I agree with Ed Busch that both options (this and 950) should be offered. 950 is about using CSS to print the current webpage rather than the full finding

Re: [Archivesspace_Users_Group] Related accession and resource links on agent records

2019-10-17 Thread Rachel Donahue
Do you by any chance have multiple repositories? Agents will only show related resources and accessions of the repository you currently have selected. --Rachel -- Please note that I currently *do not have access to ARS email*. If you need to contact me, use my LAC address:

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

2019-10-15 Thread Rachel Donahue
relevant field(s) in the relevant name table(s). > > Hope this helps, > > Alicia > > Alicia Detelich > Archivist > Manuscripts and Archives > Yale University Libraries > > From: on behalf > of Rachel Donahue > Reply-To: Archivesspace Users Group

[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