The country shown as the publisher of a dataset in GBIF is currently derived from the publishing organization. This works well for datasets published directly by institutions in their own country, but not for datasets published through international aggregators or organizations acting on behalf of others.
This issue became particularly apparent for large citizen science aggregators such as eBird and iNaturalist, where datasets from many countries appeared to be published only from the country hosting the infrastructure. To address this, the non-Darwin Core term publishingCountry was introduced in the ingestion pipelines (see gbif/pipelines#678). These publishers use custom HTML publishing workflows rather than the IPT.
The same issue, however, affects many IPT-published datasets.
Examples include:
In these cases, the country where the publishing organization is located does not necessarily reflect the country responsible for publishing or producing the dataset.
Adding support in the IPT for the optional metadata term publishingCountry, would allow publishers to explicitly indicate the country (or countries, if supported) responsible for publishing the dataset.
This would make the IPT consistent with the existing pipeline support for publishingCountry and would allow all publishing workflows to provide the same information.
Supporting publishingCountry in the IPT would:
- provide a more accurate representation of countries' contributions to GBIF publishing;
- avoid systematic attribution of internationally managed datasets to the country hosting the publishing infrastructure;
- better represent networks, journals, companies and other organizations publishing on behalf of third parties;
- align IPT-published datasets with existing support already implemented for HTML publishers.
The country shown as the publisher of a dataset in GBIF is currently derived from the publishing organization. This works well for datasets published directly by institutions in their own country, but not for datasets published through international aggregators or organizations acting on behalf of others.
This issue became particularly apparent for large citizen science aggregators such as eBird and iNaturalist, where datasets from many countries appeared to be published only from the country hosting the infrastructure. To address this, the non-Darwin Core term publishingCountry was introduced in the ingestion pipelines (see gbif/pipelines#678). These publishers use custom HTML publishing workflows rather than the IPT.
The same issue, however, affects many IPT-published datasets.
Examples include:
https://www.gbif.org/dataset/search?publishingOrg=2089ce96-4fb5-4a20-999c-3ccf45a27a4d
https://www.gbif.org/dataset/0f83e46d-1a5a-4d3b-97a4-6156b615f297
https://www.gbif.org/dataset/7596f321-4577-4cca-aeb5-2782d0149493
In these cases, the country where the publishing organization is located does not necessarily reflect the country responsible for publishing or producing the dataset.
Adding support in the IPT for the optional metadata term publishingCountry, would allow publishers to explicitly indicate the country (or countries, if supported) responsible for publishing the dataset.
This would make the IPT consistent with the existing pipeline support for publishingCountry and would allow all publishing workflows to provide the same information.
Supporting publishingCountry in the IPT would: