1 / 40

By Michele Newberry

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. Pending upgrade. Jumping 2 releases to v.18

ofira
Download Presentation

By Michele Newberry

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The FCLA Endeca Project By Michele Newberry

  2. M.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

  3. M.Newberry 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

  4. M.Newberry 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

  5. M.Newberry 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

  6. M.Newberry 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

  7. M.Newberry 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

  8. M.Newberry Basic Search

  9. M.Newberry Search Results

  10. A Closer Look at Facets

  11. Browse the Virtual Shelf

  12. M.Newberry Advanced Search

  13. M.Newberry Advanced Search

  14. M.Newberry Advanced Search

  15. M.Newberry Advanced Search

  16. M.Newberry Boolean Search

  17. M.Newberry A Closer Look at Results If item is requestable, displays request link Create RSS Feed for any result set Item status is dynamically displayed

  18. M.Newberry Export Options

  19. M.Newberry Patron Empowerment

  20. Patron Empowerment

  21. M.Newberry Full View with Holdings

  22. M.Newberry Full View with Holdings

  23. M.Newberry MARC View (Union)

  24. M.Newberry MARC View (Local)

  25. M.Newberry Monograph with many Holdings

  26. M.Newberry Monograph Holdings Full View

  27. Monograph Detailed Holdings

  28. M.Newberry Serial with many Holdings

  29. Serial Holdings Full View

  30. Serial Detailed Holdings

  31. M.Newberry Endeca Record

  32. Endeca Record (large record) …

  33. M.Newberry Endeca Record (large record) …

  34. Endeca Record (large record) …

  35. Endeca Record (large record) …

  36. M.Newberry Endeca Record (large record) …

  37. M.Newberry Next steps … • OPAC Subcommittee is examining • Data integrity • Functionality • Appearance • Usability • Accessibility • CIRC/ILL Subcommittee will be looking at future SUS-wide request capabilities

  38. M.Newberry 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

  39. M.Newberry 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

  40. M.Newberry 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

More Related