nicnames: an overview

28
nicnames: an overview names roundtable, 18 june 2010 rebecca parker research services librarian swinburne university of technology subject matter expert nicnames project

Upload: hide

Post on 17-Jan-2016

24 views

Category:

Documents


3 download

DESCRIPTION

nicnames: an overview. names roundtable, 18 june 2010 rebecca parker research services librarian swinburne university of technology subject matter expert nicnames project. NicNames: the project. Collaborative project: Swinburne University of Newcastle - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: nicnames: an overview

nicnames: an overviewnames roundtable, 18 june 2010

rebecca parkerresearch services librarianswinburne university of technology

subject matter expertnicnames project

Page 2: nicnames: an overview

NicNames: the project

Collaborative project:> Swinburne> University of Newcastle> University of New South Wales

Funded by the ARROW Project (arrow.edu.au):

> Focused on (but not limited to) repositories

Swinburne University of Technology, Melbourne, Australia

Page 3: nicnames: an overview

Swinburne University of Technology, Melbourne, Australia

Names: the problem

Author name = 20% of academiclibrary catalogue searches

Neither consistent nor unique: problem>all published works by a single author>specific papers by known authors

How about institutional repositories?

Page 4: nicnames: an overview

Swinburne University of Technology, Melbourne, Australia

Names: the status quoBrowse menus for 3 Australian institutional repositories

Page 5: nicnames: an overview

Swinburne University of Technology, Melbourne, Australia

NicNames: the process

Phase 1: Analysis> Data analysis> Repository manager survey> User research project

Phase 2: Development

Page 6: nicnames: an overview

Swinburne University of Technology, Melbourne, Australia

No one cares what you do untilyou get it wrong

> Swinburne examples:1. Standard version (controlled)2. Preferred version3. Published version

NicNames: the discoveries (1)

Page 7: nicnames: an overview

Swinburne University of Technology, Melbourne, Australia

NicNames: the discoveries (2)Name variants can have meaning> Journal house style> Citation formats> Transliteration, transcription, translation> Patronymics and other inherited names> Changes in personal circumstances> Desired distance from previous publications> Different identities for different contexts

Page 8: nicnames: an overview

Swinburne University of Technology, Melbourne, Australia

Authority control doesn’t work for IRs> ‘Missing’ information> ‘Different’ information

NicNames: the discoveries (3)

Page 9: nicnames: an overview

Swinburne University of Technology, Melbourne, Australia

Publications actually tell us a lot about researchers

> Field of research (FOR) classifications> Frequent source titles, conferences> Frequent publishers> Publication type

> Affiliation> Coauthorship

NicNames: the discoveries (4)

ARDC:Projects, grants,research data

Page 10: nicnames: an overview

An obvious solution?

Libraries

Web

University

Research

(A) unique identifier(s)> People Australia party identifier> LCCN; ISNI; ISADN

> Scopus ID> Thomson ResearcherID> GAMS ID

> OpenID> Staff ID or email address

Or one to rule them all … ?

Page 11: nicnames: an overview

Swinburne University of Technology, Melbourne, Australia

NicNames: the decisions

A local approach is appropriate:> Local knowledge> Local systems: repositories, HR

A national approach can be coordinated

Artificial intelligence can help:> Multiple sources of data are the key

Page 12: nicnames: an overview

Swinburne University of Technology, Melbourne, Australia

NicNames: the software> Assigns unique IDs> Exports to XML, OAI-PMH (new)> Stores known information about researchers> Makes use of data universities already have> Simple Web application with API (PHP)> Can control which data is exported

https://launchpad.net/nicnames

Page 13: nicnames: an overview

ARROW NicNames Project

Page 14: nicnames: an overview

ARROW NicNames Project

Page 15: nicnames: an overview

ARROW NicNames Project

Page 16: nicnames: an overview

ARROW NicNames Project

Page 17: nicnames: an overview

ARROW NicNames Project

• Chris Smith Chris Smith

Page 18: nicnames: an overview

ARROW NicNames Project

• Ralph = Tim (sometimes)

Page 19: nicnames: an overview

ARROW NicNames Project

Page 20: nicnames: an overview

Questions?

Page 21: nicnames: an overview

Questions?

Page 22: nicnames: an overview

Questions?

Page 23: nicnames: an overview

ARROW NicNames Project

Page 24: nicnames: an overview

NicNames and privacy

Only public data should be used

A ‘no surprises’ approach

Configurable export for data elements

Swinburne University of Technology, Melbourne, Australia

Page 25: nicnames: an overview

NicNames and ARDCPIP

Now OAI-PMH compliant

Considering future EAC support

Can store party IDs where these exist

Swinburne University of Technology, Melbourne, Australia

Page 26: nicnames: an overview

Swinburne University of Technology, Melbourne, Australia

Questions?

Page 27: nicnames: an overview

Swinburne University of Technology, Melbourne, Australia

Acknowledgements

ARROW Project for funding

Thomas Rutter for software screencapture

Dr Peter Sefton, ADFI, for help, adviceand support throughout the Project

Page 28: nicnames: an overview

For more information on this presentation, please contact:

Rebecca ParkerResearch Services LibrarianSwinburne University of Technology

[email protected]

or visit http://nicnamesproject.blogspot.com/

For software questions, please contact Thomas Rutter, Swinburne [email protected]