Automatic or Manually Assisted: Automatic
Programming Language(s): PHP w/ Snoopy & BasicBot
Function Summary: Adds DOIs to citations provided using {{ cite journal}}
Edit period(s) (e.g. Continuous, daily, one time run): Will do a thorough job every few months; will be available to be used on specific articles whenever requested.
Edit rate requested: 6 edits per minute. In reality the querying of other websites will be the rate limiting step.
Function Details: Adds a permanent link to any article cited using {{ cite journal}}.
url
parameterurl
paremeter for a DOItitle
and author
parameters to form a precise query. The precise search guarantees that the URL is of relevance to the article. If this URL contains a DOI, this is added to the citation; if not, the URL is added.Operator: Verisimilus T
That sounds really cool, who's operating it? SQL Query me! 20:57, 12 March 2008 (UTC) reply
A few questions:
For #3, how do you propose to know that the DOI you found belongs to the article you are looking for, and not for example, have it be from a list of references, or a see also section on the page. Are you going to do some kind of secondary check (i.e. resolve the DOI you found and see if it matches the author and title)? Also, what happens if the titles (or authors, for that matter) are not exact matches (I know they should be, but lets consider reality).
For #4 and #5, are we going to run into the same problem as CorenSearchBot (see section 5.3 of the Google Terms of Service)? Quoted here for convenience:
5.3 You agree not to access (or attempt to access) any of the Services by any means other than through the interface that is provided by Google, unless you have been specifically allowed to do so in a separate agreement with Google. You specifically agree not to access (or attempt to access) any of the Services through any automated means (including use of scripts or web crawlers) and shall ensure that you comply with the instructions set out in any robots.txt file present on the Services.
Thank you for your interest in Google Scholar. At this time, we don't allow automated queries on our index. This is for a number of reasons, both technical and due to agreements with content providers. While we don't have an API available for Google Scholar, I appreciate this feature request and have passed your email and comment on to the relevant engineers on our team.
Thanks. And this bot does sound really interesting. - AWeenieMan ( talk) 23:29, 12 March 2008 (UTC) reply
I am liking your new logic, myself. It is too bad about Google, but not much can be done. Inexact title matching shouldn't be too hard to do (in a simple way), if you are interested. I usually use a Levenshtein distance algorithm ( php.net) for such things. - AWeenieMan ( talk) 20:39, 13 March 2008 (UTC) reply
What's the status of this request? — Werdna talk 13:55, 4 April 2008 (UTC) reply
Approved.
MaxSem(
Han shot first!) 10:02, 12 April 2008 (UTC)
reply
Automatic or Manually Assisted: Automatic
Programming Language(s): PHP w/ Snoopy & BasicBot
Function Summary: Adds DOIs to citations provided using {{ cite journal}}
Edit period(s) (e.g. Continuous, daily, one time run): Will do a thorough job every few months; will be available to be used on specific articles whenever requested.
Edit rate requested: 6 edits per minute. In reality the querying of other websites will be the rate limiting step.
Function Details: Adds a permanent link to any article cited using {{ cite journal}}.
url
parameterurl
paremeter for a DOItitle
and author
parameters to form a precise query. The precise search guarantees that the URL is of relevance to the article. If this URL contains a DOI, this is added to the citation; if not, the URL is added.Operator: Verisimilus T
That sounds really cool, who's operating it? SQL Query me! 20:57, 12 March 2008 (UTC) reply
A few questions:
For #3, how do you propose to know that the DOI you found belongs to the article you are looking for, and not for example, have it be from a list of references, or a see also section on the page. Are you going to do some kind of secondary check (i.e. resolve the DOI you found and see if it matches the author and title)? Also, what happens if the titles (or authors, for that matter) are not exact matches (I know they should be, but lets consider reality).
For #4 and #5, are we going to run into the same problem as CorenSearchBot (see section 5.3 of the Google Terms of Service)? Quoted here for convenience:
5.3 You agree not to access (or attempt to access) any of the Services by any means other than through the interface that is provided by Google, unless you have been specifically allowed to do so in a separate agreement with Google. You specifically agree not to access (or attempt to access) any of the Services through any automated means (including use of scripts or web crawlers) and shall ensure that you comply with the instructions set out in any robots.txt file present on the Services.
Thank you for your interest in Google Scholar. At this time, we don't allow automated queries on our index. This is for a number of reasons, both technical and due to agreements with content providers. While we don't have an API available for Google Scholar, I appreciate this feature request and have passed your email and comment on to the relevant engineers on our team.
Thanks. And this bot does sound really interesting. - AWeenieMan ( talk) 23:29, 12 March 2008 (UTC) reply
I am liking your new logic, myself. It is too bad about Google, but not much can be done. Inexact title matching shouldn't be too hard to do (in a simple way), if you are interested. I usually use a Levenshtein distance algorithm ( php.net) for such things. - AWeenieMan ( talk) 20:39, 13 March 2008 (UTC) reply
What's the status of this request? — Werdna talk 13:55, 4 April 2008 (UTC) reply
Approved.
MaxSem(
Han shot first!) 10:02, 12 April 2008 (UTC)
reply