2. ORCID前史
• The first Name Identifier Summit, Cambridge, MA 2009/11/9
– H. Ratner (Nature) & D. Kochalko (Thomson Reuters)
– American Institute of Physics, American Psychological Association, Association
for Computing Machinery, British Library, CrossRef, Elsevier, European
Molecular Biology Organization, Hindawi, INSPIRE (project of CERN, DESY,
Fermilab, SLAC), Massachusetts Institute of Technology Libraries, Nature
Publishing Group, Public Library of Science, ProQuest, SAGE Publications Inc.,
Springer, Thomson Reuters, University College London, University of
Manchester (JISC Names Project), University of Vienna, Wellcome Trust, and
Wiley-Blackwell.
– Declaration (2009/12/1): RESEARCH STAKEHOLDERS ANNOUNCE
COLLABORATION AMONG BROAD CROSS-SECTION OF COMMUNITY TO
RESOLVE NAME AMBIGUITY IN SCHOLARLY RESEARCH
• 当時の状況:すでに出版社等が自動著者名名寄せや研究者ページをシ
ステム化
– Distinct Author Identification System, Web of Science, Thomson Reuters
– ResearcherID, Thomson Reuters
– Scopus Author Identifier, Elsevier
– Contributor ID Project, CrossRef
• しかし、各社でやることや出版社だけでやることの限界を認識
– 論文は発行元で一元管理できるが、研究者はそもそも出版社をまたがる。ま
た、出版物だkでなく、所属(大学等)ともまたがる
3.
4. ORCID, Inc.発足
• David Kochalko(Thomson Reuters)とHoward
Ratner (Nature Publishing)が音頭をとって提唱
(2009/12/1)
• ORCIDの準備会合(2009-2010前半)。Business
Working GroupとTechnical Working Group
• 参加者会合(2010/4/30 Boston)
• (2ヶ月に一度程度のBWGミーティング/理事会)
• ORCID, Inc.(アメリカ、デラウエア州のNPO)の発足
(2010.8)。理事メンバーの確定
• 運営メンバー確定
• 参加者会合(2010/12/8 London)
9. Mission Statement in early ORCID
• ORCID aims to solve the author/contributor name
ambiguity problem in scholarly communications
by creating a central registry of unique identifiers
for individual researchers and an open and
transparent linking mechanism between ORCID
and other current author ID schemes. These
identifiers, and the relationships among them,
can be linked to the researcher's output to
enhance the scientific discovery process and to
improve the efficiency of research funding and
collaboration within the research community.
11. 現在のMission Statement
Collect & Connect
“enter once, re-use often”
• Clarify implementation goals and
expectations across sectors:
• Standardize and improve the
user experience
• Improve understanding of trust
in connections between ORCID
and other identifiers:
• Increase the efficiency and
quality of integrations: Help
achieve the ORCID vision
through a community approach: