Thanks to Steve M. and Seth S. for identifying the text in our Resource record that were producing errors because of expecting data for a hyperlink when running the Export to PDF job.
We had used a Note type=Index. This is not to be used for creating an Listing (index) of names (as we did) but from creating an Index (like back of the book) within the PDF - and is therefore expecting you to put a reference to where in the record the hyperlink should relate (much link in HTML where you put a #ref to hope around on a Webpage.) We feel that we should have used a Note type = General + sub-note = ordered list. Screen shot of the offending (for us) area as a Lesson Learned to read the documentation and check when you have Resources that you can't get to Print to PDF - in our case, we also couldn't print this from ATK but we just thought it was too large of a record. We deleted that Index Note section and now the Resource can be Print to PDF using our style sheet (huzzah!) [cid:[email protected]] Kari R. Smith Digital Archivist and Program Head for Born-digital Archives Institute Archives and Special Collections Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts 617.253.5690 smithkr at mit.edu http://libraries.mit.edu/archives/ @karirene69 From: [email protected] [mailto:[email protected]] On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Thursday, August 24, 2017 1:08 PM To: Archivesspace Users Group <[email protected]> Subject: Re: [Archivesspace_Users_Group] help requested with an error message - missing attribute EAD does not validate, but that does not appear to be the problem. Replaced all of the attributes with spaces ( "library of congress name authority file" ==> "lcnaf" ) and I still get FOP errors. It appears that the EAD <indexentry> elements are producing invalid FOP xml with empty attributes that are causing fop application to fail: <fo:basic-link internal-destination="" > That seems to be the source of the problem. Will take further digging to figure out the solution. FYI: If you want to try this yourself and have Oxygen, you can load stylesheets/as-ead-pdf.xsl along with your EAD xml and transform to see the XML fop file that goes to the fop application to produce pdf. Oxygen should have it's own copy of 'fop' to process that file, but I was using my copy from home-brew on Mac. -- Steve Majewski / UVA Alderman Library ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Kari R Smith <[email protected]<mailto:[email protected]>> Sent: Thursday, August 24, 2017 12:08:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] help requested with an error message - missing attribute Thanks Steve and Seth - I did validate the EAD in Oxygen, so that's not the problem. It's a huge file, so I'm going to send you two a link (off list) to it and really appreciate anything you can do to uncover where the error is. Kari R. Smith Digital Archivist and Program Head for Born-digital Archives Institute Archives and Special Collections Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts 617.253.5690 smithkr at mit.edu http://libraries.mit.edu/archives/ @karirene69 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Thursday, August 17, 2017 12:36 PM To: Archivesspace Users Group <[email protected]<mailto:[email protected]>> Subject: Re: [Archivesspace_Users_Group] help requested with an error message - missing attribute Also do a validation of the EAD in oxygen. ASpace will sometimes produce invalid EAD, often caused by glitches handling mixed content / markup in notes, or by mixed published/unpublished content producing empty or missing elements. Most of the errors exporting PDF that I've seen are caused by invalid EAD. ( Although your's is one I haven't seen: If you're still at a loss, please post the EAD and we'll investigate. ) -- Steve Majewski / UVA Alderman Library ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Seth Shaw <[email protected]<mailto:[email protected]>> Sent: Thursday, August 17, 2017 11:33:00 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] help requested with an error message - missing attribute Note that the print to PDF process runs the EAD through an XSLT to create an XSL Formatting Objects (XSL-FO) document which is then converted into a PDF. This error may refer to line 3255 your as-ead-pdf.xsl (which lives in the stylesheets subdirectory of the archivesspace home directory), but that seems unlikely if the print to PDF works for other documents, OR the error could be the result of a bad transformation. I would first check the as-ead-pdf.xsl and, if that doesn't seem to be the source, run the EAD through the stylesheet using oXygen and check the output. If none of that turns anything up send along the original EAD and your as-ead-pdf.xsl to see if we can help debug. Good luck! On Thu, Aug 17, 2017 at 6:58 AM, Kari R Smith <[email protected]<mailto:[email protected]>> wrote: > Hello, > > We are unable to print to PDF a finding aid and I'm having trouble locating > where this error is so I can correct it: > > > > org.apache.fop.fo.ValidationException: null:3255:124: Missing attribute on > fo:basic-link: Either external-destination or internal-destination must be > specified. (See position 3255:124) > > > > I've exported the EAD and at line 3255 there is a name entry. > > I'm looking at the XML in Oxygen and have searched on "fo:basic-link" to no > success. > > > > Thanks in advance! > > > > > > Kari R. Smith > > Digital Archivist and Program Head for Born-digital Archives > > Institute Archives and Special Collections > > Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts > > 617.253.5690 smithkr at mit.edu http://libraries.mit.edu/archives/ > @karirene69 > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > [email protected]<mailto:[email protected]> > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > _______________________________________________ Archivesspace_Users_Group mailing list [email protected]<mailto:[email protected]> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
