Versions Compared

Version Old Version 40 New Version 41
Changes made by

Kathleen Gerdink (Unlicensed)

Kathleen Gerdink (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • OLE DEMO (http://demo.ole.kuali.org/ole-demo/portal.jsp)
    • Use: the OLE DEMO drive to explore OLE and past OLE 0.3 and 0.6 coding for Search.
    • OLE 0.6 Milestone User Documentation / Drivers Manual to assist in reviewing coded search features.
    • OLE DEMO is refreshed biweekly.
    • OLE DEMO is used by the Board and FC for external demonstrations during conferences, to staff, and potential partners. We request that users stay out of the environment during these times on the OLE Demo Calendar
  • OLE TEST (http://tst.ole.kuali.org/ole-tst/portal.jsp)
    • Use:  the OLE TST drive to test and review progressive search development and coding in 0.8.
    • OLE TST code is promoted biweekly on Friday afternoons and will be unavailable to users.
    • Note: OLE-DEV and OLE-TST do NOT currently (6/29/12) have bulk Bib and Instance records for testing of Search services. Those will be persisted in July pending completion of OLE Instance v.9.
  • OLE Data Model & Fields
    • Use: While OLE stores the below Document Types in the DocumentStore, OLE also maintains a relational database to store transactional data, users, patrons, and maintenance tables.
    • To access Fields used in transactions (such as Purchase Orders, Loans), users may view the following from inside OLE TST or OLE DEMO:
      • Go to OLE Application, and select the Administration Tab
      • Select: "Functional Field Description Lookup". 
      • Users must select the appropriate Namespace (OLE-PURAP for acquisitions; OLE-VND, OLE-COA) and its Tab "component"- on which tab does field display?
      • Note: We are currently maintaining Rice 1 and Rice 2 data tables, and users must select the appropriate tool to access its tables (Acquisitions- Rice 1; Cataloging, Circulation, Licensing- Rice 2)
    • Alternatives:
      • Go to any transactional doc, and just find its basic display/label name on UI, and we can translate in future specs.
      • Install a database tool (such as free Oracle SQL Developer), and link to OLE tables (oracle.ole.kuali.org- contact Project Team or see Jenkins)
  • OLE Wiki, Document Types & Schemas
    • Use: use the wiki and its linked schemas to identify additional fields to be used in search design (fields, filters, sorts, facets, display)
    • OLE Bibliographic Documents - Docstore, Marc & Dublin Core
    • Bibliographic <Node metadata: DateUpload, DateLastUpdated. Future: FastAddFlag, Public, DateEntered?, CreateBy?>
    • OLE Instance- Docstore
    • Instance <Node Metadata: DateEntered, CreatedBy, LastUpdated, LastUpdatedBy, Harvestable, Status, SuppressFromPublic, FastAddFlag>
    • Item (availability) Status
    • OLE License Agreement
  • OLE Wiki: OLE Search Technical Documentation     
    • Use: To understand technical framework as coded so far for fields, facets, indexes, sorts, search logic and operators.
    • The wiki provides iterative documentation on the progress of Search coding, and docstore architecture with data model.
    • Doctypes & Formats:
      • Bib: Marc, Dublin Core (qualified, unqualified)
      • Instance
      • Licenses
      • Crosswalks used in Search fields/indexing
    • It provides an overview to coding in place for DocStore (federated) Search:
      • Available Search Fields
      • Available facets
      • Available Sorts
      • Search logic
      • NISO standards for sort (in progress)
    • It provides an overview of Transactional/Workflow searches completed or in progress for:
      • Acquisitions Search
      • Order Holding Queue
      • Receiving Queue
      • KFS/KNS Doc Search
      • KFS/KNS available fund/budget searches
      • Patron Search
      • Maintenance Docs/Lookups (searching & adding to controlled value selection lists)
      • License Agreement Search
      • Dup Check Match-Search used in Overlay & Ingest logic
  • OLE Jira, Master Search Executive OLE-1144
    • Use: To reference past functional documentation if more in-depth research or trouble-shooting required.
    • coding updates & original specifications (open, in-progress, testing, complete)
    • November/OLE 0.3 Search (initial Bib search, sorts, facets) OLE-1996
    • OLE 0.8 new/fixes in progress:

 

Anchor
field
field

OLE Search Fields, Facets, Sorts Summary

...

  1. SEE SEARCH FEATURES SURVEY/features options
  2. Date of Publication facets-
    1. what groupings/how
    2. 260$c versus control fields 008/07-10
  3. Source of Language code lists- need to document how HTC applied
  4. Framework: KNS Tx Search vs SOLR
  5. Extend or replace KFS/OLE Custom Doc Searches
  6. Normalization
  7. Edits to Instance Schema, fields?
  8. Authority records: linkages, search, NACO standards
  9. Call Number Browse (coming in OLE 0.8)
  10. Linked PO or Circ record from Item, and Order/Circ status (coming in OLE 0.8)
  11. Linked License Agreement (electronic journals etc)- in progress
  12. Search filters: Location, Format, Dates, Language, Record/Doc Status, Item Availability status,  TBA
  13. External Linked Data: Authority, or other stores
  14. Saved DocStore Searches (or user preferences)
  15. Wildcard behaviors
  16. Positional Operators
  17. Truncation
  18. Nested Search (more than one operator in same expression)
  19. Field/Marc tagging search
  20. Checkin, Checkout from Search
  21. Rice/KNS upgrades (future): search facets and other enhancements for transactional search
  22. Non-Roman Characters (ie, Chinese, Russian, etc)
  23. Docstore UI Design Components:
    1. Search UI 
    2. Search Fields
    3. Filters
    4. Sorts
    5. Facets
    6. Pagination
    7. Preferences
    8. Search Results UI
    9. Results view options
    10. Record display: brief, expanded, preview