Hi everyone. We hope to find better ways of providing access to archival
documents using EAD and some page viewer, but this use of PDF.js is
something we could put together quickly with resources (time, coding chops,
etc) that we had.

Our PDF files are created with Adobe Acrobat. If anyone needs specifics on
how to use the app to create nameddest markers, I can find out. An Adobe
doc on #nameddest can be found here:
http://wwwimages.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/AcrobatDC_pdf_open_parameters.pdf
I don't know about Nitro Pro and its implementation of nameddest.

The PDF.js project is basically what you have in the Mozilla Firefox
browser and is available as a JavaScript library. Many thanks to the PDF.js
team! It seems to run beautifully and the same way on many browsers. I'm on
vacation and going from memory here but I can look up some things when I
get back next week if that would be useful. I do remember having to grapple
with a few sticky things. For example although the docs indicate that
ampersand (&) or pound (#) should work, I think I could not get & to work
but only # worked. I also had a little trouble figuring out how to actually
build the PDF.js application and I also struggled with some CORS issues
with hosting this on AWS. I also have the application introspect as to
where it's living (on our web version of Blacklight or the intranet
version, which has more finding aids and access to digital files). So the
PDF.js introspects to figure out where it's running and modifies the
hyperlink paths to AWS if it's running on the web or to a local location if
it's running on our intranet. Sorry if this is all TMI.

On Wed, Aug 19, 2015 at 2:40 AM, Sergio Letuche <[log in to unmask]>
wrote:

> Dear Michael, how have you created these html links? With what program? I
> have used nitro pro and the links do not show up well via pdf.js
>
> 2015-08-18 14:48 GMT+03:00 Michael Levy <[log in to unmask]>:
>
> > One method is to use Mozilla PDF.js which works the same way on many
> > browsers and supports links.
> >
> > https://mozilla.github.io/pdf.js/
> >
> > An example implementation:
> > http://collections.ushmm.org/search/catalog/irn76089
> >
> >
> >
> http://digitalarchives.assets.ushmm.org/pdfjs/web/viewer.html?file=/pdf/1992.59_FA.pdf#nameddest=inventory
> >
> > -----Original Message-----
> > [CODE4LIB] interconnecting with links in pdf files
> > From: Sergio Letuche <[log in to unmask]>
> > To:  <[log in to unmask]>
> > Tuesday, August 18, 2015 at 2:14 AM
> >
> > Hello community,
> >
> > could you please suggest me the best way to treat the following use case:
> >
> > We have a lot of pdf files, which have in them a lot of links
> > (terms), referring to different pages in the same pdf, or to a page in
> > another pdf file. Noticed that links do not behave well, when opened for
> > example with the default google chrome's pdf reader. So my aproach is to
> > force download the pdf. So the situation is getting mixed: One has a pdf
> > stored locally, and all the links load again the pdf, to be read
> online...
> >
> > Do you have any ideas, best practice i could follow, so as to make this
> > work in a better way?
> >
> > Best
> >
> > p.s. we are using drupal to serve the pdf files, but i guess this is
> > irrelevant...
> >
>