Yesterday, I started a series about certain constraints on exporting or archiving Notes data to PDF. There has been more chatter recently about exporting to PDF, a feature that may be supported natively in HCL Notes V11, and that is offered as an archiving solution by some consultants and vendors.
To reiterate, the PDF format itself is great for certain use cases, but has certain limitations by its nature. It is page based unlike both Notes and the web, and it is more of an image of a document than the document itself. That played a role in the first post which showed how attachments appear to be there in the PDF, but are not clickable or launchable, and require a separate process to save at all. Today's peril is similar with a Notes feature that is widely depended upon, the doclink.
This is the second of eight primary issues. Depending on what vendor or driver you use, a few of these may have at least a partial solution, but they are good items to check when validating your approach. The table of contents of all issues will be at the bottom of this post.
2) Doclinks not clickable at all, or go to the original source
Original Notes rich text field. A table of doclinks (from 2008 BP forum) showing original hierarchy in view.
and if we follow one of the links, we get to
PDF rendering. The doclinks look like they are there, but you can't follow them, making them both useless and frustrating
Rendered by the Midas LSX to HTML. You can seem them, you can click them, you can configure where they'll be resolved (in this case, to other local HTML files)
and if we follow one of the links, we get to
Table of Contents (will be updated as the blog series continues)
Want to try out our Midas LSX export for yourself? Simply fill out the online evaluation request, and we'll get you started. There's no cost to seeing it for yourself.
Copyright © 2019 Genii Software Ltd.
Tags: Lotus Notes PDF Midas LSX HCL Notes