[Archivesspace_Users_Group] Does built-in find and replace function affect all fields, including Notes?

[Kyle Breneman]

Does ArchivesSpace' built-in find and replace function affect all fields, 
including Notes?

Kyle Breneman
Integrated Digital Services Librarian
The University of Baltimore
kbrene...@ubalt.edu
I believe in freedom of thought and
freedom of speech. Do you?

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

Re: [Archivesspace_Users_Group] Digital objects import with incorrect Published value

[Corey Schmidt]

Wendy,

Not sure if it will be in 3.2.0. One of the ASpace team members might be able 
to say.

Corey

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Wendy 
Scheir
Sent: Tuesday, January 11, 2022 12:29 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Digital objects import with incorrect 
Published value

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]
Thanks, Corey--glad to hear this! Will this be included in the upcoming 3.2.0 
release?

On Tue, Jan 11, 2022 at 12:14 PM Corey Schmidt 
mailto:corey.schm...@uga.edu>> wrote:
Hey Wendy,

I believe there is a JIRA ticket about adding the File Version publish column 
to the spreadsheet importer: 
https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1158

It looks like it’s being worked on by the team and has gone through testing. I 
posted the ticket awhile back because we found this to be a frustrating 
experience for us as well, except not with the PUI but with EAD.xml exports. It 
doesn’t solve Julie’s original issue of logical vs. text based TRUE/FALSE 
inputs, but if there isn’t a JIRA ticket for that already, we can put one in.

Corey

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Wendy Scheir
Sent: Tuesday, January 11, 2022 11:49 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Digital objects import with incorrect 
Published value

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]

Hi,



I wanted to clarify and expand upon the email I sent yesterday regarding our 
current (proposed) use of Digital Objects in ArchivesSpace and the related 
issues that we've encountered when importing DOs using the importer. My thought 
is that perhaps there are others out there who are working on a similar or 
related workflow issue who may have some suggestions for us.



When we have a digital object publicly available on our external digital 
collections site and we wish to provide a link to that object from the 
component (archival object) level in the ASpace PUI:


We leave Publish? unchecked (that is Publish? = FALSE) in the Basic Information 
section, but we do click Publish? in the File Version section:

[https://lh6.googleusercontent.com/UQmRV-pqw1TD_rwZqoC1cD0A4Z3yGahtsHjYwfSzmP-RmI07PE_gGkXkmcAbEGN-WKDQ0N-Nn3kJCvp8WaoTHEl93Jldebskgk80DSSC4VhW4QHxoVOxE46oeG6vbnJe0QohOtoq]


[https://lh4.googleusercontent.com/GaF1UYDhvl1QcGVmWUAKKoxx7cG0EM8zfWEup2AJk3bJw45jIJDrwqKIeKU5Zvi7-TH-z-pEvm0tF0ngPo44N30Mcwzyvu1gypC6W1NqIQABD7glLiEoYrX1VReBjZCxNbuXPHox]


In the PUI, the above looks like this:

[https://lh4.googleusercontent.com/D2cP_mxbtWK-pEhmRK1ACYGtRbRjCz59DQ4S9N1bom7bT2HOTfZQxNdRFuzwKvQkk1LPi2z6ObT6UqebFnVnXxQfYk8WpHKkY4rd2N84gvC-iGVsOXwukx0WBo7P7FH_oy9XpF7_]


Here, what we wanted was the link out to the digital object on the external 
site. The reason we do not click Publish? in the Basic Information section is 
because we believe users find it confusing when there are two disconnected 
references to digital objects within the component record.



This is what the PUI looks like if both Publish? fields are clicked (both are 
TRUE):
[image.png]



Clicking FALSE under Basic Information suppresses the link to the Digital 
Object record in ASpace.


However, the import spreadsheet has a single field for Publish and the File 
Version field inherits the imported selection for the Basic Info field, and 
does not provide the option to mark the Basic Information field FALSE and the 
File Version field TRUE:


[https://lh5.googleusercontent.com/DLgtSIP3kKvG3X5wZYq8B28rC-J8QldZPCn2ZjckfsQ5DLR3WlddkQMKjfpPXyplxYzPNfTDQ0Mzo-8MX2AlQ8mNq89RMXtzKCvLHS14SQM0kgyzuaKbE_g3TUeHjuF6RUWtcci7]


This means that we don't have the option to import a batch of digital objects 
in the same way that we want them to display, which results in having to 
manually edit DOs after import.



Feel free to email me independently with any questions or if you'd like to 
continue this conversation offline.



All best,

Wendy




WENDY SCHEIR

director
THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS

66 FIFTH AVENUE, NEW YORK, NY 10011

sche...@newschool.edu

T 212-229-5942

Explore the Archives | Digital Collections from 
the Archives | New School 
Histories | 
@tnsarchives

[THE NEW SCHOOL]


On Mon, Jan 10, 2022 at 7:15 PM Wendy Scheir 
mailto:sche...@newschool.edu>> wrote:
I think a related or adjacent issue to this is that there are 2 separate 
Publish? fields for each Digital Object record, but the import spreadsheet has 
the option to select 

[Archivesspace_Users_Group] Adding Route to PUI - tip

[Joshua D. Shaw]

Since this just tripped me up, I figured I'd share with the group.

If you are looking to add a route to the PUI in a plugin, you cannot use a two 
part path for your new route since this existing route will catch any of those:

get ":obj_type/:slug_or_id" => 'objects#show'

https://github.com/archivesspace/archivesspace/blob/a2715dd9bf4d2c11671f2034d697a6c06918f39d/public/config/routes.rb#L88

jds

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