Transcript Slide 1
The FCLA Endeca Project By Michele Newberry Why ENDECA? Already proven by NCSU Build on NCSU’s work instead of starting from zero Product features: Guided navigation Facets Spellcheck Stemming Others yet to be fully explored M.Newberry 2 Pending upgrade Jumping 2 releases to v.18 None of the 15.5 customization will survive the upgrade process Resource commitment to sustain level of customization is low Familiarity with previous system is declining Upgrade process will take 4 months for the 11 Aleph instances M.Newberry 3 Other objectives Provide a consistent transition interface during the upgrade process Gain discovery and navigation functionality not currently available Gain a union catalog – a byproduct of our previous system not yet available with the current one M.Newberry 4 Endeca architecture One instance of Endeca One Endeca database 7 million records One instance of user interface with individual institution views Easy interface modification Rapid, iterative development M.Newberry 5 Building the Endeca File Extract bib records with 852 fields from 11 Aleph databases Load 1st into 12th Aleph bib file (UX) Load 2nd file-deduping on OCLC number – merge unique and local data (e.g., 852/856/headings/notes…) Load file3 … file11 Load Digital Library metadata Extract UX bib file to load into Endeca M.Newberry 6 Building the Endeca Catalog Full extraction, reformatting and load takes 48 hours – will be done every few weeks Incremental updates of adds/significant changes Current holdings status retrieved from Aleph via SQL in real-time M.Newberry 7 Basic Search M.Newberry 8 Search Results M.Newberry 9 A Closer Look at Facets Browse the Virtual Shelf Advanced Search M.Newberry 12 Advanced Search M.Newberry 13 Advanced Search M.Newberry 14 Advanced Search M.Newberry 15 Boolean Search M.Newberry 16 A Closer Look at Results If item is requestable, displays request link Create RSS Feed for any result set Item status is dynamically displayed M.Newberry 17 Export Options M.Newberry 18 Patron Empowerment M.Newberry 19 Patron Empowerment Full View with Holdings M.Newberry 21 Full View with Holdings M.Newberry 22 MARC View (Union) M.Newberry 23 MARC View (Local) M.Newberry 24 Monograph with many Holdings M.Newberry 25 Monograph Holdings Full View M.Newberry 26 Monograph Detailed Holdings Serial with many Holdings M.Newberry 28 Serial Holdings Full View 29 Serial Detailed Holdings 30 Endeca Record M.Newberry 31 Endeca Record (large record) … Endeca Record (large record) … M.Newberry 33 Endeca Record (large record) … Endeca Record (large record) … Endeca Record (large record) … M.Newberry 36 Next steps … OPAC Subcommittee is examining Data integrity Functionality Appearance Usability Accessibility CIRC/ILL Subcommittee will be looking at future SUS-wide request capabilities M.Newberry 37 Next steps … Technical Services Planning Committee is looking at: Aleph indexing changes for v.18 and the effect on Endeca Examining use of material type codes for more user-friendly results Processes to optimize the consistency of the bibliographic and holdings data feeding into Endeca M.Newberry 38 Much further down the road Technical Services Planning Committee will be looking at Feasibility of sharing bibliographic records to: Reduce duplication of effort Share authority control Redirect resources into enhancing the data Reduce level of effort to produce the Endeca database M.Newberry 39 READY … FIRE … AIM!!! http://catalog.fcla.edu http://famu.catalog.fcla.edu http://fau.catalog.fcla.edu http://fgcu.catalog.fcla.edu http://fiu.catalog.fcla.edu http://fsu.catalog.fcla.edu http://ncf.catalog.fcla.edu http://ucf.catalog.fcla.edu http://uf.catalog.fcla.edu http://unf.catalog.fcla.edu http://usf.catalog.fcla.edu http://uwf.catalog.fcla.edu M.Newberry 40