Make temporal, spatial, taxonomic scope non-required?

[peterdesmet]

The temporal, geographic and taxonomic scope are currently required terms in the metadata. All three terms can be derived from the data, i.e.:

• temporal: based on min/max deployment start/end
• spatial: based on min/max deployment latitude/longitude to create a bounding box. One can also express more complex shapes in geojson.
• taxonomic: listing all unique taxonID/scientificName. This can be completed with more information, such as higher classification, vernacular names etc.

Since these scopes can to a large part be created by software, one can argue that it makes sense to make them required. But it will be an impediment for users who don't have such software and have to "handcraft" a Camtrap DP. Like users of the GBIF IPT, which currently provides functionality to create the scopes, but only manually:

Especially for taxonomic scope, this is tedious and can lead to inconsistencies (scope doesn't fit data) or incompleteness (e.g. only a few taxa provided). I think we better reserve the terms for cases where software (such as data management platforms or even software reading a Camtrap DP) can provide complete overviews from the data.

I would therefore also remove the manual entry forms in the IPT. Users will still be able to upload a datapackage.json to the IPT that contains that information. The alternative is to have the IPT generate those scopes (if not provided in the upload), but that is maybe out of scope for the intent of the IPT.

@kbubnicki @timrobertson100 @mike-podolskiy90 thoughts?

[peterdesmet]

The update to the IPT implementation is suggested in https://github.com/gbif/ipt/issues/2047. Closing this issue, we will keep the scopes required.