Staff PDFs are generated by first exporting to EAD, then converting that
via XSL-FO to PDF. Whereas PUI PDFs are generated by first creating a
HTML file, then using a third-party library that effectively opens the
HTML in a web browser's rendering engine, then prints it to PDF. In the
former process, exporting to EAD falls back to retrieving records from
the MySQL database if, for some reason, it finds a mismatch with what's
on Solr. I do not believe the PUI does that, it only fetches from Solr.
Hence your problem might be fixed by doing a soft re-index:
https://archivesspace.github.io/tech-docs/administration/indexes.html
Andrew.
On 20/07/2022 21:57, Kyle Breneman wrote:
We are setting up two new Windows server environments for
ArchivesSpace 3.2.0. On one of our servers, we have a collection
where the PDF will generate on the staff side, but not through the
PUI. (Both servers are using copies of the same backend ArchivesSpace
database.)
Any troubleshooting tips or solutions? I’m not sure what to do with
RecordNotFound when the PDF will print on the staff side.
Here’s what I see in the log:
*Kyle Breneman*
Integrated Digital Services Librarian
The University of Baltimore
kbrene...@ubalt.edu <mailto: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
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
