Skip to end of metadata
Go to start of metadata
NameInstitutionTitleEmail
Univ. of ChicagoSerials Cataloger@uchicago.edu
Larisa WalshUniv. of Chicago

Head of Metadata Management Services

@uchicago.edu

Texas A&M University

Assistant Professor. Serials Cataloging/Metadata Librarian

@library.tamu.edu
Texas A&M UniversityAssociate Professor, Catalogingcuaco@library.tamu.edu
NCSUAssociate Head, Acquisitions and Discovery (Monographs). Convener of the MM-SIGlkwhitte@ncsu.edu

Lisa McColl

LehighCataloging/Metadata Librarian

lim213@lehigh.edu

Index DataSoftware Engineer, DevOpswayne@indexdata.com
Index DataLead developer on Inventoryniels@indexdata.com
SamhaengUX Leadfilip@samhaeng.com
Index DataLibrarian. Analyst. PO the Inventory App

charlotte@indexdata.com

ZBWMetadata Librarianf.hemme@zbw.eu
Martina SchildtVZG, GöttingenSystems librarian, ERM, ACQMartina.Schildt@gbv.de

Uschi Klute

VZG, HamburgSystem &technical librarian, Circulationuschi.klute@gbv.de
U of Colorado BoulderSerials & e-Resources Cataloging ManagerLaura.Wright@colorado.edu
Jennifer EustisFive CollegesMetadata Librarianjeustis@umass.edu
Ann KardosUMass/Five CollegesMetadata Librarianannk@umass.edu
Jenn ColtCornellMetadata Operations Librarianjrc88@cornell.edu
Patty WanningerEBSCO

Nancy BurfordTexas A&M University

Five Colleges (Amherst)

University of AlabamaCoordinator of Metadatamalexand@ua.edu

Massoud M. ALShareef

KnowledgeWare Technologies Est.


The work group was decided established at the MM-SIG meeting held on 22/2/2018 (focus on Advanced search).

Changed scope:

  1. Search enhancement
    1. Slide deck https://docs.google.com/presentation/d/1Z3IgcTtBd5nb8ODOOMr5D_LLvOqo-_Udo7SwDOj1NyU/edit#slide=id.p
    2. Search enhancement filter in jira:
       

      T Key Summary Assignee Reporter P Status Resolution Created Updated Due
      Loading...
      Refresh


  2. Ability to search any field / subfield in instance metadata record, holding and item records - UXPROD-140

  3. Advanced search (later)

Purpose: 

The group will provide feed back, changes, suggestions, improvements etc. 

Commitment:

We expect the working group would need to meet 2-3 times to complete the work.

Documents:

  1. Search Patterns Discussion (Discuss post by Kimie OuYang)



Meetings:

First WG meeting: 3/14/2018 at 9-11 AM EST (link to the recording)

    1. Introduction by Filip
    2. Kimie presented her initial work on

1.Search with the Boolean operator

2.Filters

3.Multiple sources selection

4.Facets



c) The group will provide real life examples for Kimie to work on for the next meeting. The examples can be screen dumps from existing ILSes. Examples can be uploaded to the new subfolder called Advanced Search in the MM-SIG folder on Google drive.


MM-SIG meeting 6/6/2019:

Agenda:

  1. Status: 

               Slide deck - Inventory Search enhancement requirements - MM SIG WG 6_6_19

       2. To do 

                Review spreadsheet (WIP) - Search (UXPROD-140) Inventory Beta - Metadata Elements

       3. Plan work


Workgroup meeting 6/13/2019:

Agenda:

  1. Search-test 'fest' (log user search expectations)
  2. Review spreadsheet (WIP) - Search (UXPROD-140) Inventory Beta - Metadata Elements

  3. Review document (WIP) - Ability to search any element in Inventory (instance, holdings and item records) - UXPROD-140


Search and Sort session at F2F meeting in Washington 6/18/2019:

  1. Search-test 'fest' (log user search expectations)


  • No labels

2 Comments

  1. I would like to join the Search Enhancements / Advanced Search conversation.

    This is a very critical topic for the Arabic searching and retrieval capabilities in FOLIO. Arabic searching requires stripping off prefixes and suffixes letters from Arabic words before they get indexed, because those letters are connected to the word! For example, in English you write "The Book" where "The" and "Book" are two separate words, and when indexed only the "Book" is inserted in the index table and "The" is likely to be kept out since it is a stop word. In Arabic, "The Book" is written like this "Alkitab  الكتاب" which is compromised of two words: Al and Kitab, representing The and Book English. This means that there should be some mechanism to separate the "Kitab" word from its prefixing and/or suffixing letters first, so that only the core word gets indexed. There are more than ten prefixes like "Al" that can prefix an Arabic word, and sometimes they can go as many many as three prefixes proceeding a word. The same thing can be said about suffixes trailing Arabic words, which means they must be stripped off the Arabic word before they are indexed, so that when an Arabic word(s) is searched for, it will appear in the search results in all of its forms, proceeded and/or trailed by all prefixes or suffixes letters applicable to that word. 

    Based on our 20 years of experience with ILSs, such as Unicorn/Symphony and Koha, searching for Arabic words and phrases require a full text and retrieval engine (FTR) for these Arabic words to be handled properly. FTRs such as BRS (Unicorn/Symphony) or Solr (Sierra and VuFind) or Zebra (Koha) and now ElasticSearch (Koha), are popular in the library ILS business for long times. In fact, the only new addition in Sierra to differentiate it from Millennium is the addition Apache's Solr via Encore. Therefore, all new versions of the global ILSs are building their search and retrieval capabilities on FTR engines. 

    FTRs provide very easy way to define prefixes and suffixes letters, and infixes letters if needed, for a language using the Schema approach. We have been doing this with Solr and Elastic FTR for many years now, supporting DSpace IR, VuFind Federated Search and Discovery, and Koha ILS. To my knowledge, EBSCO EDS unique support of Arabic searching and retrieval is also due to the use of Apache's Solr. We look forward to see Solr and/or ElasticSearch readily integratable with FOLIO core indexing as an optional feature for libraries to use.   


    All the best,

    Massoud AlShareef 

    KnowledgeWare Technologies Est.

  2. Massoud M. ALShareef: Hello, and thank you for this perspective on searching needs.  I was looking at the UXPROD-1135 - Getting issue details... STATUS feature within the UXPROD-1045 - Getting issue details... STATUS epic and wondering if your comments are best included there so they are taken into consideration as that feature is worked into user stories that the developers will work on.