[Archivesspace_Users_Group] Customizing the Public Interface PDF

Majewski, Steven Dennis (sdm7g) sdm7g at virginia.edu
Wed Aug 30 13:09:30 EDT 2017

The public interface PDF generation appears to be a completely different method from the FOP/xsl based PDF generator in the staff interface.

Staff PDF generation:   EAD.xml  +  FOP.xsl -> FOP.xml  + [fop-processor] -> PDF

The public interface PDF generator is using Java libraries common/lib/core-renderer.jar and common/lib/itext-2.1.7.js2.jar  which is generating PDF from XHTML + CSS .

So I believe you would want to customize the ERB  html templates in:


I haven't attempted this myself yet, but I would imagine you could override those templates by putting customized copies in plugins/local/public/views/



archivesspace - The ArchivesSpace archives management tool

See also:



archivesspace - The ArchivesSpace archives management tool



archivesspace - The ArchivesSpace archives management tool

The Flying Saucer User's Guide - GitHub Pages<https://flyingsaucerproject.github.io/flyingsaucer/r8/guide/users-guide-R8.html#pdf>
The parser is loaded and configured on first use. Normally, we find the default JDK XML parser to work just fine. You may want to alter the XMLReader instance used if ...


-- Steve Majewski / UVA Alderman Library
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Alice Elizabeth Tippit <a-tippit at northwestern.edu>
Sent: Wednesday, August 30, 2017 11:40:41 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF

Greetings all,

We would like to customize the PDF that generates from the public interface, but are having difficulty figuring out which of the xsl files in the stylesheets folder is used to generate the PDF, and where to place our customized files.

When the “Print” button is clicked in our Public interface, a PDF is automatically generated. In comparison the PDF produced through the staff interface it lacks the useful  table of contents and has formatting that produces a document that is twice the number of pages.

Notes from the public interface session held at the ArchivesSpace Forum indicate that we need to customize the as-ead-html.xsl file as a plugin:

>PDF from PUI is NOT generated from EAD-->PDF XSL (comes from HTML) so to customize PDF you would have to use a plugin; PDF on staff side still is from XSL<

Adding to our confusion, when we run the as-ead-html.xsl file through Oxygen the html document produced has a table of contents, and formatting that is easier on the eyes. No idea what it looks like converted into a PDF. I’d hope for something better than the PDF that currently generates on the public site.

Following the note from the public session as best we can, we attempted a test, placing a customized copy of the as-ead-html.xsl file in archivesspace > plugins > local > public > stylesheets. This had no effect.

Are we chasing the wrong file, or placing it in the wrong location? Or something else…

For interested folks, I’ve attached the html file produced by running the as-ead-html.xsl file through Oxygen, as well as the PDFs currently produced on the Public and Staff interface.

Any advice—thank you!

Alice Tippit
Developer-Metadata & Discovery Services
Northwestern University Library
Northwestern University
1970 Campus Drive
Evanston, IL 60208
a-tippit at northwestern.edu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170830/f1d22029/attachment.html>

More information about the Archivesspace_Users_Group mailing list