Re: [CODE4LIB] very large image display?
Check out the IIIF (International Image Interoperability Framework) Image API: http://iiif.io/ You can use an image server that supports IIIF natively (e.g., Loris https://github.com/pulibrary/loris ) or a translation shim (e..g, with Djatoka).There's client-side support in OpenSeadragon, IIPMooViewer, etc. Mike On 7/25/14, 11:36 AM, Jonathan Rochkind wrote: Does anyone have a good solution to recommend for display of very large images on the web? I'm thinking of something that supports pan and scan, as well as loading only certain tiles for the current view to avoid loading an entire giant image. A URL to more info to learn about things would be another way of answering this question, especially if it involves special server-side software. I'm not sure where to begin. Googling around I can't find any clearly good solutions. Has anyone done this before and been happy with a solution? Thanks for any info! Jonathan -- Michael Appleby Software Engineering Manager Yale Digital Collections Center Yale University
[CODE4LIB] IIIF Image and Presentation API Second Drafts Released
After a month of public testing and feedback, the IIIF Editors are pleased to announce second draft revisions of the International Image Interoperability Framework Image and Presentation (formerly 'Metadata') API specifications. * IIIF Image API 2.0.0-draft2 <http://iiif.io/api/image/2.0/> * IIIF Presentation API 2.0.0-draft2 <http://iiif.io/api/presentation/2.0/> Since the release of the first drafts. a few significant changes have been made: Image API * Added |services| to info.json [ Changes <https://github.com/IIIF/iiif.io/commit/801e9e1628f34c77001d2b151df8efb88e1c688a> | Discussion <https://groups.google.com/d/msg/iiif-discuss/4rp3OvK0jtI/Gow0pF45bMIJ> ] * Added mirroring option to rotation syntax [ Changes <https://github.com/IIIF/iiif.io/commit/93869af7e4fee290c044392e0858d1805cf26e80> | Discussion <https://groups.google.com/forum/#%21topic/iiif-discuss/J7u9cyKZKU4> ] * Added clarification of |default| quality [ Changes <https://github.com/IIIF/iiif.io/commit/dd54d7dfaf4bd2b5ade8b1ab16b8ada8687eb7bb> ] and rotation/background [ Changes <https://github.com/IIIF/iiif.io/commit/b2d6bfe59bd3fdbe3147c88333d2c922f4caf1d6> | Discussion <https://groups.google.com/forum/#%21topic/iiif-discuss/AnXBvw_gVI0> ] * Expanded |info.json| descriptions [ Changes <https://github.com/IIIF/iiif.io/commit/044da46a2eea17374f2604036bd4c066788cf95b> ] * Clarified and cleanly separated information about support for tiles vs. support for preferred sizes in |info.json| [ Changes <https://github.com/IIIF/iiif.io/commit/15c8445403d8ed72f300f8a3da6de2ce05cc8475> | Discussion <https://groups.google.com/forum/#%21topic/iiif-discuss/YOAAcALqoAE> ] Presentation API * Added server side rotation option with iiif:ImageApiSelector [ Changes <https://github.com/IIIF/iiif.io/commit/f94fda233731b4140a922ee673f09fd2f04dc053> | Discussion <https://groups.google.com/forum/#%21topic/iiif-discuss/k2Lu6INn5KM> ] * Improved JSON to RDF mapping [ Changes <https://github.com/IIIF/iiif.io/commit/522f1664f244d3a6f35b05db4d66a7833b9b6bd2> ] * Minor Clarifications: o Cannot reference locations outside of a Canvas o Reduced focus on presenting digitized physical objects o Explicit definition of physical scale algorithm The Editors would like to thank all of those who responded to the first draft with suggestions for improvement. As always, we welcome your feedback, questions, and use cases, and encourage you to submit them to the IIIF Discussion Listserv <mailto:iiif-disc...@googlegroups.com>. Drafts will be kept open for comment until the beginning of August, with the goal of final release in September. However, we would appreciate feedback early in order to work on and gain consensus for any necessary changes. Sincerely, The IIIF Image and Presentation API Editors Benjamin Albritton Michael Appleby Robert Sanderson Stuart Snydman Jon Stroop Simeon Warner -- Michael Appleby Software Engineering Manager Yale Digital Collections Center e: michael.appl...@yale.edu
[CODE4LIB] Job Posting: Senior Programmer Analyst - Office of Digital Assets and Infrastructure, Yale University
Senior Programmer Analyst Office of Digital Assets and Infrastructure, Yale University New Haven, CT ( http://tinyurl.com/yyn7dgz ) ODAI is charged with developing a digital information management strategy for Yale and building digital collections and technical infrastructure in a coordinated and collaborative manner across the entire campus. Programs include the development and deployment of large-scale digital asset management systems, long-term preservation repositories for Yale digital content in all formats, cross-collection search capabilities to enable discovery of collections hosted by numerous departments and many other innovative initiatives. The Senior Programmer Analyst will lead the planning, development, implementation, maintenance, and support of software applications that stand alone, extend functionality of existing systems, bridge systems through interoperability, and provide end-user functionality to the academic community. The software development includes but is not limited to digital asset management systems, digital library systems, knowledge management systems, media processing systems, storage systems, and related ancillary products and services. -- Michael Appleby Senior Software Developer Office of Digital Assets and Infrastructure Yale University e michael.appl...@yale.edu
