Support accessibility metadata (#701)#705
Conversation
… data model and API
…fields to thoth-app
…ame existing field for compatibility
…ted fields shouldn't prevent ingest)
…a11y fields not yet supported in 2.1)
… yet supported in 2.1)
| contact_id UUID PRIMARY KEY DEFAULT uuid_generate_v4(), | ||
| publisher_id UUID NOT NULL REFERENCES publisher(publisher_id) ON DELETE CASCADE, | ||
| contact_type contact_type NOT NULL DEFAULT 'Accessibility', | ||
| email TEXT NOT NULL CHECK (octet_length(email) >= 1), |
There was a problem hiding this comment.
This wasn't in the scope of your work, but ONIX 3.1.2 now includes Street Address, Location, Postal Code, and Country Code for Product Safety Contact for EU GPSR compliance: https://www.editeur.org/files/ONIX%203/APPNOTE%20Product%20safety%20requirements%20in%20ONIX.pdf
So we should decide whether to implement this now, or add these fields later when we work on a separate PR to implement EU GPSR compliance.
I put this comment on the contact table, rather than publisher, because according to Editeur, in the case of EU GPSR, "If the ‘manufacturer’ is not based in the European Union, the details of a
responsible entity within the EU 5 – the importer, in-EU distributor or other authorized
representative of the publisher – must be provided and displayed instead"
So a publisher might (confusingly) have multiple physical addresses, which makes a case to have them be part of contact, rather than publisher.
There was a problem hiding this comment.
Are we going to consider having an end of support date for the Thoth ONIX 3.0 output? It seems like in the long run, it's going to be a lot of work to maintain both this and the ONIX 3.1 outputs, and they're so similar.
3 participants
Fixes #701. Related to #577.
Adds support for various accessibility metadata fields to data model, API, and ONIX outputs. No new fields added to APP interface.
New fields added to all ONIX outputs where this is valid ONIX, as the metadata is required for EAA compliance. However, not all target platforms have made it clear yet whether they have started supporting this metadata. On release, we should monitor submissions to these platforms in case of issues.
This PR also includes some fixes for #682.