Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

DSpace/IIIF Slack Channel

Interested Participants

Following the DSpace Dev meeting on Mar 15, 2017, this brainstorming page was created.  The following people have expressed an interest

Meetings

Brainstorming Questions from Terrence W Brady

  • Would a IIIF server pull resources from DSpace, or does the server provide an alternative view of a DSpace item?
  • Can a IIIF manifest be used to express relationships between bitstreams?  If so, are all of those bitstreams part of one item?
  • I understand that a IIIF server can work with dynamically generated tiles and pre-generated tiles.  I assume that a DSpace integration would need to work with either option.
  • We would be interested in providing a book reader view through IIIF.  
    • Currently, we store PDF bitstreams and use a JavaScript library to render the PDF as a book.  These PDFs were generated from TIF files created during digitization.
    • I presume that we would continue to offer a PDF bitstream for download AND we would generate image tiles from the source TIF files.
  • We would also be interested in using the IIIF manifest to give context to a set of bitstreams within an item

User Story Suggestions from Ben Brumfield

From the perspective of a IIIF client trying to reuse material on a DSpace repository, here are the minimum features needed to work

IIIF Presentation API

  • A IIIF client sees a top-level collection for the DSpace installation listing communities.  Example: DSpace site mapped to IIIF collection document
  • An IIIF client sees a collection manifest listing sub collections
  • An IIIF client sees a sub-collection collection manifest listing items as IIIF manifest links
  • An IIIF client sees a manifest corresponding to an item (TODO real world item with example manifest containing metadata, labels, seeAlso services, and canvases)

IIIF Image API

  • A IIIF client sees available image parameters at by calling info.json on the image service for a single page
  • A IIIF client can display a single page image at Level 0 Compliance
  • No labels