diff --git a/iiif-online-workshop/day-one/whatisiiif.md b/iiif-online-workshop/day-one/whatisiiif.md index 6d062851..62147e34 100644 --- a/iiif-online-workshop/day-one/whatisiiif.md +++ b/iiif-online-workshop/day-one/whatisiiif.md @@ -65,6 +65,8 @@ First because IIIF provides a standard way of exposing images and metadata it is * [Same Manuscript in Mirador 3](https://projectmirador.org/embed/?iiif-content=https://damsssl.llgc.org.uk/iiif/2.0/4574752/manifest.json) * [Tify](https://demo.tify.rocks/demo.html?manifest=https://damsssl.llgc.org.uk/iiif/2.0/4574752/manifest.json) * [IIIF Curation Viewer](http://codh.rois.ac.jp/software/iiif-curation-viewer/demo/?manifest=https://damsssl.llgc.org.uk/iiif/2.0/4574752/manifest.json) + * [Annona](https://ncsu-libraries.github.io/annona/tools/#/display?url=https://damsssl.llgc.org.uk/iiif/2.0/4574752/manifest.json&viewtype=iiif-storyboard&settings=%7B%22fullpage%22%3Atrue%7D) + * [Clover](https://samvera-labs.github.io/clover-iiif/docs/viewer/demo?iiif-content=https://damsssl.llgc.org.uk/iiif/2.0/4574752/manifest.json) For instructions on how to take content from one viewer to another there is this [medium post](https://iiif-io.medium.com/how-to-use-iiif-resources-and-image-viewers-bd378a68b013). diff --git a/iiif-online-workshop/day-three/imgs/presi-usage.svg b/iiif-online-workshop/day-three/imgs/presi-usage.svg new file mode 100644 index 00000000..28c435ed --- /dev/null +++ b/iiif-online-workshop/day-three/imgs/presi-usage.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/iiif-online-workshop/day-three/prezi-how.md b/iiif-online-workshop/day-three/prezi-how.md index 10f5eee0..295c0de0 100644 --- a/iiif-online-workshop/day-three/prezi-how.md +++ b/iiif-online-workshop/day-three/prezi-how.md @@ -2,7 +2,11 @@ -In this workshop we are going to take you through creating a Manifest using a Manifest Editor. This works well for a small number of manifests and to give you an idea of what a Manifest contains. If you are going to create thousands or millions of manifests then you would need to look at automating this process. +In this workshop we are going to take you through creating a Manifest using a Manifest Editor. This works well for a small number of manifests and to give you an idea of what a Manifest contains. If you are going to create thousands or millions of manifests then you would need to look at automating this process. In the 2023 community survey we asked what people are using to generate manifests and the results can be seen below: + +![Chart showing manifest tool usage](imgs/presi-usage.svg) + +As you can see there isn't one solution and most people build their own tools using some shared libraries like iiif-prezi3. Generally the data required to create a manifest generator are as follows: @@ -22,6 +26,7 @@ Generally the format of the incoming metadata means that often these manifest ge ## Presentation API Libraries * [IIIF Manifest Generator](https://github.com/yale-web-technologies/IIIF-Manifest-Generator) - PHP library for generating IIIF manifests. * [iiif-apis](https://github.com/dbmdz/iiif-apis) - Java IIIF API libraries. + * [iiif-prezi3](https://github.com/iiif-prezi/iiif-prezi3) - Python library providing a reference implementation for IIIF v3. * [iiif-prezi](https://github.com/IIIF/iiif-prezi) - Python library providing a reference implementation. * [O'Sullivan](https://github.com/IIIF/osullivan) - Ruby API for creating IIIF manifests. * [Swiiift](https://github.com/mejackreed/Swiiift) - IIIF presentation API library for Swift. diff --git a/iiif-online-workshop/day-two/image-servers/README.md b/iiif-online-workshop/day-two/image-servers/README.md index 4dfaf6bd..b66f5126 100644 --- a/iiif-online-workshop/day-two/image-servers/README.md +++ b/iiif-online-workshop/day-two/image-servers/README.md @@ -2,9 +2,9 @@ There are many ways to make a IIIF Image available which is both a big advantage but also can add complexity. The decision on which option to go for depends on your institution or personal use case. IIIF is able to be used by single researchers up to National institutions and so there are setups to handle each individual case. Below is a list of options with benefits and issues. -In a 2018 survey we asked what people were using to provide the Image API and these were the results: +In a 2023 survey we asked what people were using to provide the Image API and these were the results: -Use of image servers +Use of image servers Respondents were mostly from within the IIIF community and there is a weighting to larger institutions. Most respondents had installed one of the Image Servers but others are using hosted and DAMS solutions. diff --git a/iiif-online-workshop/day-two/image-servers/imgs/img_server_use_2023.svg b/iiif-online-workshop/day-two/image-servers/imgs/img_server_use_2023.svg new file mode 100644 index 00000000..12878747 --- /dev/null +++ b/iiif-online-workshop/day-two/image-servers/imgs/img_server_use_2023.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/vra-workshop/demos.md b/vra-workshop/demos.md index 9e4a2417..4fd379b9 100644 --- a/vra-workshop/demos.md +++ b/vra-workshop/demos.md @@ -2,6 +2,11 @@ We've now completed the course and would be interested in seeing the demos you've been working on. +Examples from the first workshop can be found at: + +https://docs.google.com/document/d/1W6sBXJEt3Ou2zIPRQxgDQtJtaHZ7qYvCYtixTcSO1Ro/edit?usp=sharing + + ## Slack channels Join the [IIIF slack](http://bit.ly/iiif-slack):