Open GoogleCodeExporter opened 9 years ago
From a library developers point of view it would be great if we could integrate
google scholar results into our own systems.
Original comment by mcsmith1...@gmail.com
on 6 Feb 2009 at 11:16
+.Net C# wrapper
Original comment by qingping...@gmail.com
on 6 Feb 2009 at 1:16
+1. This would be a really useful feature for any bibligraphic management or
recommender tools.
Original comment by euan.a...@gmail.com
on 14 Feb 2009 at 6:16
An app to generate a 'tree of knowledge'. The app identifies parent documents
that
have been cited by x of your current biblio's documents. As these are defined,
the
app then suggests 'sibling' documents that also cite these parent documents.
This
will quickly generate multiple generations of citation, and the user qualifies
suggested documents, maintaining or increasing the focus of the suggestions.
By using cross-citation and correlation of one-way ('upstream') citation to
parent
works, the app could model the literature of a given topic in an organic way.
That
would be sweet. That might be a little beyond the function of the same app
though.
Original comment by ashoo...@gmail.com
on 18 Feb 2009 at 2:05
+1. Publish or Perish (PoP) (http://www.harzing.com/pop.htm) is the most
innovative
use of Google Scholar I've seen. It automates computing author's citation
metrics to
measure their scientific output.
Adding facility for disambiguation of authors would be tremendously valuable,
so you
could determine that "Smith, J." in this context refers to same author
mentioned as
"Smith, John" and not "Smith, James". PoP lets you select checkboxes next to
each
paper to assist with this disambiguation but its time-consuming and
error-prone. I'm
not sure what the solution would look like (maybe an OpenID validation of
authors or
possibly the disambiguation could be community moderated?) The most obvious
improvement would be to profile the topics and subject domains each author
publishes
on (and the journals they've appeared in, and the co-authorship of the papers)
and
determine that author "Smith, J." who writes on topic X is likely to be "Smith,
John"
and not "Smith, James" who writes on vastly different topic Y.
These are some ideas I've deliberated while working on an R&D project for the
Department of Energy that attempts to bring scientific credibility to the
blogosphere
-
http://wiki.milcord.com/wiki/Personalized_Web_2.0_Service_for_Authoritative_Cont
ent
Let's hope something comes of this thread.
Original comment by burkes...@gmail.com
on 23 Feb 2009 at 8:28
+1. It will be great if google scholar api is available!
Original comment by chienmin...@gmail.com
on 9 Mar 2009 at 6:12
+1 but for those who can't wait, building a mashup from
- http://www.programmableweb.com/apitag/science
- http://www.programmableweb.com/apitag/education
- http://www.programmableweb.com/apitag/research
- http://isbndb.com/docs/api/index.html
could do the trick, Im still trying to monitor publisher and journals API (and
not
just RSS feeds) but it seems to be taking a while for them to get the idea.
Maybe
they are still into information locks...
Original comment by utop...@gmail.com
on 11 Mar 2009 at 8:32
I am submitting a grant application to the National Library of Medicine for a
search
engine for health sciences. API to Google Scholar would help immensely so I
could
grab citation frequencies for articles based on their PubMed identifier (PMID)
or
digital object identifier (DOI).
Original comment by bob.badg...@gmail.com
on 18 Mar 2009 at 4:05
+1. Another nice feature would be to get a citation count by the title of a
article.
Original comment by CSilv...@gmail.com
on 1 Apr 2009 at 6:05
+1. Use-case: A Google Scholar API would enable web-based visualizations of
academic
ontologies. A very good application already exists for this: <a
href="http://papercube.peterbergstrom.com/">PaperCube<a>. Unfortunately, it is
using
CiteSeer, which provides a suboptimal data set. With a Google Scholar API
back-end to
feed the PaperCube front-end, we would have an extraordinarily valuable
resource for
performing scientific research.
Original comment by otakuj...@gmail.com
on 6 Apr 2009 at 6:09
Please Please make Google Scholar API an Open Source :)
Original comment by ba.amit...@gmail.com
on 8 Apr 2009 at 8:19
I vote for this also. I manage a couple of sites where lecturers can enter
information about books or papers that students can read for their courses.
Ideally
it should be as easy as possible for the lecturer to specify the resource that
they
are interested in, and then the system should generate links to embed in the
pages
shown to students. Those links should refer unambiguously to the right
resource, and
they should make it as easy as possible for the students to access that
resource,
either by buying a copy, finding it in a library, or reading it online. I can
do a
good job of this for books with the book search API. A Google Scholar API
would make
it easier for me to do the same with papers.
Original comment by N.P.Stri...@googlemail.com
on 10 Apr 2009 at 6:07
[deleted comment]
I could really use this. I would in fact use it in a way that would deliver
people to
Google Scholar pages.
When I have a known citation in my system, I'd like to look it up in Google
Scholar
and find out how many 'cited by' hits G.Scholar has. If non-0, I would provide
a link
to the 'cited by' listing for that original citation -- a link to the original
page
on Google Scholar.
I would be sending users to Google Scholar who might not ordinarily be using
it.
Original comment by jonathan...@gtempaccount.com
on 14 Apr 2009 at 3:25
This would be a very helpful extension of the API!
Original comment by jafarian...@gmail.com
on 15 Apr 2009 at 12:13
I would certainly vote for a Google Scholar API. Academics rely on citation
numbers
to guide them through the web of academic papers. I personally would like to
see
some application that would color code citations in papers so when looking
through
the list of references one would get an immediate impression of which were the
most
authoritative papers being cited. I've started work on something like this
using a
Google Scholar screen scraping approach:
http://linklens.blogspot.com/2009/04/citation-coloring-with-google-scholar.html
I'm
getting citation info out based on titles. A google scholar API would make this
the
scholar lookup component much cleaner and more reliable.
Thing I'm struggling with now is how to reliably grab all the titles from a
reference
list using regex ...
Original comment by tans...@gmail.com
on 21 Apr 2009 at 11:44
This would be a great feature. Please do add this asap.
Original comment by Rup.M...@gmail.com
on 27 Apr 2009 at 5:45
Found an example of a script that would benefit from a Google Scholar API:
http://www.plutosforge.com/blog/projects/ncbi-scholar
It adds number of google citations to references returned by PubMed - would
love to
see this available for all referencing systems.
Original comment by tans...@gmail.com
on 28 Apr 2009 at 1:31
Have an example of a system based on a Google Scholar API:
http://linklens.blogspot.com/2009/04/citation-parsing-regular-expression.html
Works via screen scraping at present - colorizes references by citation number
so
it's easy to see which are the key papers being referenced. Interface is web
based -
idea is that you copy reference list from PDF doc and paste into web interface
- hit
a button and returns the list colorized and linked to Google scholar ...
Original comment by tans...@gmail.com
on 29 Apr 2009 at 1:51
You have my vote either. And the suggestion for a quick fix is..
Please add "scholar" to the AJAX search like below:
http://ajax.googleapis.com/ajax/services/search/scholar
Original comment by pilho...@gmail.com
on 30 Apr 2009 at 4:13
+1 Would like to see an API to search scholar based on terms or art discussed
in
academic papers
Original comment by ZR.Supp...@gmail.com
on 30 Apr 2009 at 4:37
I think this API will bring alot info for education.
Original comment by allen...@gmail.com
on 4 May 2009 at 6:28
Yes, please! Or at least provide a way for us legitimate users to avoid
getting 302
errors because Scholar thinks we are bots.
Original comment by dke...@gmail.com
on 20 May 2009 at 1:31
Just a note - as well as adding your support in a comment, please click the star
button to receive updates on this thread - apparently Google places a lot of
stock in
the number of people "starring" an issue
Original comment by tans...@gmail.com
on 20 May 2009 at 6:06
many people are waiting for the google scholar api¡¡ i would be great¡¡
Original comment by pescobar...@gmail.com
on 21 May 2009 at 10:45
Another same request .....
google team plllllzzzzz listen to this :)
Original comment by sachdev...@gmail.com
on 27 May 2009 at 7:14
With such an API, individual researchers could:
- download citations in bibtex format for inclusion in their own paper's
citation lists.
- link to or embed google scholar results for their own publications on their
personal websites.
- provide links to papers which cited their own publications.
- compute h-indices and other measures of scientific impact.
If the papers listed have permanent URLs or other unique identifiers attached,
this could be of use for services where people
comment on papers, such as online journal clubs, possibly engaging authors.
This is more far-fetched, but if the API includes emails of authors, measures
of authoritativeness such as the h-index (even if
they can be rightfully criticized), could be the basis for increased trust of a
user logged onto a service using the same email as
in publications. Imagine knowledge repositories like wikipedia or
user-generated content aggregators like reddit or slashdot
giving more trust/karma to authenticated scientists: content quality could
improve dramatically. Pushing this a little more, it
would almost be possible to have decentralized peer-review systems based on
authenticated authors: let authenticated authors
endorse a paper, or endorse it conditioned on some requested additions to the
paper.
Original comment by kolia.sa...@gmail.com
on 29 May 2009 at 12:22
[deleted comment]
It has not technical obstacles prevent this from being done.
Google Team please provide us with the API.
Original comment by szyul...@gmail.com
on 31 May 2009 at 12:42
Google likely cannot provide a Google Scholar API.
The way Google obtains the "Cited by" links in Scholar is through it's free
access to
"deep web" accounts at all major online journal publishers which allow it to
download, index and analyze the full text PDFs.
Google's contracts with these publishers likely prohibit Google from making an
API
available. I believe this is also why they do not show the opposite of "Cited
by" and
list all the other papers a paper cites.
Original comment by reflect...@gmail.com
on 26 Jun 2009 at 3:17
Basically what I want to do is create a more "multi-dimensional" result for a
given
search. I see that 122 papers have cited a particular hit, and that's
interesting,
but I have to go look at all of those papers manually before I learn that two
thirds
of them cite the paper for reasons I'm not interested in (as an example, they
use a
method developed in the paper, whereas I'm interested in papers that extend the
actual research question). Ideally, I'd like to be able to get all of the
abstracts,
and then give them to a simple NLP engine that will automatically tell me which
ones
are moving in the direction I want (but of course, there's no simple way to do
that
with the current interface).
Someone else mentioned that citations could be used as links in a graph
representation of the reference network. I'd like to create an app that
collects the
connections (perhaps filtered as above) as something like "pubmed_id cites
pubmed_id", which could then be directly displayed in a graph visualization
tool like
cytoscape (http://www.cytoscape.org). I could then pull out keywords, authors,
or
other attributes, and load them directly into cytoscape so the graph could be
colored
or searched by attribute. The abstracts could also be linked directly from the
cytoscape interface.
This seems like it would be an incredibly powerful way to visually explore a
body of
literature on a particular topic, and I'm not aware of anything else that gets
to
this level.
Original comment by kalle...@gmail.com
on 4 Jul 2009 at 4:31
As a librarian interested in citations API, I vote for this feature
Original comment by bonariab...@gmail.com
on 6 Aug 2009 at 7:43
I vote for this..
I'm using googles api for a software develop of retrieving papers and cites
from a
specific paper, using inteligent agents.
I't woul be a social and distribuited tool for finding and retrievin only
scholara an
education papers. Of course following, free for all.
Please don't last too much...
Many people are waiting for this great service!!!
Thanks in advance!!!!
Original comment by omar.chi...@gmail.com
on 7 Sep 2009 at 1:01
I could use this for my work in analyzing citation networks...
Original comment by conrad...@gmail.com
on 12 Sep 2009 at 10:09
+1 needed for citation networks work.
Original comment by ques...@gmail.com
on 19 Sep 2009 at 10:56
This might be very useful for academic collaboration via Wave - writing an
project as a wave, submitting it to the
teacher who can follow embedded citations et cetera (and then comment).
Original comment by raoul.lu...@gmail.com
on 1 Oct 2009 at 12:53
+1 for research purposes (ideally with public specs on what is included in the
citation count!)
Original comment by dario.ta...@gmail.com
on 16 Oct 2009 at 11:44
Wow, this feature would be great! +1
Original comment by ayt...@gmail.com
on 16 Oct 2009 at 12:41
Aye. +1
Original comment by christian.muise
on 16 Oct 2009 at 1:42
+++
Original comment by a.kalitz...@gmail.com
on 16 Oct 2009 at 1:45
This would be a great feature. ++
Original comment by pat.nich...@gmail.com
on 16 Oct 2009 at 1:53
Please do!
Original comment by martharo...@gmail.com
on 16 Oct 2009 at 2:40
Yes please!
Original comment by geri.odo...@gmail.com
on 16 Oct 2009 at 3:44
One more vote from me!
Original comment by alfr...@gmail.com
on 16 Oct 2009 at 3:47
As a PhD student, I find myself performing lots of manual searches on Google
Scholar. I
started building a screen scraper to automate the process but then decided not
to
because any UI change could break it. An API would be great!
Also, we don't need anything fancy. I would guess someone could whip an
adequate
solution together in a few days or weeks.
Or you could make it some kind of a competition and let us solve it.
Original comment by steve.pi...@gmail.com
on 16 Oct 2009 at 4:08
ditto
Original comment by Ed.Corcoran
on 16 Oct 2009 at 5:55
yep
Original comment by paulo.ca...@gmail.com
on 17 Oct 2009 at 5:57
Please do!!
Original comment by Suhail.M...@gmail.com
on 18 Oct 2009 at 7:19
Yes please!
Original comment by girds...@gmail.com
on 18 Oct 2009 at 8:02
That would be very useful.
Original comment by michal.p...@gmail.com
on 19 Oct 2009 at 12:30
Original issue reported on code.google.com by
anders.n...@gmail.com
on 16 Sep 2008 at 8:15