Uniqueness constraints for provider mappings are not enforced by the database or application for writes, but they are for reads

[ansell]

Uniqueness constraints for provider mappings are not enforced by the database or application for writes, but they are for reads.

There is nothing stopping one from creating a duplicate provider mapping in the database or application for writes, but then reads, including reads to the front page of the collectory app and the provider map listing service (no search interface for provider maps), fail due to grails detecting a duplicate and not being able to continue.

Tracking this even though I am aware it needs to be marked as "Won't Fix" due to the upcoming switch to GBIF registry so I have a reference when anyone refers to "BAU maintenance" in the future.