Collaborative Collaborative Development of a Development of a

Web Knowledgebase Web Knowledgebase for a Liaison for a Liaison

Program:Program:“Back to the Future” “Back to the Future” Holly Harden, MLIS, Liaison Librarian

 Kathleen B. Oliver, MSLS, MPH, Associate Director for

Communication and Liaison Services 

Tina Otter, MLIS, Reference Librarian 

Ming Zhu, MIS, Web Development Programmer 

William H. Welch Medical LibraryJohns Hopkins University

Baltimore, Maryland 

OutlineOutline

• Liaison program background and goals• Collaborative elements and database

development• Database life cycle• Knowledgebase and management tool

Liaison Program BackgroundLiaison Program Background

Issues– Desktop delivery of information– Library gate count declines– Users need librarian expertise– Library needs user input on products and

services

Liaison Program BackgroundLiaison Program Background

• Liaison program established to address issues

• Structured for outreach to users– Each department assigned a liaison– Liaison committee formed

• Seven Librarians• One scientific editor & educator

Liaison Program GoalsLiaison Program Goals

• Communicate about library services, resources, and programs

• Listen to faculty, students, and staff• Identify information needs• Report back on findings• Build relationships

Who’s involved? Who’s involved?

• Small number of liaisons • Large number of clients

The ChallengeThe Challenge

• Internal information sharing• Program monitoring• Program development • Program management

A SolutionA Solution

Build a database of liaison contacts and activity!

Collaborative ElementsCollaborative Elements

• Who– Librarians– Web developers

• Importance of alliance• Creation of new

knowledge

“Many heads are better than one”

Collaborative ElementsCollaborative Elements

• Database development needs assessment– Purpose of database– Goals of liaison program– Model representation of liaison work

process

Collaborative ElementsCollaborative Elements

• Development meetings– Demonstrations– Live Q&A sessions– Online Q&A (e-mail)– Testing, feedback, analysis,

improvement

Liaison Database Life CycleLiaison Database Life Cycle

• Liaison program requirements definition• Software requirements definition

– Oracle database software– Cold Fusion Web application– Architectural design

• Detailed design and construction – Coding and debugging

• Delivery to the user• Operations

Information ArchitectureInformation Architecture

Liaison UserLiaison UserCold Fusion Cold Fusion Application Application

ServerServer

Oracle Database

Server

Data Data TransactionTransaction

Web Web ServerServer

Design HistoryDesign History

• Documentation and content• Generating reports• Descriptive terms for contact categories• User interface

Functionality and Usability Functionality and Usability

• Convenient and user friendly– Add a contact “on the fly”– Multiple staff selection– Sorting options

Original Add a Contact Screen

Current Add a Contact Screen

Statistical Reporting Screen

Report screenshotReport screenshotStatistical Report Result Screen

Search Contacts by Training Category

Search Results: Sorted by Date

Search Results: Sorted by Department

Database DevelopmentDatabase Development

• Continuous evolution• Continuous collaboration• Continuous use identifies further

development

The liaison knowledgebase develops as the liaison program evolves and new needs are identified.

ConclusionConclusion

• Knowledgebase for liaisons• Management data for other library

functions    – Budget justification– Meeting background

• Data for program evaluation & development