Recommended
More Related Content
What's hot
What's hot (20)
Similar to Peer Council 2016 Keynote Address with John Chapman
Similar to Peer Council 2016 Keynote Address with John Chapman (20)
Recently uploaded
Recently uploaded (20)
Peer Council 2016 Keynote Address with John Chapman
- 1. WiLS Peer Council 2016 Keynote Address John Chapman Senior Product Manager, Metadata Services OCLC, Inc.
- 3. Users want to search using names.
- 4. Users want to know more about people.
- 5. Users want to know more about people.
- 6. People are bad at giving unique names.
- 7. People are bad at giving unique names.
- 8. Find me everything by John Chapman Users want recall and precision.
- 11. Find me everything by John Chapman Not that John Chapman! Users want recall and precision.
- 12. Authorized name forms are often ignored.
- 13. Authority records aren’t good for discovery.
- 14. Authority records are hard to create.
- 15. Authority records are hard to create. OR, “Authority record creation programs take effort to set up and sustain.”
- 16. CHALLENGES
- 17. • Scope – high % are monograph authors • Model – flat/unclear (pseudonyms, titles, names, etc etc) • Mandate – only when and to the extent a name form needs to be unique Intellectual scope, model, mandate
- 18. • Applicability to special collections / non-published materials is weak • Tied with historical decisions to not catalog articles Authority control scope – material type
- 19. • Models differ • Quality control differs • Duplication • Different “clumping” • Name forms Authority control and scale
- 21. WAYS FORWARD
- 22. • Linkification vs entification Definitions
- 23. 600 1 7 ‡a Vollmann, William T. ‡2 fast ‡0 (OCoLC)fst0018706 Becomes… 600 1 7 ‡a Vollmann, William T. ‡2 fast ‡0 http://id.worldcat.org/fast/187068 “Linkification”
- 24. Vollmann, William T. Becomes: <http://worldcat.org/entity/person/id/2639915820> Entity Resolution
- 25. <http://www.worldcat.org/oclc/25509331> # An Afghanistan picture show, or, How I saved the world a schema:CreativeWork, schema:Book ; schema:creator <http://worldcat.org/entity/person/id/2639915820> ; # William T. Vollmann library:oclcnum "25509331" ; library:placeOfPublication <http://id.loc.gov/vocabulary/countries/nyu> ; library:placeOfPublication <http://dbpedia.org/resource/New_York_City> ; # New York schema:exampleOfWork <http://worldcat.org/entity/work/id/200636202> ; # Afghanistan picture show schema:genre "History"@en ; schema:genre "Personal narratives"@en ; “Entification”
- 26. • Converting data is cheaper and easier • Garbage in, garbage out • Consistency is good for sharing • Some work is “computationally expensive” Limits, investments, and tradeoff
- 27. CASE STUDY
- 28. WorldCat Person Entity Lookup Pilot • How does it work? – Users can find and identify persons with common IDs – Users can enter text (for example, a personal name) – Information returned includes other IDs, birth/death dates, roles, etc. • Pilot participants – Biblioteka Narodowa (Poland), Cornell, Deutsche Nationalbibliothek (Germany), Harvard, LC, NLM, Stanford, UC Davis, Pepperdine, swissbib, Drexel
- 29. Aggregating information about people
- 30. Aggregating information about people
- 31. Aggregating information about people
- 32. Aggregating information about people
- 33. Aggregating information about people
- 34. Lessons learned • Discovery potential
- 35. Lessons learned • Discovery potential • Potential for wider contributor base
- 36. Lessons learned • Discovery potential • Potential for wider contributor base • Need to include more non-authority data
- 40. Lessons learned • Discovery potential • Potential for wider contributor base • Need to include more non-authority data • One-by-one is good for resolution, but not for conversion
- 41. Lessons learned • Discovery potential • Potential for wider contributor base • Need to include more non-authority data • One-by-one is good for resolution, but not for conversion • Linking is fun
- 42. CONCLUSIONS
- 43. What should libraries do…
- 44. • Improve recall by controlling as many names as possible • Improve precision by improving authorities • Participate in your friendly local NACO funnel • Add MARC records to WorldCat for special collections …to make discovery work better?
- 45. • Consider adding local identifiers as stopgap • Document and share local headings …to make metadata workflows better?
- 46. • Surface hidden collections by focusing on identifying personal names and organizations • Use WorldCat, ArchiveGrid, etc to find other institutions with similar collections (or authors?) … to expand the scope of description?
- 47. SM Thank you! John Chapman Senior Product Manager, Metadata Services chapmanj@oclc.org WiLS Peer Meeting: 8 June 2016
Editor's Notes
- Name forms are created only with enough detail to differentiate. Usually a year of birth is enough, but see the example here where even a month was not specific enough. Even with this much detail, a library will still have to deal with metadata that mentions “John Chapman” without any more info. At OCLC, we knew we could help libraries identify and pull together resources in a more comprehensive way – so we created Persons as a way to do this.
- Name forms are created only with enough detail to differentiate. Usually a year of birth is enough, but see the example here where even a month was not specific enough. Even with this much detail, a library will still have to deal with metadata that mentions “John Chapman” without any more info. At OCLC, we knew we could help libraries identify and pull together resources in a more comprehensive way – so we created Persons as a way to do this.
- Name forms are created only with enough detail to differentiate. Usually a year of birth is enough, but see the example here where even a month was not specific enough. Even with this much detail, a library will still have to deal with metadata that mentions “John Chapman” without any more info. At OCLC, we knew we could help libraries identify and pull together resources in a more comprehensive way – so we created Persons as a way to do this.
- First phase was ID-based, second phase allowed for text-based searching
- This is a view of a prototype for displaying Person Entities. Note that we also pull in information from other vocabularies to build this view.
- We use a numebr of sources to show additional information about the person. This is crucial for disambiguation between similar names (the “John Smith” problem)
- We capture alternate name forms, and these are indexed so users can get to the entity through a number of alphabets
- Also important are “same as” relationships, which allow users to disambiguate and to get more information. It’s also useful to pull together displays such as this one.
- In many cases we can even show family relationships.
- Libraries need to serve their communities, and in doing so, local / special materials are important.As we expand beyond traditional authority files, we open up new opportunities and challenges for managing names and other information about persons.
- Link goes out with a call to help add context.