rdmorganiser / rdmorganiser/rdmo
Localise the standard catalogue via an additional "Local information" module
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 133
- Forks
- 60
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 21
Description
Users filling out the catalogue should not only get information on a certain topic to help them pick the right answers. They should also be hinted to local counsel and support, e.g. the legal department or a special RDM service.
The ideal constellation would be a generic basic catalogue hosted and updated centrally, which can be dynamically linked to local RDMO instances (applying updates should be optional). However, for each question it should be possible to display additional information stored in a separate module. Contact information and description of local services may also be derived from the Service-Verzeichnis Forschungsdaten, which could also be linked dynamically.
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
No files, tests, or entry points are identified in the issue. Begin by locating the catalogue and module implementation, then clarify the design for centrally hosted catalogues, optional updates, per-question local information, and possible Service-Verzeichnis Forschungsdaten links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100