Recipe #464: Reuse parts of a manifest

[glenrobson]

Links

• Original Issue: Re-use of Manifests cookbook-recipes#464
• Pull Request: Recipe on Manifest reuse. cookbook-recipes#588
• Preview: https://preview.iiif.io/cookbook/0464-reuse-manifest/recipe/0464-reuse-manifest/

Background and Summary

This is an often request recipe which recomends how to approperatly credit the original manifest and provide a link to the original when you edit a manifest published by someone else. This is often done when someone wants to publiush a new manifest with annotations, add a structure or in some other way enhance a manfiest with which the editor doesn't have control over.

Voting and changes

We welcome comments on the recipe and as well as voting +1, confused face or -1 feel free to add comments to this issue. If this issue is approved then the author will take account of the comments before we merge the branch in to the master cookbook branch.

If the recipe is rejected by the TRC then we will make the changes requested and resubmit it to a future TRC meeting. If you feel that your comments are substantial enough that the recipe should be looked at again by the TRC after the changes have been made please vote -1 (thumbs down). A confused face is treated as abstaining.

Changes to the recipe will only be made after the TRC voting process has concluded.

[triplingual]

You should copy the Canvases preserving the URI in their id property unless you modify the Canvas itself. This indicates that additions like Annotations made by you would also apply to the original Canvas in the source Manifest.

After talking about this in the TRC call and thinking about it some more, I think I'd recommend slightly changing this to

You should copy the Canvases, preserving the URI in their id property unless you modify the Canvas itself. This indicates that additions you make, such as Annotations, also refer to the original Canvas in the source Manifest.

Modest grammatical changes, but more importantly, changing "apply" to "refer" thinking that keeps the semantic point but would make, I hope, a novice IIIF person less concerned that the Annotations will attach to the original Canvas. It might just need more language, but maybe this works.

[regisrob]

This is a useful recipe, thanks @robcast and cookbook editors.

I was wondering if it would be desirable to also describe a machine-readable way of pointing to another Manifest. For example it might be interesting for plateforms like FromThePage and others to reference the original Manifest in a structured manner, in addition to simply putting it in metadata. FromThePage uses a dc:source metadata field for this, e.g. in this Manifest, but other producers may use other labels like Original Manifest or Source Manifest etc.).

This issue from 2017 tackles this question in the context of Presentation API 2.

I do not know if using seeAlso would still be considered as a valid option to do so, and, if yes, if the above syntax would be valid as well (not sure about the value of profile especially...):

"seeAlso": [
        {
          "id": "https://iiif.io/api/cookbook/recipe/0008-rights/manifest.json",
          "type": "Manifest",
          "label": { "en": [ "Source Manifest" ] },
          "format": "application/ld+json",
          "profile": "http://iiif.io/api/presentation/3#"
        }
]

What do you think? This use case could also be considered out-of-scope for that recipe.

[mikeapp]

At a meeting a few weeks ago the Editors agreed on adding canonical and via ( https://www.w3.org/TR/annotation-model/#other-identities ) to Presentation 4 ... see IIIF/api#2213 (comment).

[glenrobson]

Issue 134 (Recipe #464: Reuse parts of a manifest)

+1: 14 [akrishnan15 annhanlon azaroth42 cubap danieltbrennan glenrobson irv jamesmisson ksclarke nfreire regisrob robcast tpendragon zimeon]
0: 0 []
-1: 0 []
Not TRC: 0 []
Ineligible: 3 [LlGC-iir markpatton markpbaggett]

Result: 14 / 14 = 1.00

Super majority is in favor, issue is approved