Persistent ID: Provide optional timer job to periodically verify resolution of all dataset persistent ids, handle and doi.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Eleni mentioned this came up as part of the DataCite membership application: what steps do we take as a repo to maintain or verify continued operation and resolution of persistent ids.
At this time we monitor whether the handle service is running but we have some tickets open to make the registration process more robust to handle times of remote service outages for both handle and dois.
What we are missing is the post registration piece where properly registered ids (or otherwise) are checked to confirm ids resolve properly and if not are either resolved automatically or notification is sent to an admin for attention.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing persistent ID registration and monitoring paths for Handle and DOI services. Review how remote-service outages are handled, then determine where a periodic verification job and admin notification or automatic recovery would fit. Done means registered dataset IDs are checked for resolution and failures receive the agreed response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100