Bundle CSV metadata into IIIF manifests

[bmschmidt]

Wax cites FAIR user principles and has a re-use tab, but it shares metadata as tables rather than linking it inside the IIIF. Some forms of re-use would be better supported by including all metadata in the IIIF presentation manifests. This should be relatively simple, perhaps as a post-processing step on the current products of wax:derivatives:iiif if mucking around the current derivative code is too hard.

It would just be adding an additional key to the json for metadata with the serialized row.

Reference example here.

This would be a good first task for someone looking to the contribute to the codebase with little/no experience in Ruby.

"metadata": [
{
"label": "Label",
"value": "Portrait of Hasan 'Ali Mirza Shuja al-Saltana"
},
{
"label": "Artist",
"value": "Unknown"
}
...
]

[dnoneill]

I tried contributing this at one point. It was decided that this is something they did not want to add. Maybe things have changed.
minicomp/wax_tasks#42

[bmschmidt]

That seems like good work, thanks.

Reading the old discussion, it looks like most of the concerns there had to do with automatically ingesting label, description, attribution, etc. into the top level of the IIIF manifest, when someone might use attribution for, like, putative authorship instead of a credit line. But if I'm reading this right here, https://github.com/minicomp/wax_tasks/blob/fd222e220911f6ef1d5f885c61a74c1e1ba11c5c/lib/wax_tasks/item.rb#L70-L102 iiif_config in the yaml file only supports adding top_level metadata fields like these. (I can't seem to find any documentation on iiif_config in the wiki, though?)

Your code also does what I propose, which is blindly populate the 'metadata' field of the manifest from the CSV. Currently wax manifests have no metadata; https://iiif.io/api/presentation/2.1/#metadata says "A manifest SHOULD have one or more metadata pairs associated with it describing the object or work." So picking that part of the old request would bring wax into better IIIF conformance.

[martimpassos]

+1, it seems pretty natural that Wax would at least be able to create fully fledged manifests if asked for it. If that's already possible with iiif_config, could someone provide minimal documentation for it?