openlibhums / openlibhums/janeway
RDF graph for ing.grid - Missing information from the repository API
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 239
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
The IT staff of our library is currently working on triplifying ing.grid information into RDF triples. They are working on the data that is published through the ing.grid APIs.
In this context, they encountered a few issues. They will benefit the semantics behind data they are trying to triplify and currently not visible through the APIs. They wanted to discuss whether it would be possible to publish them along with the information published.
- The ORCIDs of the authors involved
- DOIs of the articles
- Versions and their respective published/revised dates of articles
- Comments by users on every version
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 reviewing the repository API endpoints that expose article, version, and user-comment data, then read the issue discussion for agreed scope. The work is done when the APIs publish author ORCIDs, article DOIs, version publication and revision dates, and comments for every version, with the intended semantics documented or confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100