Feature Request/Idea: Installing an harvesting protocol parser with Java SPI
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
As many want to add new harvesting protocols to the 3 existing protocols : OAI DC, OAI DDI + dataverse_json;
What about having the capability to add a Java Service Provider Interface (SPI) plugin to support a new harvesting protocol parser (like Installing External Metadata Exporters) ?
The community could have an easier time adding to the harvesting feature.
This have been mentioned in the code back in 2016 : https://github.com/IQSS/dataverse/blob/8c99a74f854a62050d850dccf30246c2fb06a5b9/src/main/java/edu/harvard/iq/dataverse/api/imports/ImportServiceBean.java#L219
- Example : #1592
- Linked issue : https://github.com/IQSS/dataverse-pm/issues/171
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 reading ImportServiceBean.java at the referenced 2016 location, the external metadata exporters guidance, and example issue #1592. Compare those references with the three existing harvesting protocols, then clarify the SPI scope, extension points, and completion criteria with maintainers.
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
- Needs clarification
- Newbie friendliness
- 25/100