[Archivesspace_Users_Group] Print to PDF: Works via staff interface; does not work via public interface
Joshua D. Shaw
Joshua.D.Shaw at dartmouth.edu
Tue Jul 13 17:32:00 EDT 2021
The PUI and the staff side use different methods for generating the pdfs. The staff side goes EAD->PDF if I recall correctly, while the PUI is HTML->PDF.
I'd look for errors in the logs that should point you to the issue.
If I had to guess.... I'd say it might be an ampersand issue. Sometimes an ampersand will look like it's starting an html entity to the PUI generation and cause all sorts of havoc.
But definitely look at the logs for anything that has an ERROR or FATAL in the entry.
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Mark Cyzyk <mcyzyk at jhu.edu>
Sent: Tuesday, July 13, 2021 5:12 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Print to PDF: Works via staff interface; does not work via public interface
Dear ASpace list,
We have a resource record that prints to PDF just fine via the Staff
Interface, but results in error when attempting to print via the Public
I am not finding any errors in the logs on this.
I have exported as EAD (and have attached the file). Looks good to me
(although I will note that record initially entered out ASpace via a
migration from Archivists Toolkit).
Does anyone know why a particular record might print fine from within
the Staff interface, yet not print from the Public interface?
(Our ASpace is running on Linux/CentOS...)
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcyzyk at jhu.edu
Verba volant, scripta manent.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group