Authors sharing same last name and initials

[GoogleCodeExporter]

What steps will reproduce the problem?
1. A number of authors have the same last name and initials
2.
3.

What is the expected output? What do you see instead?
There is no simple fix. However, if an interactive listing was provided, 
one could "select" the papers known to a particular author. 
This "corrected" list could then be submitted for re-computation of the 
score.

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by DrJRGue...@gmail.com on 14 Feb 2009 at 8:10

[GoogleCodeExporter]

As a suggestion, allowing searching by field would reduce this error. For 
example,
allow users to search for an author published by field (Business, Economics, 
Finance,
etc. or Physics, etc.)

Original comment by peterlan...@gmail.com on 3 Mar 2009 at 6:14

[GoogleCodeExporter]

Thanks for your reply. 
That would indeed fix most of the problems. Presently, Google Scholar Citation 
Counter does not support that feature. So hopefully your suggestion will be 
adopted. 
Surprisingly, there are still authors (more than you might guess) with the same 
surname AND initials working in the same field! That was the problem I was 
really 
having--that's why I suggested the "editable" list. 

Original comment by DrJRGue...@gmail.com on 5 Mar 2009 at 9:50

[GoogleCodeExporter]

For me, even searching by field would not fix this (limiting to institutional
affiliations would help).  The best solution (used by ISI's Web of Science) is 
to
allow a subset of the listed articles to be manually selected or unselected.

Original comment by Professo...@gmail.com on 28 Mar 2009 at 6:19

[GoogleCodeExporter]

I absolutely agree...this is a fatal issue that, if not resolved, basically 
renders
this tool utterly useless. ISI is much better in this respect, but still not 
perfect.
Is there a way to assign individual researchers a unique identification number 
that
can then be associated with their publications? Then all one needs to know is 
this
number, that would solve all these issues.

Original comment by jkenn...@gmail.com on 10 Apr 2009 at 3:47

[GoogleCodeExporter]

I think a simpler idea than convincing the academic community to adopting
identification numbers or to allow for areas of research (because there is no 
end to
the number of sub areas that people would have to invent to describe their 
work), is
this:  Allow first, the search to accept names to be entered with a first, 
possibly
second, initial.  If you put in "Surname Initial" now (with quotation marks), it
finds the correct number of citations, but cannot calculate the H-index.  That 
way
people with a unique surname and first initial combination are covered.  Then 
the
people who have a common combination should put their institute(s) in the 
'other'
box.  Or their area of research.  It does not look like Google Scholar searches 
for
more than author name, date, or publication, so this might be the best a Google 
based
search can muster...

Original comment by AMo...@gmail.com on 22 Apr 2009 at 11:13

[GoogleCodeExporter]

Hi folks, actually you can limit the search to only the universities/company 
where
the author has worked, at least somewhat.  In the "+Other" box, type all or 
part of
the company names, quoting multiple words as necessary, with "|" between the 
each
university/company.  For example:
Carnegie|Rensselaer|"Kent State"
requires one of those terms, which pretty much allows me to filter out all the 
people
with my name who have not been at Carnegie Mellon, Rensselaer, or Kent State.
Similarly, I can refine the name search by typing in:
"First Middle Last"|"First M. Last"|"FM Last", replacing with my own first, 
middle,
and last name.

However, what I can NOT do, as least so far as I can determine, is say do not 
include
papers with a phrase to filter out the one last person with my name, who is at a
particular university that I've never been associated with.

Original comment by walkerbo...@gmail.com on 26 Sep 2009 at 1:48

[GoogleCodeExporter]

I would also like to see this bug fixed.

Original comment by JamesEst...@gmail.com on 6 Jan 2010 at 3:38