Unable to define subject metadata when creating Dataset using the SWORD API
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
The SWORD API Docs explains this rule:
"Subject” uses our controlled vocabulary list of subjects. This list is in the Citation Metadata of our User Guide > Metadata References. Otherwise, if a term does not match our controlled vocabulary list, it will put any subject terms in “Keyword”. If Subject is empty it is automatically populated with “N/A”.
Tried different ways to define the subject, by using the controlled vocabulary table, but all of them resulted on datasets with empty subjects and value filled into the keyword metadata.
Example of values used on the subject: Physics, D10, 11
Don't know if it's a bug, but some example payloads to create Datasets would certainly help in using the SWORD API.
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 with the SWORD API documentation and reproduce dataset creation using the reported subject values: Physics, D10, and 11. Compare the resulting subject and keyword metadata, then check whether the controlled-vocabulary behavior is documented or implemented as described. Done means either valid subjects are stored correctly or the supported payload format is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100