Publishing datasets with invalid EML

[mike-podolskiy90]

There are many datasets at gibf.org with invalid metadata with different issues.

For example, many PANGAEA datasets https://registry.gbif.org/installation/600586fe-f762-11e1-a439-00145eb45e9a do not have abstract (description) which is a required field in the GBIF EML profile.

Some other datasets do not have creators and other required fields.

Problem is, it is not indicated anywhere, that the dataset has an invalid EML. Should it be somewhere?

Copying @gbif/dataproducts

[CecSve]

Problem is, it is not indicated anywhere, that the dataset has an invalid EML. Should it be somewhere?

Could it be captured somehow with a machine tag? Then we could use that to find publishers and contact them. Or at least keep track of which datasets, installations, and publishers have that issue.

[mike-podolskiy90]

Thanks Cecilie

I can add machine tags to those datasets by a script if it's needed

[mike-podolskiy90]

But I guess it would be better to do that during ingestion

[MattBlissett]

A modification to the crawler and/or registry to update the tags (including removing a tag once the EML becomes valid) would be best.

Registry is probably the place for this.