Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

November 19, 2014 NISO Virtual Conference: Can't We All Work Together?: Interoperability & Systems Integration

1,315 views

Published on

Distributed Person Data
Violeta Ilik, Digital Innovations Librarian, Northwestern University Feinberg School of Medicine, Galter Health Sciences Library, Chicago

Published in: Education
  • Be the first to comment

November 19, 2014 NISO Virtual Conference: Can't We All Work Together?: Interoperability & Systems Integration

  1. 1. + Distributed Person Data NISO Virtual Conference: Can't we all Work Together? Interoperability & Systems Integration Violeta Ilik Digital Innovations Librarian Galter Health Sciences Library Northwestern University Clinical and Translational Sciences Institute Chicago, IL November 19, 2014
  2. 2. + Uniquely identifying researchers Compiling scholarly output Measuring the scholarly output Finding collaborators Disseminating research Tracking funded research Researchers, institutions, publishers, libraries, funding organizations, identity management systems (one example: researcher profile system)
  3. 3. + The Problem Each system creates identifiers for each author and co-author Need to link and disambiguate researchers across institutions and systems Need to preserve institutional authority over scholarly contributions Not all researchers have ORCiD or other unique identifier Systems don’t talk to each other
  4. 4. +
  5. 5. + Challenge Teun Hocks
  6. 6. + Challenges Multiple names/transliteration Change of names Pseudonyms - privacy issues!!! Multiple profiles, identifiers – not linked Data standards not interoperable
  7. 7. + To be or not to be proactive Test me!
  8. 8. + VIVO – researcher profile system Questions: Persistent URIs? Are they location independent? Are they free to use? RDF support? Community driven? Curated resource? Are they reliable? Unrestricted scope?
  9. 9. + How do we track researcher’s various affiliations over time in VIVO? Former Institution VIVO URI http://vivo.institutionA.edu/ individual/n64866 Future Institution VIVO URI http://vivo.institutionC.edu/ individual/n54678 Current Institution VIVO URI http://vivo.institutionB.edu/ individual/n435876 sameAs link? seeAlso link? sameAs link? seeAlso link? OR OR Role: graduate student Role: postdoctoral scholar Role: tenured faculty VIVO Registry URI http://vivo.vivoweb.org/individual/n654321
  10. 10. + Distributed person data Each institution publishes authoritative data about researcher's activities during a given time period. URIs for VIVOs that commit to maintaining the historical data should be registered for ongoing discoverability in the VIVO Registry Each VIVO records ORCID iD to aid in sameAs linking. “The Case For Stable VIVO URIs” Melissa Haendel, Brian Lowe, and Violeta Ilik - VIVO/SciTS Conference, Austin, TX, August 8, 2014
  11. 11. + Institution A Institution B ID:123 http://vivo.institutionA.edu/ individual/n64866 http://vivo.institutionB.edu/ individual/n88764 http://vivo.institutionA.edu/ individual/n45891 Mary Jane Co-authorship Joe Shmo Joe Shmo Creating stable VIVO URIs “The Case For Stable VIVO URIs” Melissa Haendel, Brian Lowe, and Violeta Ilik - VIVO/SciTS Conference, Austin, TX, August 8, 2014 http://vivo.vivoweb.org/individual/n654321
  12. 12. + Program for Cooperative Cataloging (PCC) Task Group on the creation and Function of Name Authorities in a Non-MARC Environment Goals: Relate external named entity identifiers and information to library authority data and bibliographic data Structure library authority data for use in linked data environment and library systems
  13. 13. + OCLC Research - Registering Researchers in Authority Files Task Group “Rather than waiting until sufficient information is available to create a national authority heading, librarians could generate a stub with an ID that others could augment or match and merge with other metadata.”
  14. 14. + Think about it: possibility of using VIVO Registry For Corson-Rikert, Jonathan use instead of the local VIVO Cornell one: http://vivo.cornell.edu/individual/individual22972 the one from VIVO Registry: http://vivo.vivoweb.org/individual/n5444
  15. 15. + Goal Registering VIVO URIs with OCLC PURL server? Registration of VIVO URIs from VIVO Registry in VIAF Making vivoweb.org/ontology URIs persistent “The Case For Stable VIVO URIs” Melissa Haendel, Brian Lowe, and Violeta Ilik - VIVO/SciTS Conference, Austin, TX, August 8, 2014
  16. 16. + Conclusion To support maximal data integration across sites and platforms, we need to support: Persistent VIVO person URIs Management of seeAlso assertions for person instances across various VIVO platforms Management of sameAs assertions for person instances across different data sources Resolving to VIVO Registry Leading to interoperability!
  17. 17. + Linking across data sources Example: VIVO Registry URI sameAs link? Why not?!
  18. 18. Thank you

×
https://www.slideshare.net/BaltimoreNISO/ilik-vivo
www.slideshare.net
crawl=CC-MAIN-2018-51
166009
application/http; msgtype=response
sha1:B6KXLLDUBWZMM7OVPEAUKMLPCHFGTM3D
<urn:uuid:d97d67eb-724a-4cfa-bd8e-5ca117187337>
2018-12-13T00:48:18Z
108.174.10.19
text/html
sha1:OSOS5AY4LN7C4LIXYI7IXQORLKLQS7T4
<urn:uuid:44f0f10d-8db8-43eb-b960-409cdd0fb2b2>
https://www.slideshare.net/BaltimoreNISO/ilik-vivo
response
<urn:uuid:42e8f67c-04ca-45a3-8a60-ea87a7354d49>
isPartOf: CC-MAIN-2018-51
publisher: Common Crawl
description: Wide crawl of the web for December 2018
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-164-234-169.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/