It finally led us to rethink any direct integration with Mirador. It sports a very flexible plugin architecture, allowing for various imaging engines to be activated, including ImageMagick, and even Kakadu (which I’ll return to below).Īnnotations turned out to be a pretty big bite to chew. However, we decided to integrate with Cantaloupe as it solved many IIIF integration issues out-of-the-box. This component is mostly just an exercise in translating NetX data - thumbnails, zooms, and metadata - into an IIIF format.įor zooms, we have a long history of experience with the various underlying technologies, from Pyramid TIFFs and “Zoomify” tiles, to ImageMagick and various other imaging libraries. IIIF manifests are the foundation of any support. This led us down three distinct technological tracks: IIIF manifests, IIIF zoom servers, and IIIF annotations. This would solve a secondary issue we hoped to resolve: providing a markup and approval function within NetX. We started thinking boldly: integrating a Mirador viewer into NetX. Working diligently since we received the Museum community letter to DAMS vendors, we are now poised to offer an initial prototype of NetX support for IIIF. I mention my caution to help frame NetX’s approach to supporting IIIF: we are doing so carefully, methodically, and deliberately in stages. This is not to sound any alarm with IIIF in fact, the rapid pace of change within the IIIF spec and supporting open source libraries is incredibly positive - showing energy and commitment behind IIIF. From my vantage, IIIF certainly will be approached with caution because of NetX’s earlier experiences with projects that failed - CMIS is one of many. I referenced my “ Bigger Than DAM ” post deliberately, because at that time, it held up (the now defunct) CMIS standard as the “new way forward”. This presents a challenge to a software vendor like NetX. Furthermore, not only is the IIIF spec itself evolving rapidly, supporting software implementations (Mirador and many others) are also changing rapidly. To date, these conversations lead me to believe that this is still largely an open question (more on this later). These questions led us to start talking to our customers (and potential customers) about how they would use NetX in conjunction with IIIF. The question of “How would we implement this?”, quickly turned into “What are the use cases to guide us?”. We started by reading the IIIF spec and shortly after, our engineers dug into the APIs. So when NetX received Sheila Rabun’s email back in May 2017 - “ Museum community letter to DAMS vendors, (sent on behalf of the museum’s community) regarding the International Image Interoperability Framework (IIIF) ” - we were excited to meet its implicit challenge: NetX should embrace and support IIIF. Since that time, NetX has also committed to serving the DAM requirements of cultural heritage organizations, especially Museums, Libraries, Foundations, and Universities. I wrote about this commitment back in 2011 with a post titled “ Bigger Than DAM ” ( ) there, I argued that DAMs should be an open, standards-based platform for driving a wide variety of enterprise applications. Click on "Split." and enter "tile_ccc_rrr.As a company, NetX has a core commitment to open standards and to make our product as interoperable as possible. Choose format JPG and check the box "Split.".Open the map image and select menu item File -> "Save as.".(optional) First disable option "Add a resource field" in the Preferences pane of GraphicConverter to make the splitting faster and also to reduce the disk space used by the tiles.To split an image into tiles with GraphicConverter: GraphicConverter is a very useful shareware graphics utility program on MacOS, which can read almost any graphic format (including ECW). All the tiles must be compressed into a single zip file before being transferred into Multiplans. It may also start with tile_0_0.jpg, or even any other value xmin_ymin. The numbering of the tiles need not begin with tile_1_1.jpg. The tiles can alternatively be named along the scheme used by program Zoomify Converter, that is names of the form "zoom-x-y.jpg". The format of the tiles can be jpg or png. Where x and y represent, respectively, the column and line number of the tile.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |