diff --git a/recipe/0032-collection/index.md b/recipe/0032-collection/index.md index 8916e58b5..8df4e4027 100644 --- a/recipe/0032-collection/index.md +++ b/recipe/0032-collection/index.md @@ -8,27 +8,28 @@ viewers: - UV - Mirador - Clover + - Annona topic: - basic --- ## Use Case -Your organization has a named digital collection of artworks authored by a specific person. Each of these unique items are already digital objects represented by Manifests and you would now like to organize and present them as an ordered IIIF Presentation resource. +Your organization has a named collection of artworks authored by a specific person. Each of these unique items already has a digital representation and a Manifest, and you would now like to organize and present them together in a unified and coherent IIIF Presentation interface. ## Implementation notes This recipe illustrates the mandatory structure and properties of a IIIF Collection of Manifests, with the simplest possible content. IIIF Collections have no restrictions on the organizational purpose of their referenced resources, though the resources may be related as a named digital collection, a common metadata value, or be organized as search results. -Like with a Manifest, The JSON-LD of a Collection opens with the`@context` declaration, which identifies the terms used in the document as belonging to the IIIF specification. The `id` property identifies this collection with the URL at which it is available online. The `type` property must be `Collection`. +Like with a Manifest, the JSON-LD of a Collection opens with the`@context` declaration, which identifies the terms used in the document as belonging to the IIIF specification. The `id` property identifies this collection with the URL at which it is available online. The `type` property must be `Collection`. As with a Manifest, the `label` property is mandatory, and the language of its value must be given (or the special value `none`), using a [language map](https://iiif.io/api/presentation/3.0/#language-of-property-values). Here the language of the `label` is English and its value is “Simple Collection Example”. -The Collection `items` property is an array of referenced Manifests. In this example there are two Manifests. Each `items` entry must have an `id`, `type`, and a `label`. The `id` must be the URI where the Manifest can be available online. The `type` must be `Manifest` or a `Collection`. Each `items` entry referenced should not be full embedded into the Collection, and should contain only necessary properties for presentation of the collection such as thumbnail. Various other [descriptive](https://iiif.io/api/presentation/3.0/#31-descriptive-properties) and [linking](https://iiif.io/api/presentation/3.0/#33-linking-properties) properties such as `summary`, minimal `metadata`, and `homepage` may be useful as well for presentation. See the [Summary of property requirements](https://iiif.io/api/presentation/3.0/#a-summary-of-property-requirements) for a complete list. +The Collection `items` property is an array of referenced Manifests. In this example there are two Manifests. Each `items` entry must have an `id`, `type`, and a `label`. The `id` must be the URI where the Manifest can be available online. The `type` must be `Manifest` or a `Collection`. Each `items` entry referenced should not be fully embedded into the Collection, and should contain only necessary properties for presentation of the collection such as `thumbnail`. Various other [descriptive](https://iiif.io/api/presentation/3.0/#31-descriptive-properties) and [linking](https://iiif.io/api/presentation/3.0/#33-linking-properties) properties such as `summary`, minimal `metadata`, and `homepage` may be useful as well for presentation. See the [Summary of property requirements](https://iiif.io/api/presentation/3.0/#a-summary-of-property-requirements) for a complete list. -Collections may also reference other Collections as sub-collections. +Collections may also reference other Collections. -Collections may have [`behavior`](https://iiif.io/api/presentation/3.0/#behavior) defined in order to influence user experience when viewing the resource. Manifests within a collection DO NOT inherit behaviors from their referencing Collections, however referenced Collections will. +Collections may have [`behavior`](https://iiif.io/api/presentation/3.0/#behavior) defined in order to influence user experience when viewing the resource. Manifests within a Collection DO NOT inherit behaviors from their referencing Collections; however referenced Collections will. ## Restrictions