Image Swap Meet

Northwestern and DIL: One large compound object for image data streams and a sibling object containing VRA Work type metadata
- DELIV-OPS datastream stores crop information
- ARCHV-IMG and ARCHV-EXIF are archive copies of TIFFs only (not for display), they are EXTERNAL DATASTREAMS, external to have different storage strategy for larger files
- VRA Work object (descriptive metadata)
  - describes the thing that is actually photographed (eg. a building)
  - in UI shows related images using VRA work relationships (i.e.. sculptor, painter)
- Duke, U of Oregon, and Oregon State interested in using DIL code (and interested in Hydra)
- Disseminators used to translate requests to the image server (Aware vended software, same library as Djatoka)
- How does this relate to IIIF?
- It would be beneficial to make crop tool be IIIF API compliant
  - some of the disseminator terms could not be IIIF but maybe create a mapping from IIIF compliant REST resources to Fedora based disseminator calls
- Hydra has user groups and permission awareness and make sense to put in at Hydra level?
- Next steps: NW document image model and look into IIIF compliancy