Closed Hobbesball closed 5 years ago
other possible implementation implement as above, but don't create a separate command and instead run this at the end of ETL5
Added in 2306938861d0b4b49ffa34825310431c1867b0c9
The top-level collection is also validated the same way as the manifests (using the same 'validate_manifests' toggle). The collection passes validation, but for some reason the validator returns the following warning:
WARNING: 'top' not a known viewing hint for type 'sc:Collection': individuals multi-part
Despite the IIIF presentation API documentation example having a 'viewingHint: top', the python implementation of the validator expects either 'individuals' or 'multi-part' as viewingHint. See also: https://github.com/iiif-prezi/iiif-prezi/blob/master/iiif_prezi/factory.py,
COLL_VIEWINGHINTS = ['individuals', 'multi-part']
the viewinghint:top is technically only valid for ranges, and a top-level collection is not a range. That said, looking at other top-level collections from other organisations they also use viewinghint:top. I would disregard this warning, thanks for flagging it!
Detailed description of the issue. Having a page that lists all the available IIIF manifests in the imagehub enhances the discoverability of the imagehub manifests. In the same way that datahub has the ListRecords command to show all available LIDO records, a similar function for imagehub is needed.
Possible implementation This can be implemented in several different ways, but following the possibilities of the IIIF spec seems like the most elegant solution. a top-level IIIF Collection is a JSON file that gives a list of manifests. cfr. IIIF v.1. spec about Collections.
an example Collection JSON file would look like this: