rdmorganiser / rdmorganiser/rdmo
Support metadata standard mappings for attributes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 133
- Forks
- 60
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 21
Description
Rationale / Begründung
RDMO attributes represent the semantic meaning of collected information, but they cannot currently be explicitly mapped to terms from established metadata standards or vocabularies.
Such mappings would improve semantic interoperability and make RDMO data easier to reuse in other systems and metadata formats.
Affected
Managers, who create and maintain catalogs.
External systems and integrations that reuse, exchange, or process data from RDMO.
Minimal functionality
Allow managers to assign one or more metadata terms from established standards or vocabularies, such as DCAT-AP.de or Dublin Core, to an attribute.
Mappings should:
- be included in XML exports and preserved during XML imports;
- be displayed in the management panel; and
- be available via the API.
Nice-to-have functionality
References / Verweise
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 tracing attribute handling through the XML export and import paths, management panel, and API entry points. Done means managers can assign one or more metadata-standard terms to an attribute, mappings survive XML round trips, appear in the management panel, and are exposed through the API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend-api-design, full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100