When we release a vocabulary we push JSON to nexus, such as this example.
However, this returns a different JSON document from the GBIF API for the same release. This one has a "tags".
This might be by design (e.g. to allow a UI to compare content across releases while still allowing new features to be added) but I think it might cause some confusion. Once released, it would be more intuitive to always treat released vocabularies as immutable.
marcos-lg
commented
3 years ago
When we release a vocabulary we push JSON to nexus, such as this example.
However, this returns a different JSON document from the GBIF API for the same release. This one has a "tags".
This might be by design (e.g. to allow a UI to compare content across releases while still allowing new features to be added) but I think it might cause some confusion. Once released, it would be more intuitive to always treat released vocabularies as immutable.
Discovered in production here