citation-js / citation-js/toolforge-tool
Input: references
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
As we want to restrict input, we cannot pass extra information from references along with stated in. This means missing out on reference URL, retrieved, and identifiers. The tool can instead take reference URIs as input and retrieve that information itself.
SELECT ?ref ?statedIn ?formatterUrl ?identifier ?referenceUrl ?retrieved WHERE {
VALUES ?ref { wdref:005bca173b32a7c8f623bbeb832a152889e8f4e3 }
OPTIONAL {
?ref pr:P248 ?statedIn .
OPTIONAL {
?statedIn ^wdt:P9073 ?identifierProperty .
?identifierProperty wikibase:reference ?identifierPropertyReference .
OPTIONAL {
?identifierProperty wdt:P1630 ?formatterUrl .
}
?ref ?identifierPropertyReference ?identifier .
}
}
OPTIONAL {
?ref pr:P854 ?referenceUrl .
}
OPTIONAL {
?ref pr:P813 ?retrieved .
}
}
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 tool's input handling and the code path that processes the supplied reference URIs, then compare its behavior with the SPARQL query in the issue. Done means reference URIs can be accepted and the available stated-in, identifier, reference URL, and retrieved information is returned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100