You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we publish a project on PhysioNet, we also create a DOI and publish various metadata using the DataCite API.
From time to time we may want to make improvements to this metadata, such as by adding new fields (e.g. pull #2154, #2119).
It is also possible - though discouraged! - for site administrators to modify projects after publication, such as to fix a typo in a project title or an author's name.
In both cases, we want to update the information for existing projects. It doesn't have to be done immediately but it should be done reasonably quickly, and automatically.
We could try to track whether a particular DOI needs updating, but this could be complicated and error-prone. It feels like it would be better just to update all published DOIs regularly (say, once a week), as long as it's not a burden on the API.
The text was updated successfully, but these errors were encountered:
Recently Tom mentioned that PhysioNet publications appear (magically?) on people's ORCID profiles.
Since that's not anything we're doing, I assume that it happens because ORCID pulls the information from DataCite.
So that is another important case: we need to regularly re-publish DataCite info so that ORCID will see it (authors can always add/remove an ORCID profile after publishing projects.)
When we publish a project on PhysioNet, we also create a DOI and publish various metadata using the DataCite API.
From time to time we may want to make improvements to this metadata, such as by adding new fields (e.g. pull #2154, #2119).
It is also possible - though discouraged! - for site administrators to modify projects after publication, such as to fix a typo in a project title or an author's name.
In both cases, we want to update the information for existing projects. It doesn't have to be done immediately but it should be done reasonably quickly, and automatically.
We could try to track whether a particular DOI needs updating, but this could be complicated and error-prone. It feels like it would be better just to update all published DOIs regularly (say, once a week), as long as it's not a burden on the API.
The text was updated successfully, but these errors were encountered: