HILT: Past, present and future - PowerPoint PPT Presentation

1 / 24
About This Presentation
Title:

HILT: Past, present and future

Description:

Ongoing Dissemination; website upgrade. Requirements Document (still a work in progress) ... http://hiltm2m.cdlr.strath.ac.uk/hiltm2m/hiltsoapclient.php ... – PowerPoint PPT presentation

Number of Views:41
Avg rating:3.0/5.0
Slides: 25
Provided by: CIS471
Category:
Tags: hilt | future | past | php | present | upgrade

less

Transcript and Presenter's Notes

Title: HILT: Past, present and future


1
HILT Past, present and future
  • HILT Steering Group, October, 2006

2
HILT Past, present and future
  • Brief background notes
  • Phase III to date
  • Functions and use cases
  • Initial thoughts on a possible
  • baseline service

3
HILT Brief background notes
4
HILT Background and Overview
  • Funded JISC Support OCLC Collaborative
  • Aim provide subject interoperability in a
    multi-
  • scheme environment via inter-scheme mapping
  • Ideally by identifying a generic approach, able
    to be
  • built up through distributed collaborative
    action
  • Originally intellectual mapping, but now see
    how
  • model can include range of interoperability
    services
  • Phase I, II, M2M FS Now Phase III (main focus)

5
HILT Phase III Nov 05 Jan 07
  • Aim an M2M pilot that
  • Offers terminology services via SRW but is open
    to later extension to ( Z39.50 SRU)
  • Uses SKOS-Core as the mark-up for sending out
    terminology sets and classification data but
    open to later extension to other formats (MARC
    Zthes)
  • Is open to the possibility of a distributed
    approach to building a full service up via wide
    collaboration
  • Extends the user-accessible (non-M2M) Phase II
    pilot beyond inter-scheme mapping

6
HILT Phase III to date
7
(1) Future requirements (2)
Pre-refinement evaluation (3) Post-refinement
evaluation
8
Outputs to date
  • Project Plan Consortium Agreement
  • Various required reports to JISC or of meetings
  • Ongoing Dissemination website upgrade
  • Requirements Document (still a work in progress)
  • SKOS preparatory work
  • Mapping work Initial mapping types evaluation
  • Outline plan for a future baseline service
  • Working (if unfinished) M2M pilot based on SRW
  • server and clients, SOAP, SKOS wrapped KOS

9
(No Transcript)
10
(No Transcript)
11
(No Transcript)
12
Remaining work
  • Complete pilot SRW clients, SRW server,
  • SOAP server and functions, mappings, database
  • Evaluation of functioning pilot
  • Refinement based on results
  • Final evaluation
  • Complete requirements document, including
  • future requirements
  • Final Report Ongoing Dissemination Website
  • Bid for future baseline service (possibly soon)

13
HILT Functions and use cases
14
The Phase III pilot in outline
  • GoGeo Based Service-specific SRW client
  • HILT Client Phase II plus additional facilities
  • A baseline SRW open source client that includes
  • the DDC collections-finding code (HILT SRW)
  • More schemes DDC, LCSH, IPSV, AAT, GCMD
  • HASSET, MeSH, NMR, JACS, UNESCO (SKOS)
  • Additional but still illustrative - mappings
  • Detailed data on terms in schemes BT, NT,RT,
  • synonyms, scope note etc.
  • Functionality Support M2M FS Use Cases plus

15
Six Functions UC1 Emulate Phase II
  • Get_DDC_records
  • Returns DDC captions and numbers related to an
    input term list for user to choose best fit
    caption/no.
  • Get_collections
  • Returns collections classified under a specified
    DDC number or its stem, including subject scheme
    used
  • Get_non_DDC_records
  • Returns mappings to other schemes from a
    specified (untruncated) DDC number

16
UC1 (1 step) UC2/3 (2 functions)
  • Get_explain
  • Get_all_records
  • Combines the functions of get_DDC_records and
    get_non_DDC_records seen above
  • UC1 in 1 step
  • Use cases 2/3 Provide enriched set of search
  • terms so users can use (selectively or
    otherwise) to
  • improve searches of local service database
  • includes term expansion, singular/plural
    mappings,
  • spelling/typos correction (Google did you
    mean?)
  • Get_all_records or

17
UC2/3 (2 functions) UC4 UC5
  • Get_filtered_set
  • Allows specified fields from specific
    terminologies or combinations of terminologies to
    be searched enabling functionality beyond phase
    II to be added
  • UC4 Scheme hierarchy browse in no hits
  • from HILT or user/service request situation
  • UC 5 Improved precision use cases, either
  • via browsing scheme hierarchies,
    disambiguation
  • or specific requests for narrower/related
    terms
  • Other UCs plus Get_filtered_set

18
HILT A baseline service?
19
Future Possibility A Baseline Service?
  • Possible generic collaborative distributed
    approach
  • based on clients, distributed
    interoperability/KOS
  • services categorised in collections/services
    database
  • If clients can generate scheme hierarchies
    initial but
  • extendable service based on top level
    mappings and
  • hierarchy based collection retrieval looks
    feasible
  • Deeper levels of mapping as and when possible
  • Distributed approach could allow faster progress
    on
  • scheme expansion and deeper mapping
  • Local KOS services would serve local needs

20
  • Phase II emulation
  • Client sends users
  • Subject term to HILT
  • HILT sends captions
  • User selects caption
  • and DDC number
  • Client queries CS
  • database for
  • collections/schemes
  • User picks collection
  • and scheme
  • Client gets scheme
  • data from HILT
  • Client builds scheme
  • hierarchy to collection
  • using top level DDC
  • mapping to take user
  • in at an appropriate
  • point in hierarchy

21
  • Local hits first version
  • User finds/marks good
  • hits in local service
  • Client uses HILT to
  • get relevant DDC no.
  • Client queries CS
  • database for
  • collections/schemes
  • User picks collection
  • and scheme
  • Client gets scheme
  • data from HILT
  • Client builds scheme
  • hierarchy to collection
  • using top level DDC
  • mapping to take user
  • in at an appropriate
  • point in hierarchy
  • User navigates

22
  • Other variations
  • Client has local list of
  • of best collections,
  • uses CS database for
  • connection details and
  • schemes, and HILT to
  • get data to build
  • hierarchies for users
  • Client uses HILT DDC
  • mappings and CS
  • database to identify
  • collections, uses HILT
  • to build hierarchies for
  • schemes in HILT, but
  • CS databases (SLIC)
  • to find other inter-
  • operability/ terminology
  • services for schemes

23
A Baseline Service?
  • Basis of HILT service fourfold
  • Generic and adaptable open source client
  • HILT mapping and terminologies data
  • IESR (or similar) with scope extended to cover
    t-services
  • Other terminology/interop. services if and when
    they arise
  • What other terminology or interoperability
    services?
  • OCLC DDC LCSH mappings?
  • Red-Light-Green and similar?
  • Automated mapping services?
  • New services emerging from the current JISC call?

24
Further Information
  • Website (all HILT phases)
  • http//hilt.cdlr.strath.ac.uk/
  • E-mails
  • d.m.nicholson_at_strath.ac.uk
  • george.macgregor_at_strath.ac.uk
  • e.mcculloch_at_strath.ac.uk
  • HILT (SOAP) Demonstrator
  • http//hiltm2m.cdlr.strath.ac.uk/hiltm2m/hiltsoapc
    lient.php
Write a Comment
User Comments (0)
About PowerShow.com