Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tutorial needs additional detail for query format, Crossref question example #151

Open
es87m opened this issue Feb 6, 2017 · 0 comments

Comments

@es87m
Copy link

es87m commented Feb 6, 2017

Greetings, I'm an end-user new to Content Mine. I understand that in a multi word query
-q alcohol dopamine will default to an OR' query (137K hits)
-q '"alcohol dopamine"' is of course an exact match (5 hits)
-q 'alcohol dopamine' seems to be an 'AND' query (5K hits) although that isn't clear in the tutorial and other complex mixtures don't work like I expect - such as -q '"alcohol dopamine" and "substance p"'

However, when using --api crossref as an option, I am unable to achieve the same idea.
Using the crossref web query page
alcohol dopamine 183K hits [OR search]
+alcohol +dopamine 500 hits [AND search +(force include term) !(force exclude term) ]
[and they don't seem to have a way to do exact match]

but with getpapers, using -api crossref
-q alcohol dopamine 151K hits
-q 'alcohol dopamine' or -q '"alcohol dopamine"' or '+alcohol +dopamine' or '"+alcohol +dopamine"' 201K hits

Hit numbers aside,I just looked at the crossref api github page, and although I understand there may be some technical details I can apply, it is my suggestion that it may be more complex than many end users will search for. Some API specific guidance in the tutorials, or in the long run, a back-end way for getpapers to format the query syntax for the particular API from a standard method of input from users would make for a consistent and pleasurable user experience.

Thank you very much to developers and testers for your work on the project, I look forward to using the application.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant