In addition to serving images, the data node also executes scripts that directly interfaces with the files in an item. Scaling by an arbitrary factor (increases server load).Supported output image formats (these are formats that all browsers can display): It extracts, decompresses, scales, rotates, and recompresses images that are stored in the Internet Archive storage format. Setting up the Datanode and the BookReader Image ServerīookReaderImages.php turns your data node into a very simple image server. These files are not necessary for a simple BookReader deployment using static images or an image server. They live in the BookReaderIA directory in the repository. The IA-specific backend PHP and python files that parse the meta.xml and extract the JPEG 2000 image are normally served from a data node. They located in the top-level BookReader directory in the git repository. The static files, such as BookReader.js and BookReader.css, are served from a web node. However, it is easy to run the BookReader on a single machine, serving both roles. The BookReader code is designed to be split onto two kinds of different cluster nodes, web nodes and data nodes. scandata.zip – older variant of bookid_scandata.xml.scandata.xml – older variant of bookid_scandata.xml.bookid_scandata.xml – contains image size and page number information.bookid_meta.xml – contains bibliographic metadata about the book.bookid_jp2.zip – contains processed JPEG2000 images, these are scaled and displayed by the bookreader.bookid_abbyy.gz – contains OCR data XML format, used by full-text search.Here is a breakdown of how the files in an item would look for an item with the identifier bookid, which is located in the directory /1/items/bookid: An item has an identifier that is unique within the IA cluster. There are various other files that describe a book, and these files are grouped together in an Internet Archive item. The Internet Archive stores book images in JPEG 2000 format, and the individual images are sequentially-numbered and stored in a ZIP file. ![]() However, what if your images are stored in a zip file, similar to how stores book images? We’ll walk you through how to set up your webserver (or cluster) to serve images using IA-style book data. Most likely, your book images are either static images in a directory, or they are served by an image server. These two scenarios should cover most use cases. Others have modified the IA BookReader to read image files from an image server, such as the Djatoka JPEG 2000 Image Server, instead of using static files on disk. You can change the location of the images to anywhere on your webserver, and you should be up and running! Once you download the BookReader source code to your webserver, you can load the BookReaderDemo, which will run the bookreader code with static images. The Internet Archive BookReader is designed so that you can run it on your own server. the custom JS file is now looking for instead of jquery-browser-min.js.How to serve IA-style books from your own cluster This recipe was updated to address that bug, e.g. Note: There used to be a bug where FileManager automatically changes “.” to “-” in uploaded file names (not the “.” before the extension), but it was fixed in October 2021. Image 2: BookReader viewer displays selected image file A separate window will open with that record loaded inside the BookReader viewer. You should see the BookReader icon on the right side and to the right of the Download or Print icons. Navigate to an item on your website that is an image file (to be certain it has IIIF API support). ![]() To verify this recipe, first clear your local browser cache (or use a private/incognito window) to make sure you have the most recent version of your custom JavaScript files. Save and publish the changes you made in Website Configuration Tool.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |