[Archivesspace_Users_Group] ID display config options

[Brian Hoffman]

Hi Tom,

In this case, the work just happened to get done right after the cut-off point for the new release. The associated JIRA issue is still in “Ready for Testing” state, so it needs to be tested and accepted before it is considered “done”.

https://archivesspace.atlassian.net/browse/ANW-1196

Brian


From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Tom Hanstra <hanstra at nd.edu>
Date: Tuesday, May 16, 2023 at 9:02 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ID display config options
Thanks for the clarification and sorry for the confusion.

Again, I find myself not familiar enough with the process for ArchivesSpace releases and development. If the work is done (as shown in the pull request sent), what is barring this from being added into the upcoming release of 13.4? Seems like completed work could easily be added to the next release, but I'm probably being too simplistic?

If it won't be added by 3.4, I'll look into the plugin. If someone has a URL for it, that would be great. Or I'll try Google.

Thanks,
Tom

On Tue, May 16, 2023 at 8:49 AM Erhan Tuskan <etu at iisg.nl<mailto:etu at iisg.nl>> wrote:
Yes, what Brian thinks must be true, at IISH we use the Cambridge plugin too and the Component Unique Identifiers are displayed in the PUI and staff client as well.

Erhan,
[cid:18824a230fb4ce8e91]


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Brian Hoffman
Sent: dinsdag 16 mei 2023 2:27
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] ID display config options

Hi Jennifer,

I believe that functionality was originally developed as a plugin – perhaps that explains why Cambridge has it working already?

Brian


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Jennifer Brcka <Jennifer.L.Brcka.2 at nd.edu<mailto:Jennifer.L.Brcka.2 at nd.edu>>
Date: Monday, May 15, 2023 at 4:49 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] ID display config options
Hi Brian,

For clarification -- I'd seen IDs in Cambridge's public display and had asked Tom to toggle our instance on after that model. Is the tree display here<https://archivesearch.lib.cam.ac.uk/repositories/2/resources/8865> output by the PUI configuration option we're discussing? Or does something else make that ID display possible?

The staff-side view presented in the pull request you referenced also looks like exactly what we're after. The work being done, any chance this option could be included in the 3.4 release? Thanks again,

Jennifer

On Mon, May 15, 2023 at 1:41 PM Brian Hoffman <brian.hoffman at lyrasis.org<mailto:brian.hoffman at lyrasis.org>> wrote:
Hi Tom,

I don’t believe it has worked in 3.3.1 or any previous release. Yes, it should be working in 3.5 as the work has already been done:

https://github.com/archivesspace/archivesspace/pull/2987

Brian

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Tom Hanstra <hanstra at nd.edu<mailto:hanstra at nd.edu>>
Date: Monday, May 15, 2023 at 1:15 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] ID display config options
Brian:

Is this a future version such as the released version of 3.4 or a future version like in 3.5 or later?

I'm unclear how functionality in 3.3.1 would get "lost" in the move to 3.4.

Thanks,
Tom

On Mon, May 15, 2023 at 1:00 PM Brian Hoffman <brian.hoffman at lyrasis.org<mailto:brian.hoffman at lyrasis.org>> wrote:
Hi Jennifer,

There is an issue with the way those features were implemented, and they won’t work without some customization in version 3.4.0. There is a fix completed that will appear in a future version.

Brian

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Andrew Morrison <andrew.morrison at bodleian.ox.ac.uk<mailto:andrew.morrison at bodleian.ox.ac.uk>>
Date: Monday, May 15, 2023 at 12:27 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org> <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] ID display config options

Those two features are partially implemented in JavaScript. It is possible that your web browser has cached the old versions of the JavaScript files. Try doing a hard refresh<https://www.howtogeek.com/672607/how-to-hard-refresh-your-web-browser-to-bypass-your-cache/> or emptying your browser's cache.

Andrew.


On 15/05/2023 16:53, Jennifer Brcka wrote:
Hi All,

We've been testing 3.4.0-RC1 and haven't been able to get two configuration options to work:

AppConfig[:display_identifiers_in_largetree_container] = true
AppConfig[:pui_display_identifiers_in_resource_tree] = true

Our database was reindexed after switching these to 'true.'  Any thoughts on what could be going on? Is there anything else we need to change to get this to work?

Thanks,
Jennifer

--

Jennifer Brcka

Archives Specialist
Archival Collections & Management, Hesburgh Libraries
University of Notre Dame

e: jbrcka at nd.edu<mailto:jbrcka at nd.edu>

o: (574)631-2008


_______________________________________________

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

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


--
Tom Hanstra
Sr. Systems Administrator
hanstra at nd.edu<mailto:hanstra at nd.edu>

Error! Filename not specified.
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Tom Hanstra
Sr. Systems Administrator
hanstra at nd.edu<mailto:hanstra at nd.edu>

[Image removed by sender.]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20230516/50e5f363/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 14465 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20230516/50e5f363/attachment.jpg>