1 / 40

Concept Evolution (Subject Ontogeny) in the NLM Classification Scheme: a Case Study

Concept Evolution (Subject Ontogeny) in the NLM Classification Scheme: a Case Study. Outline. Schemes Concepts in Schemes Concept Evolution in Schemes Modified Record for Concepts Conclusion. Schemes. Schemes. Classification schemes, controlled vocabularies (indexing languages),

deiter
Télécharger la présentation

Concept Evolution (Subject Ontogeny) in the NLM Classification Scheme: a Case Study

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. Concept Evolution (Subject Ontogeny) in the NLM Classification Scheme: a Case Study

  2. Outline • Schemes • Concepts in Schemes • Concept Evolution in Schemes • Modified Record for Concepts • Conclusion

  3. Schemes

  4. Schemes • Classification schemes, • controlled vocabularies (indexing languages), • ontologies and taxonomies (newer versions of representations not always used as indexing languages, tho’ sharing similar structures and appearance).

  5. Schemes • Dublin Core calls these encoding schemes [4]

  6. Schemes • NLM Classification [1] • UMLS (Unified Medical Language System) [2] • Galen Common Reference Model [3]

  7. Concepts in Schemes

  8. Concepts in Schemes • Schemes are made up of concepts - identified by terms and relationships between terms. • The structure of classification schemes allows the user to identify the concept by both terminological access (via index or linked subject headings), or through relationships between concepts.

  9. Concept Evolution in Schemes (Subject Ontogeny)

  10. Concept Evolution in Schemes • Schemes change - they go through revisions, new editions, etc. • Concepts change because their relationships change - as do the terms used to identify these concepts.

  11. Concept Evolution in Schemes • I have metaphorically called this subject ontogeny • Based on a biological term for the development of an organism during its lifetime • Not a great metaphor

  12. Concept Evolution in Schemes • Evolution (cancellation here) is deployed in the NLM in order to aid collocation. • However, the change splits the materials.

  13. Concept Evolution in Schemes • As more of our materials are born digital and indexed using digital schemes, we can collocate through various editions - through the evolution of schemes. • Further, as more of our users interact with our collections through interfaces, the move value we can add the better we will serve them.

  14. Concept Evolution in Schemes • If we build structures to aid us in this, we can actually maintain and enhance the purpose of these schemes - collocation. • We can also enhance displays allowing for a better combination of searching and browsing.

  15. Concept Evolution in Schemes • What then is required to track these changes? • We need a concept record that tracks these changes.

  16. Concept Evolution in Schemes • This kind of record can be modified to account for change that is both machine and human readable.

  17. Modified Record for Concepts

  18. Modified Record for Concepts • Need to add various aspects of change to the record. • Current records (like above) capture history but this is not actionable by machines from the record. It is also written in a cryptic professional notation.

  19. Modified Record for Concepts • We can add fields then that are actionable if we’re specific about what we need. • In the case of the NLM we can say what was added and what was canceled, making it actionable in the record.

  20. Modified Record for Concepts • Class Number • Subject in English • Date Created • Previous Number • Broader Number • Narrower Number • Coordinate Number

  21. Conclusion

  22. Conclusion • We can make these fields manifest in our catalogues by exploiting current data structures. • MARC Classification Format offers all of these fields • Currently these are all optional

  23. Conclusion • These are the Tracing fields • Special Relationship - Previous class number, New class number • Hierarchical Relationship - Broader and Narrower topics

  24. Conclusion • These structures could then be used to enhance search and display in catalogues. • And initiatives like this are developing - exploiting MARC data structures for users - not just professionals.

  25. Conclusion • With this kind of record used - we can build better displays and better systems, • Enhancing the user experience • Aiding browsing and navigation through vast amount of information.

  26. References 1 http://wwwcf.nlm.nih.gov/class/ 2 http://www.nlm.nih.gov/research/umls/ 3 http://www.opengalen.org/open/crm/ 4 http://www.dublincore.org/documents/usageguide/glossary.shtml#E 5 http://www.nlm.nih.gov/mesh/MBrowser.html

  27. Thank you jtennis@interchange.ubc.ca www.slais.ubc.ca

More Related