Posted by: Susan | April 28, 2010

A Solution to Subject Access of the Library OPAC


Responses

  1. [...] This post was mentioned on Twitter by TheSource Newsletter, Susan Roby Berdinka. Susan Roby Berdinka said: http://susanrb.wordpress.com/2010/04/28/subject-access-the-opac Subject Access of the #Library #OPAC #library30 #semantic_web #cataloging [...]

  2. Susan, I liked this post very much.

    I haven’t yet King and Reinhold, but it sounds like what’s proposed is to add a layer between authority records and the “natural language” that translates the controlled vocabulary of subject headings to something that is semantically receptive?

    • There are two layers that I believe need to be added between the authority records and the patron’s natural language. One is to program a user interface to interpret the patron’s natural language. The other is an ontology.

      I hope you can obtain a copy of the book. What King and Reinhold propose is creating an ontology layer between the authority records and the user interface. An ontology defines classes, sets, attributes, and relations of the domain – in this case the LC Subject Headings. Also, it includes synonyms of the members of the domain. Given the size of the LC Subject Headings, this is certainly not a trivial project.

      The user interface would need to be programmed more intelligently in order to do more than perform the brute queries that are typical of an OPAC. There has been a lot of research on natural language processing in the computer science field using a number of programming languages.

      Thanks for your comment!

  3. [...] } As I stated in my article A Solution to Subject Access of the Library OPAC, it is the responsibility of those of us organizing information to allow the searcher to find his [...]

  4. [...] to make the OPAC more user friendly, as I have discussed in my last two articles on findability and subject access: Basic Flow for OPAC [...]


Categories

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: