kit-data-manager / kit-data-manager/pit-service
Communication of urgent changes
- Dominant language
- Java
- Stars
- 3
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
(From HMC CCT3, Versioning discussions) As a consequence of the above: how does someone communicate an urgent patch / change to HMC central services or the whole FDO-based digital ecosystem? As a user, that is. E.g. a real-time registry of urgent patches or announcements which can be used to cross-check any holding of FDOs inside or outside Helmholtz
Contributor guide
Research direction
Start by reviewing the referenced HMC CCT3 versioning discussions and the repository description for its typed PID and FAIR DO scope. Define the user-facing requirements for urgent patch or announcement communication and how users would cross-check held FDOs. Done requires an agreed mechanism and clear integration scope for the FDO-based ecosystem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100