A New Approach to E-reserves The Seneca Libraries Experience - PowerPoint PPT Presentation

a new approach to e reserves the seneca libraries experience n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
A New Approach to E-reserves The Seneca Libraries Experience PowerPoint Presentation
Download Presentation
A New Approach to E-reserves The Seneca Libraries Experience

play fullscreen
1 / 59
A New Approach to E-reserves The Seneca Libraries Experience
102 Views
Download Presentation
guiliaine
Download Presentation

A New Approach to E-reserves The Seneca Libraries Experience

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. A New Approach to E-reservesThe Seneca Libraries Experience End User – April 28, 2007 Presented by: Jane Foo, Manager of Digital Library Services & Information Systems Jennifer Peters-Lise, Metadata & Digital Services Librarian Sharon Tait, Digital Library Systems

  2. Today’s talk • Background on e-reserves project • Goals for e-reserves • Research committee • Prototypes • Encompass for Digital Collections • Set-up & customizations • Metadata • Policies & procedures • The future…

  3. Seneca College • Toronto, Ontario • 18,000 FTE; 90,000 PT • 678 FT faculty • 4 campus libraries • 12 FT librarians ; about 30 FT technicians • Over 100,000 books

  4. Goals for E-reserves • Collocate all course materials into one list • Access as much as possible online • Not online? Tell them where to find it! • User friendly and inexpensive system

  5. Course materials • Print Reserves • E-reserves • Traditional reserve-type material available online • Research by course pages

  6. Research by Course pages

  7. Seneca’s current reserves • Mixture of formats • Paper copies damaged; pages lost • Complaints about loan periods • Line-ups everywhere! • Major disconnection between materials • Research by course pages on our website • Reserves in the OPAC • Textbooks on OPAC but separate from reserves

  8. E-reserves Research Committee • Oct 2005 - Dec 2006 • Examined: • Seneca’s current reserves • Canadian E-reserves Scan • 17 existing e-reserves projects across Canada • Available systems for e-reserves See final committee report for more information…

  9. Systems tested for e-reservesCommercial system: DocutekSeneca owned systems: Blackboard, Voyager, EDC

  10. Docutek

  11. Course dashboard

  12. Docutek’s ERes • What we liked • User friendly • Self-maintenance available • Administrative control • What we didn’t like • Duplicate data entry • Cost • Stand-alone system

  13. Voyager

  14. Embedding the link in Blackboard

  15. Embedding the link in Blackboard

  16. Voyager • What we liked: • Cataloguing • Integration of print and electronic materials • Maintenance • What we didn’t like • Results/browsing interface

  17. Blackboard’s Content System

  18. Blackboard • What we liked: • Familiarity with system • Access for students • Logical hierarchy of readings • What we did not like: • No cataloguing – only filename • Limited searching capabilities • No reports and limited statistics • No administrative control over our content within Blackboard

  19. Encompass for Digital Collections

  20. Main page

  21. Browsing by course code

  22. Organizing readings by week

  23. Alternate organization of readings

  24. Search for course code

  25. Results display

  26. Encompass and BlackBoard • Embedded • Link directly to browsing list from a course page in Blackboard

  27. EDC – what we liked • Cataloguing workflow • Quick templates = no duplicate data entry • Immediate error correction • Top-down collection view • Maintain database integrity by limiting access to cataloguing • Import MARC records • Similarity to ILS system • Combines logical browsing of Blackboard with the cataloguing and data control of Voyager

  28. Setting Up EDC • MARC_ereserves.dtd • <!ELEMENT ereserves (course-code*, course-name*, begin-reserve-on*, remove-reserve-on*, instructor-name*, grouping*, title, url*, label-for-url*, author*, corporate-author*, corporate-author-subordinate*, editor*, series-title*, edition*, date-of-publication*, page-numbers*, periodical-publication-dates*, source*, file-size*, notes*, unique-identifier*, isbn*, issn*, call-number*, author-dates*, place-of-publication*, publisher*, publication-frequency*, subject*, subject-general*, subject-geographic*, subject-form*)> • <!ELEMENT course-code (#PCDATA)> • <!ELEMENT course-name (#PCDATA)> • <!ELEMENT begin-reserve-on (#PCDATA)> • <!ELEMENT remove-reserve-on (#PCDATA)> • <!ELEMENT instructor-name (#PCDATA)> • <!ELEMENT grouping (#PCDATA)> • <!ELEMENT title (#PCDATA)>…. • Base and Repository DMD • Collection DMD – Qualified DC (encdc.dtd) • Repo DMD – customized two dtds • Complete Repo DMD Mapping to Collection DMD based on Crosswalk developed by Jenn MARC_ereserves_wrapper.dtd (validation DTD) <!ELEMENT collection (ereserves*)> <!ELEMENT ereserves (course-code*, course-name*, begin-reserve-on*, remove-reserve-on*, instructor-name*, grouping*, title, url*, label-for-url*, author*, corporate-author*, corporate-author-subordinate*, editor*, series-title*, edition*, date-of-publication*, page-numbers*, periodical-publication-dates*, source*, file-size*, notes*, unique-identifier*, isbn*, issn*, call-number*, author-dates*, place-of-publication*, publisher*, publication-frequency*, subject*, subject-general*, subject-geographic*, subject-form*)> <!ELEMENT course-code (#PCDATA)> <!ELEMENT course-name (#PCDATA)> <!ELEMENT begin-reserve-on (#PCDATA)> …..

  29. Marctoqual-dublin.xsl <?xml version="1.0" encoding="utf-8" ?> - <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:output method="xml" indent="yes" /> <xsl:preserve-space elements="*" /> - <xsl:template match="/"> - <xsl:element name="esdrecord"> - <xsl:for-each select="MARC_ereserves | ereserves"> <xsl:call-template name="itemtitle" /> <xsl:call-template name="auth" /> <xsl:call-template name="abs" /> <xsl:call-template name="subjterms" /> <xsl:call-template name="all" /> </xsl:for-each> </xsl:element> </xsl:template> - <xsl:template name="itemtitle"> - <xsl:if test="title"> - <xsl:element name="itemtitle"> - <xsl:variable name="str"> - <xsl:for-each select="title"> - <xsl:if test="position() > 1"> …. • Search indices • Collection: Search Index – default qual-dublin-cm.xsl Access Points Index – modified existing qual-dublin-bu.xsl • Repo: Search Index:customized a new xsl based on the existing qual-dublin.xsl • New Search Key Indices: Instructor (Ikey) Public Course code (ckey) Public Date Created/Updated (dkey) – Staff search only

  30. Marc to MARCXML script (in MarcEdit) <?xml version="1.0" encoding="UTF-8" ?> <!-- sef --> - <xsl:stylesheet version="1.0" xmlns:marc="http://www.loc.gov/MARC21/slim" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="marc"> <xsl:import href="MARC21slimUtils.xsl" /> <xsl:output method="xml" encoding="UTF-8" indent="yes" omit-xml-declaration="yes" /> <!-- only for bulk import, add to output tag: doctype-system="../dtds/MARC_ereserves_wrapper.dtd" --> - <xsl:template match="/"> - <ereserves> <xsl:apply-templates /> </ereserves> </xsl:template> - <xsl:template match="marc:record"> <xsl:variable name="controlField001" select="marc:controlfield[@tag=001]" /> <!-- title --> - <xsl:for-each select="marc:datafield[@tag=245] | marc:datafield[@tag=246]"> - <title> <xsl:value-of select="normalize-space(.)" /> </title> </xsl:for-each> <!-- URL --> - <xsl:for-each select="marc:datafield[@tag=856]"> - <url> <xsl:value-of select="marc:subfield[@code='u']" /> </url> </xsl:for-each> <!-- URL label --> - <xsl:for-each select="marc:datafield[@tag=856]"> - <url_label> <xsl:value-of select="marc:subfield[@code='z']" /> </url_label> </xsl:for-each> <!-- author --> - <xsl:for-each select="marc:datafield[@tag=100]"> - <author> <xsl:value-of select="normalize-space(.)" /> </author> </xsl:for-each> • Bulk Loading v. Client-Based loading • Server Metaload • generic-shredder.xsl - modified • XmlLoader.properties – modified • Started with concept of bulk loading but eventually Marc records were loaded individually through staff client Export from library catalogue – converted to xml via marcedit • Voyager Export

  31. Customizing the Metadata • Wish list for metadata • Compared wish list to MARC, CanCore, Dublin Core • MARC won overall • Chose a sub-set of MARC fields, added extra local fields • Human readable field names to accommodate non-cataloguing staff • AACR2 cataloguing rules

  32. Metadata profile • MARC fields • title, URL, label for URL, author, corporate author, corporate author subordinate unit editor, series title, edition, date of publication, page numbers, periodical publication dates, source, notes • Non-MARC fields • course code, course name, begin reserve on, remove reserve on, instructor name, grouping, file size

  33. Customizing the Metadata • Print reserve records • Save bib from Voyager • Convert bib to xml using MARCedit • Custom XSLT file defining our metadata profile • Import xml file into EDC

  34. Metadata profile • MARC fields • title, URL, label for URL, author, corporate author, corporate author subordinate unit editor, series title, edition, date of publication, page numbers, periodical publication dates, source, notes • Placeholders for imported MARC records for print reserves. • (no data is entered into these fields for e-reserves) • unique identifier, ISBN, ISSN, call number, author dates, place of publication, publisher, publication frequency, subject, subject (general subdivision), subject (geographic subdivision), subject (form subdivision) • Non-MARC fields • course code, course name, begin reserve on, remove reserve on, instructor name, grouping, file size

  35. User Interface requirements • Browse > search • One-click from title • Uncluttered (less is more) • Can be embedded / integrated into other Web interfaces • Language that makes sense to students • Branding & identity

  36. Customization notes • XSLT, CSS … and APIs • code cleanup • modified: basic search, advanced search, results list, object record and view relationship pages • display order • custom metadata xsl files for field display • custom search indices (course code, instructor, date added)

  37. Custom field displays

  38. Linking directly from browse and search • 2 types of links: • link • (url tag) • digital object • (objResURL tag)

  39. Live linking to Voyager automatically constructed live link to Voyager record using imported Bib ID(aka unique-identifier tag)

  40. Re-purposing “View Relationships”

  41. This is just the beginning … • 2 iterations so far • Faculty involvement from project onset • Staff town hall and training sessions • distinction between electronic vs. print • User-centered testing / feedback – Summer 2007 • Explore and create more opportunities for embedding / integration

  42. Policies and Procedures – content & staffing • Merge Research by Course pages into the system • Both reference and borrower services staff will catalogue materials for the system