Consider reorganizing metadata import code
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
As currently implemented, metadata import for the supported formats (DC, DDI...) is hard-coded in the application. We should consider changing it to something similar to how the exports are implemented (as Exporter classes that ExportService loads dynamically). This would make it easier to add support for more formats (and, potentially, for harvesting from more sources).
If we wanted to be really fancy, we could add support for loading these as real dynamic plugins, that could be dropped in place, without needing to add the code to the application project).
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 current hard-coded metadata import paths for the supported DC and DDI formats. Compare them with the Exporter classes and ExportService dynamic-loading approach. Done would mean a decided, maintainable import architecture that makes adding formats easier, with optional plugin loading addressed explicitly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100