Harnessing the Potential of Database Driven Websites

  • Published on

  • View

  • Download

Embed Size (px)


Harnessing the Potential of Database Driven Websites. David Lindahl Web Initiatives Manager River Campus Libraries University of Rochester. Background. Computer Science Xerox PARC Work Practice Study Web Design and Development. Our Organization. University of Rochester - PowerPoint PPT Presentation


  • Harnessing the Potential of Database Driven WebsitesDavid LindahlWeb Initiatives ManagerRiver Campus LibrariesUniversity of Rochester

  • BackgroundComputer ScienceXerox PARCWork Practice StudyWeb Design and Development

  • Our OrganizationUniversity of RochesterAnnual sponsored research funding over $1 billion46 PhD programsUR LibrariesOver 3 million volumes$14 million annual budget

  • OverviewDatabase Driven WebsitesDynamic Web PagesContent Management Systems

  • Why DB Driven? (part 1)Separate design from contentBuild content management toolsManage contentEnforce consistencyRetention policyStaff efficiencyProvide data integrityContent reuse

  • Why DB Driven? (part 2)Create a seamless experienceCreate a task oriented, activity oriented websiteImprove Usability through more flexibility/capability in pagesCustomization to users contextConnect to other systems

  • How DB Driven Sites Work123456

  • Examples of TechnologiesCold FusionMicrosoft SQLActive Server PagesJava, JSP, JavaScriptPERLFlashWeb Services, SOAP, XML

  • Library Website GoalsVisually appealing User-Centered DesignTask-oriented Infrastructure to support capabilities

  • What the Libraries DidRoles and ResponsibilitiesWeb Working GroupContent GroupsUsability GroupVendor PartnershipsTechnology Platforms / Integration

  • Our InfrastructureWeb Server (Cold Fusion, IIS, Novell)SQL 2000 ServerVoyager OPAC (Oracle DB)ILLiad ServerERA ServerSFX Server

  • Applications We BuiltContent Management SystemFind ArticlesCoursesSearch / Browse ResourcesQuestions and Comments SystemChange Requests

  • For Each ApplicationWhy?Features / CapabilitiesRoles and ResponsibilitiesDemonstrationSystem Architecture

  • 1. Content Management SystemWhy?Site surveyThousands of files with no inventoryInconsistencyStaff efficiencyUsabilityADA compliance

  • 1. Content Management SystemFeatures / Capabilities (part 1)Staff login / permissionsWeb administrationPage level metadataEdit page buttonAutomatic backup and restoreLink checkingURL independence / syntax standards

  • 1. Content Management SystemFeatures / Capabilities (part 2)Web statisticsSupport for multiple designs and sitesConsistency enforcementTitle/link matchingStyle sheetsCommon elementsBreadcrumbsADA compliance

  • 1. Content Management SystemRoles and ResponsibilitiesWeb development groupDesignDevelopmentAdministrationADALibrary staffContent creation and updateADA

  • 1. Content Management SystemDemonstrationStaff loginStaff modulesAnatomy of a pagePage propertiesEdit pageMore staff modules

  • Staff Login Login from any page Permissions determine available services

  • Footer (after Staff Login) Staff Modules Properties, Edit Page Logoff Link Checker Detailed Last Updated Information

  • Staff ModulesStaff Module Applications Page Manager Site Manager Feedback News Resource Manager Courses Manager Printer Transactions Voyager Link Checking Return To Site LogoffMore

  • Anatomy of a Page Common Header Common FooterOther Properties Title Background Color Meta Tags Page Number

  • Anatomy of a PageBody TemplateBody FileCommon Elements

  • Page Properties 1More

  • Page Properties 2More

  • Edit Page

  • More Staff Modules Logged In To TestDave Account No Access To Admin Functionality Limited Access To Applications Limited Access To Edit Content

  • 1. Content Management SystemMore DemonstrationOther sites in our CMSTitle link enforcement exampleWeb statisticsLink checking

  • Demo Other Sites

  • TitleConsistency

  • Demo Statistics

  • Demo Link Check

  • 1. Content Management SystemSystem Architecture (part 1)Web Server IIS Cold FusionDatabase Server Microsoft SQLIndex.cfmStyleSheet.cfmHeader.cfmBody.cfmFooter.cfmFile Server Checks System State In DBhttp://www.library.rochester.edu/index.cfm?page=12

  • 1. Content Management SystemSystem Architecture (part 2)Database Tables Contain: Pages Users Permissions System State Content (Application Data)

  • 2. Find ArticlesWhy?Finding articles is a big obstacle for undergraduatesUsability testing revealed this issueUsers dont know what a database is or how to select oneGoogle can be a lower quality resource

  • 2. Find ArticlesFeatures / CapabilitiesTask oriented pathways to finding articlesGoogle-like search interfaceIntegration of vendor technologiesHide the technologyAccess from home

  • 2. Find ArticlesRoles and ResponsibilitiesAJN content groupTask force on meta-search technologyPartnerships with vendorsIT department involvementERA ServerSFX Server

  • 2. Find ArticlesDemonstrationFindArticlesBrowseResultsViewFull Text(Gathering)

  • Demo Find Articles

  • Demo (gathering)

  • Demo Find Article Results

  • Demo Full Text

  • 2. Find ArticlesSystem Architecture

  • 3. CoursesWhy?Difficulty finding reserves materialSubject guides not effective

  • 3. CoursesFeatures / CapabilitiesSearch interfaceCustom web pages of library resources for coursesIncludes bibliographer, selected resources, link to the instructor created course page, the syllabus, and the reserves materialEasier for bibliographersImport from the registrars office

  • 3. CoursesRoles and ResponsibilitiesCourses content groupResponsible for features of systemWorking with registrars officeBibliographers are responsible for mapping library resources to specific courses.Faculty provide the syllabusReserves/circ staff for linking

  • 3. CoursesDemonstration (front end)FindCourseChooseSectionViewResourcesAccessSyllabus

  • Demo Courses

  • Demo Select

  • Demo Course Page

  • Demo Reserves

  • 3. CoursesDemonstration (back-end)

  • Demo Courses Admin

  • Demo Courses Admin 2

  • 3. CoursesSystem ArchitectureWeb applications haveaccess to catalog datain real time

  • Courses AvailabilityOpen source software:http://sourceforge.net/projects/libcb

  • 4. Search / Browse ResourcesWhy?Catalog difficult to useCatalog user interface not customizableCatalog not task orientedComplex set limits screenBoolean searching is not intuitive

  • 4. Search / Browse ResourcesFeatures / CapabilitiesSearch box and browsable list available for multiple resourcesUsability tested interface, customized to the needs of our usersConsistent design across all resource types and applications in the siteScheduled export of catalog records

  • 4. Search / Browse ResourcesRoles and ResponsibilitiesAutomated systemContent group reviews record displaysDesign group maintains site style guidelines

  • 4. Search / Browse ResourcesDemonstration

  • Demo Videos

  • Demo Pop Reading

  • Demo ejournals

  • Demo DB

  • 4. Search / Browse ResourcesSystem ArchitectureTo improve performance,Cold Fusion scheduledtasks copy catalog dataat regular intervals.

  • 5. Questions and Comments SystemWhy?Users were required to understand our organization in order to ask a question or make a comment.Some contact points went to a single individual and could get delayed or lost.

  • 5. Questions and Comments SystemFeatures / CapabilitiesDatabase-driven help desk applicationKnowledgeable staff member reads and forwards each piece of correspondenceQCs stored in a database with metadata (date, history)Statistics gathering is possible

  • 5. Questions and Comments SystemRoles and ResponsibilitiesReference Librarian responsible for triageAll staff responsible for responding to Questions and Comments

  • 5. Questions and Comments SystemDemonstration

  • 5. Questions and Comments SystemSystem ArchitectureWeb Server IIS Cold FusionDatabase Server Microsoft SQLEmail is used to notifystaff of new QCs andto respond to patrons.

  • 6. Change Request SystemWhy?Library staff were emailing the web development group directlyNewest requests were trumping more difficult outstanding requestsNo evaluation of the requests was taking place

  • 6. Change Request SystemFeatures / CapabilitiesChange request formChange request queue for viewing status of all requestsUrgent request awareness toolView history of past requests and resolutionsPrint lists designed for weekly review

  • 6. Change Request SystemRoles and ResponsibilitiesStaff submit requests and track progress through systemComments from the public can be converted to change requests by any staff memberWeb development group evaluates and implements changes

  • 6. Change Request SystemDemonstrationChangeRequest FormOutstandingQueueCompletedQueueUrgentQueue

  • Demo CR Form

  • Demo CR List 1

  • Demo CR List 2

  • 6. Change Request SystemSystem ArchitectureChange Requests arestored and updated inthe database.Web Server IIS Cold FusionDatabase Server Microsoft SQL

  • Others FeaturesChat systemOfflineCatalogILLiadNews systemHelp/FAQ system

  • Harnessing the Potential of Database Driven Websites

    David LindahlWeb Initiatives ManagerRiver Campus LibrariesUniversity of Rochester


    Talk about how a book is added automatically from catalog (integration)


View more >