https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38655
--- Comment #12 from David Cook <[email protected]> --- I'd have to think about this one some more... For a web reader, I'd say you'd need to pre-process your PDFs ahead of time. Splitting them into individual pages and converted into images, which could then be served one by one (for performance and security). (But then... there is the question of where this data is stored and served from. Depending on the amount of data and views you're planning, you'd need to consider the operational costs involved.) I suppose a simple version could be done where the content is stored on the Koha server and served from it. Having Koha serving the content would slow down your Koha overall, but that might be acceptable for you. -- Actually, as I write this, I'm reminded that this topic is already handled by the IIIF (International Image Interoperability Framework). Most of my experience with IIIF is with publicly accessible content, but IIIF does come with authorization APIs too. -- Typically, with IIIF you have an "Image Server" (like the Java-based Cantaloupe) and an "Image Viewer" (like the Javascript-based Universal Viewer). The IIIF-enabled web app has the "Image Viewer" and the app gives the Image Viewer a URL to a IIIF Manifest which is a JSON file, which contains links to the Image Server. Technically, I think you don't have to use an Image Server. I think that you can just use static images as well. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
