Merge pull request #217 from IIIF/nlw_2025_training

Adding AV

Author: glenrobson

nlw-workshop/SUMMARY.md

@@ -51,12 +51,12 @@
 ## IIIF & AV
 - [An introduction to AV](av-intro.md) 
   - [Looking at a BL audio file](day-three/BL-Audio/README.md) 
-  - [Looking at the Internet Archive Videos](ia-examples.md) **todo**
+  - [Looking at the Internet Archive Videos](ia-examples.md) 
   - [Examples](av-examples.md)
   - [Create video Manifest](day-three/digirati-editor/Add_video_manifest.md)
 
 ## Tools and implementations
-- [Tools](tools.md) **todo** 
+- [Tools](tools.md) 
   - [Exhibit](exhibit/exhibit.md)
   - [All Maps](use_cases/allmaps.md)
   - [FromThePage](use_cases/FromThePage.md)

nlw-workshop/av-intro.md

@@ -50,7 +50,7 @@ Note if the audio resource in the body is longer than the time specified in the
 
 Using one of the example NLW video files I created a manifest using the Digirati Manifest editor and then added a few fields that weren't supported by the editor. You can see the manifest below:
 
-[Example AV Manifest](av-manifest.json)
+[Example AV Manifest](https://glenrobson.github.io/iiif_stuff/nlw-workshop/av-manifest.json)
 
 Important features:
  * Bilingual metadata
@@ -59,12 +59,31 @@ Important features:
  * homepage pointing to Clip website
  * provider linking to NLW
  * VTT files
+ * Table of contents example
 
 To view this in a number of viewers you can click on the following links:
 
- * [Universal Viewer](https://uv-v4.netlify.app/#?c=&m=&s=&cv=&manifest=https://training.iiif.io/nlw-workshop/av-manifest.json)
- * [Mirador](https://projectmirador.org/embed/?iiif-content=https://training.iiif.io/nlw-workshop/av-manifest.json)
- * [Clover](https://samvera-labs.github.io/clover-iiif/docs/viewer/demo?iiif-content=https://training.iiif.io/nlw-workshop/av-manifest.json)
- * [Ramp](https://ramp.avalonmediasystem.org/?iiif-content=https://training.iiif.io/nlw-workshop/av-manifest.json)
- * [Avery](https://iiif.aviaryplatform.com/player?manifest=https://training.iiif.io/nlw-workshop/av-manifest.json)
- * [Theseus](https://theseusviewer.org/?iiif-content=https://training.iiif.io/nlw-workshop/av-manifest.json)
+ * [Universal Viewer 4](https://uv-v4.netlify.app/#?c=&m=&s=&cv=&manifest=https://glenrobson.github.io/iiif_stuff/nlw-workshop/av-manifest.json)
+ * [Universal Viewer 3](https://uv-v3.netlify.app/#?c=&m=&s=&cv=&manifest=https://glenrobson.github.io/iiif_stuff/nlw-workshop/av-manifest.json)
+ * [Mirador](https://projectmirador.org/embed/?iiif-content=https://glenrobson.github.io/iiif_stuff/nlw-workshop/av-manifest.json)
+ * [Clover](https://samvera-labs.github.io/clover-iiif/docs/viewer/demo?iiif-content=https://glenrobson.github.io/iiif_stuff/nlw-workshop/av-manifest.json)
+ * [Ramp](https://ramp.avalonmediasystem.org/?iiif-content=https://glenrobson.github.io/iiif_stuff/nlw-workshop/av-manifest.json)
+ * [Avery](https://iiif.aviaryplatform.com/player?manifest=https://glenrobson.github.io/iiif_stuff/nlw-workshop/av-manifest.json)
+ * [Theseus](https://theseusviewer.org/?iiif-content=https://glenrobson.github.io/iiif_stuff/nlw-workshop/av-manifest.json)
+
+
+ ## Playlist example
+
+ One thing that came up in discussion is to allow users to create a playlist of items. This could be done with a manifest with multiple canvases but you would loose a lot of the metadata. I think this would be done better with a IIIF collection like the following:
+
+ [Example AV Collection](https://glenrobson.github.io/iiif_stuff/nlw-workshop/playlist-collection.json)
+
+ It doesn't look like this is well supported in viewers yet:
+
+ * [Universal Viewer 4](https://uv-v4.netlify.app/#?c=&m=&s=&cv=&manifest=https://glenrobson.github.io/iiif_stuff/nlw-workshop/playlist-collection.json)
+ * [Universal Viewer 3](https://uv-v3.netlify.app/#?c=&m=&s=&cv=&manifest=https://glenrobson.github.io/iiif_stuff/nlw-workshop/playlist-collection.json)
+ * [Mirador](https://projectmirador.org/embed/?iiif-content=https://glenrobson.github.io/iiif_stuff/nlw-workshop/playlist-collection.json)
+ * [Clover](https://samvera-labs.github.io/clover-iiif/docs/viewer/demo?iiif-content=https://glenrobson.github.io/iiif_stuff/nlw-workshop/playlist-collection.json)
+ * [Ramp](https://ramp.avalonmediasystem.org/?iiif-content=https://glenrobson.github.io/iiif_stuff/nlw-workshop/playlist-collection.json)
+ * [Avery](https://iiif.aviaryplatform.com/player?manifest=https://glenrobson.github.io/iiif_stuff/nlw-workshop/playlist-collection.json)
+ * [Theseus](https://theseusviewer.org/?iiif-content=https://glenrobson.github.io/iiif_stuff/nlw-workshop/playlist-collection.json) 

nlw-workshop/imgs/tools/cookbook.png

@@ -1,11 +1,53 @@
 # Tools and Implementations
 
+## IIIF Cookbook
+https://iiif.io/api/cookbook
 
-cookbook
+![IIIF Cookbook](imgs/tools/cookbook.png)
 
+The IIIF Cookbook is maintained by volunteers and provides the following functions:
 
-Omeka-s: https://training.iiif.io/advanced_iiif/modules/omeka/
+ * Examples for beginners to copy. 
+ * Shows which viewers support which IIIF feature
+ * Gives viewer developers fixtures to test with
 
-Zooniverse: https://training.iiif.io/advanced_iiif/modules/zooniverse/
+Each recipe has gone through a formal review process and gives a guide to both IIIF publishers and viewer developers for accepted patterns. By detailing which viewers support which recipe it also provides a matrix so you can see the strengths and weaknesses of each viewer. It also solves a common problem with IIIF where the specification supports a feature but you don't know if its implemented in a viewer. If you create a test manifest you are unsure if its the viewer at fault or if you've made a mistake in the manifest.  
 
-Transkribus: https://www.transkribus.org/
+## Omeka-s 
+
+Omeka-s is a great way of creating digital exhibition or simple websites and integrates well with IIIF. Its possible to embed IIIF viewers and there are even plugings to enable a native IIIF image server. The guide below takes you through a use case at the University of Ghent where students are tasked with creating exhibitions using the Ghent digital collections. 
+
+https://training.iiif.io/advanced_iiif/modules/omeka/
+
+### Zooniverse 
+
+The British Library funded the support of IIIF within the Zooniverse crowdsourcing system. The guide below takes you through creating a IIIF enabled crowdsourcing project. 
+
+https://training.iiif.io/advanced_iiif/modules/zooniverse/
+
+## Transkribus
+
+Transkribus is a Handwriting Text Recognition system that can be trained to turn handwriting into annotations. You can import a IIIF manifest, then transcribe a portion of the text and create a model that will transcribe the rest of the content. They have some out of the box models that may work with some content but it works best with large collections of personal archives like diaries and letters written by the same person. 
+
+https://www.transkribus.org/
+
+## Glycerine
+
+Glycerine is a relatively new annotation system that is developed by a company in Australia. We have come across the viewer early in the course but it also has a annotation server that allows easy annotation of collections:
+
+https://glycerine.io/ 
+
+
+## liiive.now
+
+This is a very recent entrance to the IIIF annotation space. The early beta testing release came out over Christmas but it looks like it will be a very interesting collaborative annotation system. All of the other annotation systems are one person at a time systems or systems where the annotations are private. This is the first one which allows real time collaboration in a similar form to Google docs. 
+
+https://liiive.now/
+
+## More
+
+There are so many more exciting projects and the best place to find them is in the IIIF Community calls on [youtube](https://www.youtube.com/playlist?list=PLYPP1-8uH9c6VZbIlaNSj1WV9AEAnkmGC). Other ways to find IIIF compatible tools include:
+
+ * [IIIF Newsletter](https://iiif.io/newsletter/)
+ * [IIIF Conference](https://iiif.io/event/2025/leeds/)
+ * [IIIF slack](http://bit.ly/iiif-slack)