Part of: pyOpenSci/software-submission#267 (comment)
The documentation (
|
Working with Different Data Sources |
|
------------------------------------ |
|
|
|
OneCite routes queries to data sources based on content type: |
|
|
|
**For Biomedical Literature** |
|
|
|
Add search terms related to medicine, biology, or health:: |
|
|
|
onecite process medical_refs.txt |
|
|
|
This will prioritize PubMed when available. |
|
|
|
**For Computer Science** |
|
|
|
Add search terms related to CS topics:: |
|
|
|
onecite process cs_refs.txt |
|
|
|
This will prioritize DBLP and arXiv. |
|
|
|
**For General Academic Work** |
|
|
|
Mixed references will use CrossRef and Semantic Scholar:: |
|
|
|
onecite process general_refs.txt |
) reads:
OneCite routes queries to data sources based on content type:
For Biomedical Literature
Add search terms related to medicine, biology, or health:
onecite process medical_refs.txt
This will prioritize PubMed when available.
For Computer Science
Add search terms related to CS topics:
onecite process cs_refs.txt
This will prioritize DBLP and arXiv.
For General Academic Work
Mixed references will use CrossRef and Semantic Scholar:
onecite process general_refs.txt
This appears to suggest that the filename used when defining input references affects the program operation somehow. However i find no mechanism for that.
The file is read here:
and the filename is never referenced again
Part of: pyOpenSci/software-submission#267 (comment)
The documentation (
OneCite/docs/advanced_usage.rst
Lines 51 to 76 in 12b1dea
This appears to suggest that the filename used when defining input references affects the program operation somehow. However i find no mechanism for that.
The file is read here:
OneCite/onecite/cli.py
Line 125 in 12b1dea
and the filename is never referenced again