As described in the Yale usability test, users would like the ability to download the complete finding aid PDF from any view of the Collection, not only the top level tabs. As you can see from the mock up, it would mean just having the Print to PDF button present in all views, even if an archival object is opened and selected.
Hi Nice to be here. This is such an easy way to comment on specifications. Maybe too easy - I jumped in when I should have thought it through more. Of course there is the PDF in the export function. Just ignore my request All the best from a very hot Canberra..
I’ve created a new ticket re: optimizing the PDF stylesheet: . Please direct comments and suggestions there. Let’s try to keep discussion on this particular ticket’s topic, since it’s still not entirely obvious to me on the answer. It currently sounds like it would make the most sense to be able to export a PDF of whatever you’re currently viewing, and that exporting the entire finding aid each time isn’t as helpful or desirable, particularly with large collections - right?
As somebody earlier commented, I think having both options would be good--ability to print entire finding aid to PDF from anywhere within a resource record, and a separate button to print just a section of a finding aid to pdf. Several people have mentioned large finding aids where users only need a series or sub-group to review. I suppose this second piece is available through print preview options in browsers, where you can select custom printing of pages--but for some finding aids, that might mean scrolling through the print preview for a long time to hunt down just the section of finding aid you want to print.
I agree. I think that there should be an improved CTRL-P option for printing the current page in the PUI as well as the ability to download an improved version of the entire PDF of a finding aid from any component. For the latter, we addressed this at Yale in our implementation of the PUI by adding the “PDF Finding Aid” button to every component, e.g. https://archives.yale.edu/repositories/15/archival_objects/2820102. I think that works well, but it would be good to know if it’s clear to users what’s happening (and based on this ticket’s title, I think that’s what this ticket is getting at). However, we didn’t do anything to improve what happens when a user prints the current page. But I don’t think such a thing would be very difficult to implement, and I think that addressing ASAP makes a lot of sense!
Writing to adding support from Cambridge University for this issue. We have migrated some huge multi-level catalogues to ArchivesSpace as resources and it would be extremely useful to researchers and many staff users to be able to generate PDFs at any level of the description, not just at resource level.