[Archivesspace_Users_Group] print pdf of unpublished resource crashes AS
Majewski, Steven Dennis (sdm7g)
sdm7g at virginia.edu
Fri Apr 27 13:27:46 EDT 2018
PDF printing from the frontend/staff webapp is a three step process:
 exports the resource to EAD
 XSLT processes EAD with stylesheets/as-ead-pdf.xsl to produce a FOP xml file.
 Runs that output thru the FOP processor to create final PDF.
So it would be good to find out in which step it is failing.
( In my experience, the most frequent problem has been the initial step exporting invalid EAD. )
Try checking to see if there is any more specific trace of what is failing in either the application log file
( logs/archivesspace.out ) or in the log files for the batch jobs ( displayed in the batch job console and also in files data/shared/job_files/print_to_pdf_job_*/output.log ).
You can also try each of the steps manually:
 export resource to EAD — validate EAD against ead schema with xmllint ( or Oxygen XML Editor or whatever else available. )
 process EAD against stylesheets/as-ead-pdf.xsl with SAXON
 process fop xml with fop processor.
I have seen invalid EAD sometimes produced if a mix of published and unpublished components can produce EAD with a missing required element. ( I can’t recall the exact combination at the moment — it was an obvious mistake where a note was supposed to be published. ) I have never tried to export EAD with include unpublished unckecked where the top level resource is unpublished. I don’t know if that is a use case that is tested.
— Steve Majewski
> On Apr 27, 2018, at 12:45 PM, Daniel Sprouse <dsprouse at tsl.texas.gov> wrote:
> We have an implementation of AS at Texas State Library and Archives Commission, although I am very new to this application. I have not seen this topic in a search of recent lyralist emails or the user manual, it may be a bug. If it is a feature it isn't a great one. When printing an unpublished resource to pdf AS crashes. If anyone has any insight into this, help would be appreciated.
> What follows is from my users and myself, synopsized.
> "As my user, I went to Create=〉Background Job=〉Print to PDF. I typed in (a redacted last name,) then selected the (a redacted name) finding aid and chose to print to pdf. The "Resource" is unpublished and I did not click on the "include unpublished". It showed an error message in the generic dialog box which looks that it is an unpublished Resource, took its time and then crashed."
> "It could be that this error is related to the fact the item is "unpublished" and I didn't check on the "print unpublished". If you reset again I can try to see if checking that box still causes a crash"
> additional tests, all of which result in crashing archivesspace app:
> Test 1: Resource has no "published" elements and include unpublished was not checked. Error message stated that this is an unpublished resource.
> Test 2: Resource has no published elements and include unpublished was checked. Error message regarding some of the content and export failed
> Test 3: Published top-most level of the Resource and checked including unpublished. Received a proxy error stating an invalid response from an upstream server and could not handle the GET request (Error reading from remote server). Refreshing the page after allowing time for the process does not help
> We are continuing to test ways that this kills AS at this time.
> Thanks, Daniel Sprouse, dsprouse at tsl.texas.gov <mailto:dsprouse at tsl.texas.gov>
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org <mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 6091 bytes
Desc: not available
More information about the Archivesspace_Users_Group