[Archivesspace_Users_Group] Help suppressing a finding aid section

[Custer, Mark]

Hi Bridger,

Just a very quick reply, as I haven't had time to look at the newest release of ArchiveSpace, but...

  1.  Yes, I think you'd need to use a plugin or other mechanism to do this (lots of plugin examples out there, but if you have any questions about that, there are lots of people in the ASpace community that could help out).
  2.  I don't like the accordion approach overall, so maybe that will be updated at some point, but that still doesn't help you right now, of course.
  3.  Most importantly, if you do remove this section, I'd encourage you to think about not moving some of the data elsewhere, particularly the finding aid author, sponsor info (if applicable), etc.  I also wish that the finding author info could be managed as linked agents, rather than just text, but even as text it's very useful data!  Also, it provides credit as well as some visibility to archival labor (that's another reason I don't like the accordions, since it hides that info by default).

I hope that helps.  And I'm curious to hear more about whatever direction you wind up taking!

All my best

Mark


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Dyson-Smith, Bridger <bdysonsm at utk.edu>
Sent: Monday, March 1, 2021 10:29 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Help suppressing a finding aid section

Hi all -

I'm trying to think about suppressing a section of our finding aids in
the PUI, specifically the Finding Aid & Administrative Information. I'm
not sure, though, if this should be managed through the admin UI or
programmatically.

I had thought that there might be 'Publish' radio box on that section
in the admin UI, but maybe there isn't. Unless I'm missing something
(and I probably am!) in the admin UI, then addressing this
programmatically seems to be the way forward.

Does this sound accurate? What else should I be looking for? We're
running v2.5.1. Thoughts and suggestions would be greatly appreciated -
thanks in advance for your time and trouble.

Best,
Bridger
--
Bridger Dyson-Smith
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=04%7C01%7Cmark.custer%40yale.edu%7C7f6e4c3f47be431e9dd308d8dcc6e758%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637502094224544177%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=PMx4OS0yPDdHFrwVS3Xn8TdtOOEb5NTxzbd6WwMvFdo%3D&reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20210301/11daaa36/attachment.html>