1 / 16

The HILT Pilot Terminologies Server

The HILT Pilot Terminologies Server. Dennis Nicholson: Centre for Digital Library Research, Strathclyde University. Overview. Introduction Scope Design Current state of play Other Points to Note Underlying Logic. Introduction. Terminologies server for JISC I.E.: Pilot server

rylee-hubbard
Download Presentation

The HILT Pilot Terminologies Server

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. The HILT Pilot Terminologies Server Dennis Nicholson: Centre for Digital Library Research, Strathclyde University

  2. Overview • Introduction • Scope • Design • Current state of play • Other Points to Note • Underlying Logic

  3. Introduction • Terminologies server for JISC I.E.: • Pilot server • Explore issues • Design requirements for full server • Focus on collection level requirements • Costs and benefits • Based on mapping between schemes (HILT Phase community consensus)

  4. Scope • Collection level only, so: • Accept and disambiguate user query; Identify appropriate collections [Y] • Provide information on subject schemes used [Y] • Guidance on how best to search collections; sample retrieval [Y] • Facilities to improve legacy metadata interoperability problems[N]

  5. Design • Wordmap; three elements: • Database (Oracle) of terminology mappings • User front end that interacts with database according to staff specifications and user input and feedback • Drag and drop, multi-user interface to support sophisticated staff interaction with database for creation and maintenance of maps, inter-service co-ordination and training

  6. Design • Comprehensive: • DDC spine; captions from schedules; relative index; standard subdivisions • LCSH to DDC mapping (maybe) • Selective; illustrative: • UNESCO to DDC; User terms set’; MeSH, AAT?

  7. Design • User enters subject term • Term matched to terminology set and mapped to DDC • Options and disambiguation • DDC number truncated and mapped to collections database to identify appropriate collections • Information on scheme used; advice; sample retrieval

  8. Design • Pilot acts as a portal; uses own collections database (SCONE) • Specification: m2m with other portals and IESR • Collections database (IESR): • Classified by DDC • Sub-collections; collection strength • Subject scheme used at item level

  9. Current state of play • (Simple) Pilot well advanced • User and staff workshop planned in June to refine requirement • Further development and issues research planned after workshop • Cost benefit analysis planned – using INSIGHT methodology • Completion: end September

  10. Other Points to Note • Simple pilot to explore issues and specify more complex operational collection level service: • User need several terms? (combined) • Multiple disambiguation choices? • Next phase would build service and explore item level issues • Many ‘user level’ issues also: • Profile, task, skill level at subject query expression

  11. Underlying Logic • Perfect retrieval if fully fit for purpose standard scheme always fully understood and correctly and consistently applied by both staff and users and legacy metadata problems vanish overnight • An unlikely scenario at best but shows aim of terminologies server must be to: • Improve accurate and consistent description by staff • Improve accurate and informed searching by users • Provide mechanisms to facilitate improved retrieval from legacy metadata • Monitor, learn from user terminology sets

  12. Underlying Logic • Improve accurate and consistent description: • UK versions of standard terms on central server • Scheme extensions on central server – standardized across services • Sample retrieval from collections showing staff the kind of resources that should be described in particular ways using a particular scheme • Online training for staff

  13. Underlying Logic • Improve accurate and informed searching by users: • minimize staff changes to standard schemes • make changes, extensions known to users • user training • System facilities that allow users to see and explore the scheme used • Optimise the extent to which the terminologies server can ‘recognize’ terms used by users and map them intelligently to the scheme used by a collection

  14. Underlying Logic • Provide mechanisms to facilitate improved retrieval from legacy metadata: • Central repository of frequently used UK amendments and extensions • Service specific variations and advice? • Automated help to facilitate description upgrades?

  15. Underlying Logic • Monitor, learn from user terminology sets: • Central server can improve retrieval performance by facilitating speedy mapping of user terminology sets to standard terminologies

  16. Further Information • Website: http://hilt.cdlr.strath.ac.uk/ • e-mail: • d.m.nicholson@strath.ac.uk • Ali.shiri@strath.ac.uk • emma.mcculloch@strath.ac.uk • LIS-HILT-ORG@jiscmail.ac.uk

More Related