Merge pull request #206 from IIIF/dhsi-2024

Dhsi 2024

dhsi/SUMMARY.md

@@ -62,6 +62,7 @@
 <!-- , Session 1: 9:00am-10:15am -->
 
 1. [Advanced used cases](day-four/advanced-use-cases.md)
+2. [Collections](day-four/collections.md)
 1. [Wax](day-four/wax.md) <!-- ## Thursday, Session 12: 10:30am-12:00pm -->
 2. [Introduction to Jekyll and GitHub pages](day-four/github-jekyll-pages.md)
 

dhsi/day-four/advanced-use-cases.md

@@ -7,4 +7,5 @@
 6. [Spotlight](https://exhibits.stanford.edu/)
 7. Anything A/V
 8. [Omeka](https://training.iiif.io/advanced_iiif/modules/omeka/)
-9. [Spotlight and Annotations](https://spotlight.vatlib.it/humanist-library)
+9. [Spotlight and Annotations](https://spotlight.vatlib.it/humanist-library)
+10. [Omeka](https://training.iiif.io/advanced_iiif/modules/omeka/)

dhsi/day-four/collections.md

@@ -0,0 +1,25 @@
+# Collections
+Collections are a way to semantically link multiple different manifests. It allows for linking materials either through concrete or abstract groupings.
+
+An example can seen in the [IIIF cookbook recipe](https://iiif.io/api/cookbook/recipe/0032-collection/).
+
+
+## Other collection examples
+
+1. [National Gallery of Art](https://research.ng-london.org.uk/iiif-projects/json/ng-projects.json)
+2. [FromThePage Jeremiah White Graves Diaries](https://fromthepage.com/iiif/collection/jeremiah-white-graves-diaries)
+3. [Staedel Museum](https://iiif.manducus.net/collections/0008/collection.json)
+4. [Zeppelin Museum Friedrichshafen](https://iiif.manducus.net/collections/0012/collection.json)
+5. [Fotothek](https://sachsen.museum-digital.de/apis/iiif-presentation/collection/c231)
+6. [The biological basis of medicine / edited by E. Edward Bittar ; assisted by Neville Bittar.](https://iiif.wellcomecollection.org/presentation/v2/b18031511)
+7. [e-codices – Virtual Manuscript Library of Switzerland](https://www.e-codices.ch/metadata/iiif/collection.json)
+8. [e-manuscripta](https://www.e-manuscripta.ch/i3f/v21/collection/top)
+9. [e-rara](https://www.e-rara.ch/i3f/v21/collection/top)
+10. [fragmentarium – International Digital Research Lab for Medieval Manuscript Fragments](https://fragmentarium.ms/metadata/iiif/collection.json)
+11. [IIIF Collection for Leipzig University Library](https://iiif.ub.uni-leipzig.de/static/collections/toplevel.json)
+12. [Rare Books](https://digitalcollections.universiteitleiden.nl/rarebooks/datastream/MANIFEST/view)
+13. [Luke Wadding Papers](https://data.ucd.ie/api/img/collection/ivrla:18726)
+14. [Arabic documents](https://iiif.durham.ac.uk/manifests/trifle/collection/32150/t2c9k41zd486)
+15. [We are ISU- Snapshots of Student Life](https://cdm16001.contentdm.oclc.org/iiif/info/p16001coll48/manifest.json)
+16. [Air Scoop](https://digital.lib.utk.edu/assemble/collection/collections/ascoop)
+17. [Collection de Charles V (roi de France, 1338-1380)](https://portail.biblissima.fr/iiif/collection/ark:/43093/coldataa9d9a2d98084b67becd2c1a78c78e4d6143e35da)

dhsi/day-two/reflections.md

@@ -1 +1,9 @@
-- What are some of the disadvantages of us all creating our own viewers
+# Some Reflection Questions
+
+* What kind of NON-image data do you need to make your “viewer” work?
+* What kind of labels and descriptions do you need?
+* What kind of data relationships are needed in order to make it work?
+  * (For example sequence: what comes first, what comes last, what comes next?)
+* What were the pain points of making an image viewer this way?
+* What felt repetitive?
+* Were there features you built that you wanted to re-use but couldn't? How come?