Update on the Enhancement Process

1
AVUG Meeting Melbourne, Australia
Endeavor Update 6 February 2004
2
Topics

• Endeavor Information Systems Overview
• Donald Muccino, Chief Operating Officer
• User Community Interactions and Opportunities
• Shelley Hostetler, Voyager Product Manager
• Voyager Unicode Release and Early Release
• Keeley Sorokti, Customer Support Manager
• Endeavor Product Update, User Group Update
• Shelley Hostetler, Voyager Product Manager
• Questions

3
Endeavor Management Team
4
Endeavor Mission
Endeavors mission is to develop, provide, and
integrate building blocks and services to create,
facilitate, maintain and enhance the library and
knowledge infrastructures of our customers.
5
Vision for Endeavor

• To be the best Library Solutions group
• Develop our organization to meet future goals and
  strategies. This would include
• Reviewing workflows and responsibilities
• Bridge/eliminate existing silos
• Elevate accountability
• Improve internal and external communication
• Preparing ourselves for a much larger role in
  Elsevier

6
Company Objectives

• To be the best Library and Knowledge
• Infrastructure Provider
• Innovation
• Concentrate on BEST PRACTICE
• Quality
• Customer Service
• Market Share

7
Endeavor Information Systems

• Employees
• Offices
• Chicago, IL USA (headquarters)
• London, UK
• Sydney, Australia
• 160 staff members
• 33 with advanced library science degrees
• Customers
• 1200 Library Customers
• 10 National Libraries
• 5 continents
• 16 countries

8
Endeavor A Full Range of Services

• Outstanding Data Migration to convert your most
  valuable resource
• Cooperatively planned Implementation scheduled to
  match your local needs
• Complete training on all Endeavor modules
• Phone and email customer support for all of your
  questions -- large or small
• Complete 24x7 support resource via SupportWeb,
  our customer-secure website

9
Trends
THEN
NOW
Integrated Library Systems
Interoperability and Integration
End user satisfaction and experience
Automated back office
Primarily concerned with printed material
Explosion in electronic content
XML based, multiple format standards
MARC based
Local system control
Hosted solutions
10
Endeavors Current Offerings Three Main
Systems

• Voyager
• Integrated Library System
• Traditional Back Office functions
• Acquisitions, Cataloging, Circulation
• User-friendly OPAC
• ENCompass
• Resource Access
• Federated Search
• Digital Collections
• Organization System for Local Digital Content
• Journals On Site
• Local Storage of Full-Text Journal Content
• Course Content Integrator
• Instructor tool to generically link library
  content into to courses
• LinkFinderPlus
• OpenURL-enabled Link Resolver

11
Customer Services Environment

• High Rate and Number of Changes
• Sophisticated and Experienced User Base
• Increasingly Complex Environments and Uniqueness
• Many New Staff
• Mature Product Set
• Commodity Product/Custom Workflow
• New and Evolving Product Mix on Digital
• Ultimately Reintegrating Functionality

12
2003 Accomplishments

• Launched LinkFinderPlus Subscription Service
• Consolidated Technical Groups under CIO
• 130 Voyager Implementations
• 25 Digital Implementations
• Nearly 1000 Upgrades
• Created improved HSE Connector Update Process
• View your incidents online for improved
  efficiency
• Implemented new phone system for Support

13
2003 Accomplishments

• Australasian Project Manager Position Opened
• Hired Curriculum Development Manager 3 Trainers
• Josephine Crawford
• Increased Customer Support Staff
• New Digital Services Team Leader
• 2 new Digital support staff 2 new Voyager
  support staff

14
2004 Goals

• Improve CS capabilities to meet the services
  needs of a growing and technically sophisticated
  customer base and integrated product set
• Develop Metrics and Measure ResultsContinuous
  Improvements
• Manage Change Proactively

15
(No Transcript)
16
Endeavor Mission
Endeavors mission is to develop, provide, and
integrate building blocks and services to create,
facilitate, maintain and enhance the library and
knowledge infrastructures of our customers.
Endeavors mission is to develop, provide, and
integrate building blocks and services to create,
facilitate, maintain and enhance the library and
knowledge infrastructures of our customers.
17
Building Block Categories

• Data Management Modules
• Voyager for physical aspects and MARC-based
  record management
• Integration Modules
• ENCompass for Resource Access providing federated
  searching
• LinkFinderPlus providing OpenURL-enabled linking
  to full-text of articles
• Digital Library Operating Systems Modules
• ENCompass for Digital Collections providing
  digital object management
• ENCompass for Journals OnSite providing
  institutional repository management

18
Endeavor Product Architecture

ENCompass Management Modules and/or External
Resources
19
Endeavor Product Architecture
20
(No Transcript)
21
Strategic Advisory Boards

• European Library Advisory Board
• Announced September, 2003
• Australia/New Zealand Library Advisory Board
• Announced February, 2004
• . . . representing the thought leaders and
  innovators in our user group to discuss with us
  the larger needs and trends of this community.

22
Australia/New Zealand Library Advisory Board

• Nominees should demonstrate an understanding of
  the issues that do, and will, concern libraries
  today and in the years to come.
• Please nominate individuals who have demonstrated
  vision, leadership, and dedication to the library
  community and who understand the important issues
  facing libraries today.
• Nominations should be sent to Susie Thorpe at
  susie.thorpe_at_endinfosys.com.
• Deadline for nominations 31 March 2004

23

• Endeavor Information Systems Overview
• Donald Muccino, Chief Operating Officer
• User Community Interactions and Opportunities
• Shelley Hostetler, Voyager Product Manager
• Voyager Unicode Release and Early Release
• Keeley Sorokti, Customer Support Manager
• Endeavor Product Update
• Shelley Hostetler, Voyager Product Manager
• Questions

24
Strategic Advisory Boards

• Our primary goal is to advance a joint
  understanding of the issues that do, and will,
  concern libraries today and in the years to come.
  
•  
• With such a board in place, Endeavor will be in a
  position to better anticipate these libraries
  needs and to deliver appropriate solutions in a
  timely way
•  
• We anticipate that our partnership with these
  representatives will result in a more
  constructive and effective communication in
  between Endeavor and our users.

25
Customer Feedback Cycle

• Endeavor works with Task Forces to further define
  requirements, specifications, and design

26
Enhancement Committees

• 8 Committees
• Acquisitions
• Cataloging/Authority Control
• Circulation/Reserves
• Inter-Library Loan
• Media Scheduling
• OPAC/Citation Server
• Serials
• Technical

27
Enhancement Committees

• Enhancement Committees review all requests
• Determines which workflows to prioritize
• Meets via Webex/teleconference, with Product
  Management, Development
• Develops problem statements
• Four members
• Selected by EndUser Board
• Alternating two year terms
• Two-term limit
• Chair selected by Committee members

28
Enhancement Council

• Comprised of Committee Chairs
• Supplies a broader perspective
• Determines impact on other modules
• Identifies trends
• Negotiates priority recommendations
• Forwards to Endeavor

29
Enhancement Process
September 2003
November 2003
January 2004
August 2003
June 2003
April 2004
Endeavor offers feedback on statements at annual
user group meeting.
Enhancements given to committees for review.
Problem Statements finalized.
Committees complete problem statements.
Council meets to prioritize all statements.
Committees begin reviewing enhancements.
Time line NOT to scale
30
Participation

• Submitting Enhancement Statements
• . . . describe a workflow need a user has
  encountered that is not currently handled by the
  software
• http//support.endinfosys.com/cust/board/enhancest
  ate.html
• Volunteering for enhancement committees
• Call for volunteers in September
• http//support.endinfosys.com/cust/board/process1.
  html
• Providing feedback on posted problem statements
• Review the current problem statements and respond
  to the Committees
• http//support.endinfosys.com/cust/board/enhanceme
  mbers.html

31
Task Forces

• Purpose
• To further define enhancements to a workable set
  of requirements
• To review specifications
• To review design
• Makeup
• Appointed jointly
• EndUser Board
• Endeavor
• Represent a cross-section of libraries
• Understand best practices
• Provide industry expertise
• Membership cross-over between Enhancement
  committee and task force

32
Global Data Change Task Force

• . . . to explore the requirements that
  catalogers have for working with batches of
  authority, bib, mfhd, and item records, such as
  replacing, adding or deleting data.
• Members
• Michael Doran - U of Texas at Arlington
• Ann Della Porta - Library of Congress
• Gary Strawn - Northwestern University
• Patricia Scott - University of Adelaide
• Charles Woods - University of Waterloo
• Margaret Foote - Eastern Kentucky University
• Karen Davis - Georgia State University
• Ulla Ikäheimo Linnea2 Consortium, Finland

33
EndUser Board
The purpose of the Organization

• Association of individuals and organizations
  having an interest in Endeavor products
• Exchange ideas and explore issues of mutual
  concern
• A conduit of advice and information between users
  and EISI
• Build consensus among customers for future
  software enhancements
• Synthesize for EISI the input of members
• Facilitate the exchange of information and advice
  among members

34
EndUser Board Members

• Debbie Morrow, President
• Grand Valley State University, USA
• Will Frost, Vice President/President Elect
• University of Hawaii, USA
• Don Hamilton, Secretary/Treasurer
• Tri University, Canada
• Del Hamilton, Past President
• Slippery Rock University, USA
• Ellie Briscoe, Board Member
• National Geographic Society, USA
• Annu Jauhiainen, Board Member
• Linnea2 Consortium, Finland
• Janet Lute, Board Member
• Princeton University, USA
• Alan Manifold, Board Member
• Purdue University, Indiana, USA

35
Call for Nominations

• Three 3 new members of the Endeavor Users Group
  (EndUser) Executive Board will be elected this
  year.
• If you would like to nominate either yourself or
  someone else, please email Rick Heyser at
  rick.heyser_at_tccd.net, or Ellie Briscoe at
  ebriscoe_at_ngs.org by 20 February 2004.
• Include the nominee's name, institution,
  telephone number and email address.
• Note Endeavor sponsors travel and accommodation
  for board meetings.

36
EndUser Board Participation

• Each site with a signed contract has one vote.
  Once the slate of candidates is set, a ballot
  will be sent to the Designated Voting
  Representative at each site. Election results
  will be announced by email before the annual User
  Group meeting in April.
• Contact Support to check your contacts and verify
  that you have an EndUser Voter for your site.
• To contact the EndUser Board
• enduboard_at_voyager.ship.edu

37

• Endeavor Information Systems Overview
• Donald Muccino, Chief Operating Officer
• User Community Interactions and Opportunities
• Shelley Hostetler, Voyager Product Manager
• Voyager Unicode Release and Early Release
• Keeley Sorokti, Customer Support Manager
• Endeavor Product Update
• Shelley Hostetler, Voyager Product Manager
• Questions

38
Release Update

• Voyager
• 2001.2 in General Release
• Voyager with Unicode in Early Release
• General Release in Q2
• Voyager 5.0 in Alpha
• Target Early Release in Q1 2005
• ENCompass
• 3.0 in General Release
• 3.5 in Beta
• Early Release in late Q1/early Q2
• LinkFinderPlus
• 3.5 in General Release
• LinkFinder Plus Subscription Service in General
  Release

39
Voyager with Unicode Topics

• New Features
• Workflow Improvements in Circulation
  Acquisitions
• Endeavors Unicode Implementation An Overview
• Upgrade What to Expect
• Resources to help you prepare The Road to
  Unicode
• Prepping for your upgrade
• Conversion Logging
• Cataloging
• New Validation Rules
• Special Characters
• Fonts
• Import/Export Round Trip of Records
• WebVoyage
• Searching
• Z39.50
• The Rest of Voyager

40
New Features

• Cataloging, Acquisitions Circulation
• Increased Resource Availability for Staff
• LinkFinderPlus available in Cataloging,
  Acquisitions Circulation
• Record menu in Cataloging contains a Send Record
  to option
• Send Record To LinkFinderPlus
• Toggle record view from staff client to WebVoyáge
• Record menu in Cataloging contains a Send Record
  to option
• Send Record To WebVoyáge
• Configured in voyager.ini file MARC POSTing
  stanza

41
New Features

• Cataloging
• Increased Resource Availability for Staff
• Drive searches to resources on the web
• Add new button to search interface in staff
  clients which inserts the query text into any URL
  syntax
• Click button and a browser is opened search is
  executed
• This is PC specific (voyager.ini)
• Possible applications
• Link to another OPAC
• Link to one of your vendors
• Link to an online book seller

42
New Features

• Circulation
• Filter Fine/Fee List
• Operators can view the fines/fees/demerits that
  are most relevant to their circulation happening
  location
• Session Preferences can be used to define the
  active circ desk as the default limit.

43
New Features

• WebVoyáge
• Bib ID Redirect to WebVoyáge
• OpenURL Item Requests
• Append patron information to send to another
  requesting utility (like Relais)
• Get patron authentication along with standard
  OpenURL
• Course Reserves Browsing (New option for display)

44
New Features

• Call Slip
• Call Slip Queue Reassignment
• Call Slip Item Substitution Without Barcode
• Citation Server Call Slip Requests

45
Interface Workflow Improvements

• Based on Circulation Acquisitions Task Forces
  Input
• Circulation
• Patron Search focus is always on Last Name now
• Access to patron record during discharge
• You can retrieve patron record for any discharged
  item
• Items entry is selected in discharged items list
  automatically
• Selected items lists only allows single item to
  be selected
• Acquisitions
• Check-in note remembers its placement (i.e.
  bottom left of screen)
• Clear button on all search forms to return to
  defaults
• See SupportWeb gt Release Notes area for full list
  of the 31
• Improvements incorporated into the Unicode
  release.

46
Voyager with Unicode Topics

• New Features
• Efficiency Improvements in Circulation
  Acquisitions
• Endeavors Unicode Implementation An Overview
• Upgrade What to Expect
• Resources to help you prepare The Road to
  Unicode
• Prepping for your upgrade
• Conversion Logging
• Cataloging
• New Validation Rules
• Special Characters
• Fonts
• Import/Export Round Trip of Records
• WebVoyage
• Searching
• Z39.50
• The Rest of Voyager

47
Wed Like to Thank the Task Force Members

• Cambridge University
• Getty Research Institute
• University of Hawaii
• Library of Congress
• Linnea2 Consortium of Finland
• Pepperdine University
• University of Pittsburgh
• Princeton University
• Yale University

48
Unicode Implementation in Voyager

• Follows Standards (not proprietary)
• http//www.unicode.org
• http//lcweb.loc.gov/marc/specifications/specchar
  ucs.html
• (LCs format of MARC records that use
  Unicode. Voyager will follow this specification.
  Code Tables also available here.)
• The Voyager implementation of the Unicode
  standard gives libraries and their users greater
  flexibility when accessing collection materials
  that contain both Roman and non-Roman text.
• By introducing improved multilingual input and
  display capabilities in Voyager, our libraries
  stay on the leading edge of MARC21 format.
• Greater script coverage for cataloging materials
  from around the world.

49
Unicode Implementation in Voyager

• Designed to work with Windows
• Standard Windows 2000/XP Unicode support
• Standard Unicode fonts
• Standard input using IME (Input Method Editors)
• Standard browser support
• Data Conversion
• The MARC records in the Voyager database will be
  converted from Voyager legacy encoding (VRLIN) to
  (MARC21-compliant) UTF-8 encoding.

50
Voyager with Unicode

• Find and display records in their native
  languages
• Select the Unicode font of your choice
• Create and edit any MARC record using UTF-8
• Error-checking and logging during conversion and
  upgrade
• Import and export of records with any supported
  character set
• Display Unicode characters in WebVoyáge without
  any proprietary software

51
Voyager with Unicode Topics

• New Features
• Efficiency Improvements in Circulation
  Acquisitions
• Endeavors Unicode Implementation An Overview
• Upgrade What to Expect
• Resources to help you prepare The Road to
  Unicode
• What to Expect
• Conversion Logging
• Cataloging
• New Validation Rules
• Special Characters
• Fonts
• Import/Export Round Trip of Records
• WebVoyage
• Searching
• Z39.50
• The Rest of Voyager

52
Early Release Update

• Started in January, 2004
• Scheduled to end in Q2
• 3 Unicode Task Force Members
• 2 European Customers
• 1 Windows Server Customer

53
Upgrade Resources

• SupportWeb Resources
• The Road to Voyager with Unicode
• New icons for various types of information
• Tech, Functional, Must Read
• Release Handbook
• 38 pages of detailed information on each new
  feature
• Bug Fix List
• Interface Workflow Improvements List Coming
  Soon
• Preview Server Coming Soon

54
Upgrade What to Expect

• Upgrade to Oracle 9.2
• Requires an additional 3 gigs of Disk Space
• Data Conversion
• MARC records are converted from VRLIN (Voyager
  legacy encoding) to MARC21 compliant UTF-8
  encoding
• Leader position 9 becomes an a
• Conversion Log Created
• Slight increase in disk space needed (1 2)
• All indexes and database columns with MARC data
  are regenerated after conversion.
• Will take longer than previous upgrades

55
Upgrade What to Expect

• You can still do your own upgrade if you are 500
  certified.
• Pre-EndUser Post-EndUser Cert. 500 will contain
  Unicode specific information if you want a
  refresher
• No need to do data clean up beforehand
• Easier to do after the upgrade
• No loss in functionality while you are doing any
  clean up that you feel is necessary

56
Upgrade PC Requirements

• In order to enjoy the full range of benefits, you
  must
• have current software on your PCs.
• For our customers, that means
• Windows 2000 or XP for staff PCs
• WebVoyáge PCs will not require 2000 or XP you
  could use NT or 98 here.
• Unicode compliant browsers
• IE 6
• Netscape 6

57
Upgrade Conversion Error Logging

• Libraries need to know the details about the
• results of the conversion process.
• Full error checking and logging is included as
  part of the upgrade.
• A report of any records that have any anomalies,
  whether or not they have anything to do with the
  conversion.
• It will include details like the field, the tag,
  the characters around the field where the problem
  occurred.

58
Upgrade Conversion Details

•  
• The conversion application handles each field in
  the record individually.
• As each field is processed, it may change length,
  requiring adjustments to the leader and directory
  of the record. 
• When all fields in the record are processed, its
  saved to the database with a leader position
  a. 
• Both record-level and field-level checking is
  performed. In some cases an entire record might
  fail conversion it is more likely that an
  individual field failed to be converted.
• Records will fail to convert if they contain text
  that cannot be mapped into Unicode according to
  the standard MARC-8 to Unicode mappings.
• Records that fail conversion will be stored in
  the database as-is, without being converted to
  Unicode.

59
Upgrade Reading the Log
Field Level Errors Warnings

• Sample Error
• -bib 5008559 880 c-gt8 undefined char page1 at
  19 '217c55213b79217c !U!y!'
• 880 c-gt8 undefined char page1 at 42
  '217c791b2828422c !y.((B,'
• 880 c-gt8 undefined char page1 at 22
  '217c2e21464d2137 !.!FM!7
• Record Type and ID bib 5008559
• Tag of the field 880
• Voyager Encoding to Unicode c-gt8
• Specific warning or error undefined char page
• Code Page Indicator page1 1 CJK characters
• Position within the Field that caused at 19
• the problem
• Hexadecimal dump of the source
  '217c55213b79217c
• character following 7 characters
• ASCII dump of the source character and !U!y!'
• the following 7 characters

60
Voyager with Unicode Topics

• New Features
• Efficiency Improvements in Circulation
  Acquisitions
• Endeavors Unicode Implementation An Overview
• Upgrade What to Expect
• Resources to help you prepare The Road to
  Unicode
• Prepping for your upgrade
• Conversion Logging
• Cataloging
• New Validation Rules
• Special Characters
• Fonts
• Import/Export Round Trip of Records
• WebVoyage
• Searching
• Z39.50
• The Rest of Voyager

61
Cataloging Identifying non-Unicode data

• To identify a non-Unicode record, select a color
  for Conversion records in Session Defaults and
  Preferences gt Colors-Fonts tab.

62
Cataloging Identifying non-Unicode data

• Any non-converted record displays in the chosen
  color.

63
Cataloging Identifying non-Unicode data

• Additional methods for identifying a
• non-Unicode record (from conversion).
• Arial Unicode MS

64
Cataloging Diacritics in Voyager

• Cataloging practices then and now
• Pre-Unicode input in Cataloging accent
  character (diacritic) then the base character.
• Example espana
• Post-Unicode input in Cataloging base character
  then the accent character (diacritic).
• Example espana
• Ability to display combined characters is an
  improvement over past versions and a way to
  insure accurate entry

65
Special Characters.cfg
SpecialCharacters.cfg located in the
C\Voyager\Catalog folder Defines what is in the
special character entry dialog box You can define
your most used characters here.
66
Special Characters.cfg
This is what the dialog box in Cataloging looks
like.
67
Diacritics in Voyager MARC21 vs. Unicode

• Composition and Decomposition
• Composed Single Character n
• Decomposed Two Characters n
• Unicode Composed (generally)
• MARC21 Decomposed (generally)
• Your data is decomposed now and will remain
  decomposed post conversion.
• Data stored decomposed in the database displays
  in Cataloging as.ñ

68
Cataloging - New Validation Rules

• Session Defaults Preferences gt Validation Tab
• Bypass Decomposition of accented characters for
  MARC21
• Unchecked means Voyager checks the record when it
  is saved and stores the record according to
  MARC21 rules.
• Checked means that Voyager will store the
  characters composed, as per standard Unicode.
• Bypass MARC21 Character set validation
• Select this option to prevent the validation of
  records against the MARC21 character set when you
  save to the database.
• When this option is not selected, the MARC21
  Repertoire.cfg file stored in the Catalog folder
  of the Voyager software on each PC is used for
  character set validation.

69
Cataloging Input of Non-Roman Text

• This release supports all standard Microsoft
  Windows keyboard and input method editors (IMEs).
• Taking advantage of these standards allows
  operators to search for, display, and edit the
  contents of all MARC records using the full range
  of UTF-8 characters.
• Including right-to-left input!

70
Cataloging Input of Non-Roman Text

• Example of Windows On-Screen Keyboard.

71
Voyager with Unicode Topics

• New Features
• Efficiency Improvements in Circulation
  Acquisitions
• Endeavors Unicode Implementation An Overview
• Upgrade What to Expect
• Resources to help you prepare The Road to
  Unicode
• Prepping for your upgrade
• Conversion Logging
• Cataloging
• New Validation Rules
• Special Characters
• Fonts
• Import/Export Round Trip of Records
• WebVoyage
• Searching
• Z39.50
• The Rest of Voyager

72
Fonts You Decide!
Voyager Font Goes Away!
73
Fonts

• Just because a MARC record contains non-Roman
  characters does not mean you can see them.
• You have to use a font that in Unicode compliant.
• Lucida Sans Unicode installed by default with
  Windows
• Arial Unicode MS
• Good choice for libraries with mixed cataloging
• Microsoft Office must be installed to get this
  font

74
Voyager with Unicode Topics

• New Features
• Efficiency Improvements in Circulation
  Acquisitions
• Endeavors Unicode Implementation An Overview
• Upgrade What to Expect
• Resources to help you prepare The Road to
  Unicode
• Prepping for your upgrade
• Conversion Logging
• Cataloging
• New Validation Rules
• Special Characters
• Fonts
• Import/Export Round Trip of Records
• WebVoyage
• Searching
• Z39.50
• The Rest of Voyager

75
Import / Export

• Bulk Import
• Fundamentally the same as before
• Leader byte 9 is checked against the incoming
  character set identified in the import rule.
• Blank non-Unicode converted imported
• a Unicode imported
• Neither Blank nor a errors out not imported
• Records that cant be converted error out not
  imported
• Voyager does not check for decomposed vs.
  composed. The data will be stored in the form it
  is received.

76
Import / Export

• Bulk Import
• Character set mapping for Bulk Import is
  designated in the Bulk Import rule in
• SysAdmin gt Cataloging gt Bulk Import Rules.

77
Import / Export

• Marcexport
• Default export character set is MARC21 UTF-8
• Use the a option to choose different character
  set (in the command line)
• LATIN1 will get a dot exported for characters
  outside the LATIN1 character set
• If it cannot find a mapping for a composed
  character it will decompose and try to find a
  match for each part.

78
Import / Export

• New ISBN Index
• 020N 020a Number only
• 020R 020z Number only
• 020 a 1234567890 (Knopf)
• 020 a 1234567890
• ? Check your bib and auth dup-detection profiles
  in System Administration!

79
Voyager with Unicode Topics

• New Features
• Efficiency Improvements in Circulation
  Acquisitions
• Endeavors Unicode Implementation An Overview
• Upgrade What to Expect
• Resources to help you prepare The Road to
  Unicode
• Prepping for your upgrade
• Conversion Logging
• Cataloging
• New Validation Rules
• Special Characters
• Fonts
• Import/Export Round Trip of Records
• WebVoyáge
• Searching
• Z39.50
• The Rest of Voyager

80
WebVoyáge

• MARC data supplied to the browser in UTF-8
• New UTF-8 download/save format
• Search and display in native languages for staff
  and users.
• WebVoyáge and Cataloging allow for UnicodeTM
  input in searching to search for and and retrieve
  records in their native languages.
• This display of all characters in the record is
  available for non-Latin scripts, including
  right-to-left scripts like Arabic and Hebrew,
  taking advantage of the web browsers native
  rendering support.

81
WebVoyage Public Display of Unicode Records
82
Voyager with Unicode Topics

• New Features
• Efficiency Improvements in Circulation
  Acquisitions
• Endeavors Unicode Implementation An Overview
• Upgrade What to Expect
• Resources to help you prepare The Road to
  Unicode
• Prepping for your upgrade
• Conversion Logging
• Cataloging
• New Validation Rules
• Special Characters
• Fonts
• Import/Export Round Trip of Records
• WebVoyage
• Searching
• Z39.50
• The Rest of Voyager

83
Searching Interacting with other systems

• Incoming Z39.50 Connections
• z3950svr will send MARC8 encoded or UTF-8 encoded
  records, per the librarys preference
• You can set up two different z3950svr ports so
  that you can provide records in both formats
• Outgoing Z39.50 Connections
• Will be able to serve up records in Unicode
• Will convert incoming records based on new
  Database Definitions setting in System
  Administration called Source Character Set
• Latin1 (non unicode)
• MARC 21 MARC8 (non unicode)
• MARC21 UTF8
• OCLC (non unicode)
• RLIN legacy (non unicode)
• Voyager legacy (non unicode)

84
Voyager with Unicode Topics

• New Features
• Efficiency Improvements in Circulation
  Acquisitions
• Endeavors Unicode Implementation An Overview
• Upgrade What to Expect
• Resources to help you prepare The Road to
  Unicode
• Prepping for your upgrade
• Conversion Logging
• Cataloging
• New Validation Rules
• Special Characters
• Fonts
• Import/Export Round Trip of Records
• WebVoyage
• Searching
• Z39.50
• The Rest of Voyager

85
The Rest of Voyager

• Non-MARC data is not converted
• Acquisitions data
• Circulation data (patron info, etc.)
• Item data
• Reporter
• Not Unicode compliant
• Translates data to LATIN1
• Dots appear where you used to see squares

86
Prepackaged MSAccess Reports

• The Oracle client returns UTF-8 or Latin-1
  encoded data to Access.
• Access cannot properly display UTF-8 data,
  therefore an internal conversion function is used
  to convert the UTF-8 encoded data into UTF-16
  encoded data.
• Latin-1 displays appropriately with no
  conversion.
• Some examples of queries that convert UTF-8 data
  to UTF-16 data are
• Bib Records Created by operator, data from
  bib_text.title_brief
• Item Status - Damaged, data from bib_text.title
• MFHD Count - Library of Congress classification,
  data from
• lcclass_vw.class
• all the Title List reports

87
Prepackaged MSAccess Reports

• Customers creating new queries or modifying
  existing queries must determine if the column
  they are referencing is UTF-8 encoded. If this is
  the case, they must include a conversion function
  (UTF-8 to UTF-16) to appropriately display the
  data.
•  
• Many of your customized reports will require
  modification if you want to see data in Unicode.
  Otherwise, your reports will look similar as
  before the upgrade.
• For a complete list of UTF-8 columns in the
  Voyager database see the Voyager Technical Users
  Guide.

88
Prepackaged MSAccess Reports

• Expr1 UTF8to16(TITLE)

89

• Endeavor Information Systems Overview
• Donald Muccino, Chief Operating Officer
• User Community Interactions and Opportunities
• Shelley Hostetler, Voyager Product Manager
• Voyager Unicode Release and Early Release
• Keeley Sorokti, Customer Support Manager
• Endeavor Product Update
• Shelley Hostetler, Voyager Product Manager
• Questions

90
Voyager Interlibrary Loan

• Voyager Interlibrary Loan is currently in the
  testing process with Kinetica Document Delivery.
• We plan to have a new Voyager ILL release
  delivering the KDD integration, available in Q2.

91
Voyager 5 Overview

• Increasing local circulation controls
• Improving WebVoyáge holdings display
• Easing workflows in Acquisitions
• Delivering results with precision searching
• Providing more flexibility in Bulk Import
• Introducing Media Bookings in WebVoyáge

92
Increasing local circulation controls

• Hold shelf life moved to matrix
• Hold Life and Recall Life moved to Circulation
  Happening location
• Maximum items borrowed by item type
• Globally
• Globally, by item type
• By policy group
• By policy group, by item type

93
Increasing local circulation controls

• Alerts at charge and discharge
• Link from discharge to patron record
• Alerts to exceptions at discharge
• Alerts at charge and discharge when patron has
  available items, fines, or demerits
• Control over display in FYI column
• Enhanced display of In Transit, On Hold items
• Where item was discharged
• When item was discharged
• Items destination

94
Increasing local circulation controls

• End user privacy
• Security for access to retained history in
  Circulation
• Batch job for deleting retained history
• Determine number of patrons retained
• Patron purge!
• Will be based on date
• Purge date OR Expire date

95
Improving WebVoyáge Holdings Display

• Serial Issue Presentation
• Display , group, and order components
• Display component name
• Control order display within a set of components
  attached to a single line item
• Order display within components
• Marc Holdings Data Display
• Coordinate, group, and display elements from the
  85x/86x holdings fields
• Exercise total control over display
• Delivered through XML/XSL architecture

96
Easing workflows in Acquisitions

• Complex Serial Prediction
• Prediction for normalized irregulars
• More combine/omit
• Issue-based
• Quick line item now available for
• invoices

97
Delivering Results with Precision Searching

• Ability to define individual keyword indexes on
  holdings records
• Available in staff clients
• Wildcards for left and internal truncation
• Headings keyword searches

98
Providing more flexibility in Bulk Import

• Replace/No add profile in duplicate detection
• Improved handling of suppression

99
Introducing Media Bookings in WebVoyáge

• Booking of items and/or equipment
• Includes patron information display

100
Digital Product Update

• LinkFinder Plus Subscription Service
• ENCompass 3.5

101
LinkFinderPlus Subscription Service

• LinkFinderPlus Subscription Service is
• An OpenURL-compliant link resolver
• Hosted by Endeavor at the same professionally-run
  hosting site that hosts ScienceDirect and
  LexisNexis providing 24x7 support
• LinkFinderPlus Subscription Service
• Links together disparate electronic resources
• Makes the research process faster and more
  efficient for the end-user
• Makes more use and better use of the librarys
  investments in electronic resources
• Increases the use of under-utilized electronic
  resources and helps users find full-text
  resources

102
LinkFinderPlus Subscription Service

• With a subscription service
• There is no need to purchase or re-purpose
  hardware
• There is no need to install and upgrade software
• No extra work for the IT staff

103
ENCompass 3.5

• Added functionality to existing features
• Expanding information in web
• Usability in staff client
• Deliver strategic functionality
• Learning management integration
• Additional gateways
• FAST search engine

104
Added Functionality in 3.5

• Expanding Information in the Web
• Searchable versus Clickable
• Context sensitive full text button
• Link to specific record in Voyager
• Usability in Staff client
• Multiple digital objects with single descriptive
  record
• Cascade delete for containers

105
Added Functionality in 3.5

• Add records to ENCompass repository via web form
• Linux development
• Unicode compliance
• EAD as single object

106
Course Content Integrator

• Why integrate learning management?
• Courseware of increasing importance
• Students view of resources shaped by courseware
  and campus portals
• Integrate traditional forms of research with new
  teaching methods
• Currently working with WebCT and Blackboard

107
Questions?