1 / 28

NicNames Project: Enhancing Author Identification in Academic Repositories

Explore the NicNames project aiming to address author identification challenges in academic repositories by analyzing data, discovering key findings, and proposing software solutions. Supported by ARROW Project, the initiative focuses on enhancing search accuracy and consistency in academic libraries.

hide
Télécharger la présentation

NicNames Project: Enhancing Author Identification in Academic Repositories

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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

  3. 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? Swinburne University of Technology, Melbourne, Australia

  4. Names: the status quo Browse menus for 3 Australian institutional repositories Swinburne University of Technology, Melbourne, Australia

  5. NicNames: the process • Phase 1: Analysis • Data analysis • Repository manager survey • User research project • Phase 2: Development Swinburne University of Technology, Melbourne, Australia

  6. NicNames: the discoveries(1) • No one cares what you do untilyou get it wrong • Swinburne examples: • 1. Standard version (controlled) • 2. Preferred version • 3. Published version Swinburne University of Technology, Melbourne, Australia

  7. 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 Swinburne University of Technology, Melbourne, Australia

  8. NicNames: the discoveries(3) • Authority control doesn’t work for IRs • ‘Missing’ information • ‘Different’ information Swinburne University of Technology, Melbourne, Australia

  9. NicNames: the discoveries(4) • Publications actually tell us a lot about researchers • Field of research (FOR) classifications • Frequent source titles, conferences • Frequent publishers • Publication type • Affiliation • Coauthorship ARDC:Projects, grants, research data Swinburne University of Technology, Melbourne, Australia

  10. An obvious solution? • (A) unique identifier(s) • People Australia party identifier • LCCN; ISNI; ISADN • Scopus ID • Thomson ResearcherID • GAMS ID • OpenID • Staff ID or email address Libraries Research Web University Or one to rule them all … ?

  11. 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 Swinburne University of Technology, Melbourne, Australia

  12. 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 Swinburne University of Technology, Melbourne, Australia

  13. ARROW NicNames Project

  14. ARROW NicNames Project

  15. ARROW NicNames Project

  16. ARROW NicNames Project

  17. ARROW NicNames Project • Chris Smith ¹ Chris Smith

  18. ARROW NicNames Project • Ralph = Tim (sometimes)

  19. ARROW NicNames Project

  20. Questions?

  21. Questions?

  22. Questions?

  23. ARROW NicNames Project

  24. NicNames and privacy • Only public data should be used • A ‘no surprises’ approach • Configurable export for data elements Swinburne University of Technology, Melbourne, Australia

  25. NicNames and ARDCPIP • Now OAI-PMH compliant • Considering future EAC support • Can store party IDs where these exist Swinburne University of Technology, Melbourne, Australia

  26. Questions? Swinburne University of Technology, Melbourne, Australia

  27. Acknowledgements • ARROW Project for funding • Thomas Rutter for software screencapture • Dr Peter Sefton, ADFI, for help, adviceand support throughout the Project Swinburne University of Technology, Melbourne, Australia

  28. For more information on this presentation, please contact: Rebecca Parker Research Services Librarian Swinburne University of Technology rparker@swin.edu.au or visit http://nicnamesproject.blogspot.com/ For software questions, please contact Thomas Rutter, Swinburne Library trutter@swin.edu.au

More Related