Versions Compared

Key

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

Attendees: Brian, Laura, Kimberly, Charlotte, Natasha, Magda

Note-taker:  Brian Clark

Recording: https://vod.video.cornell.edu/media/Inventory+Search+Improvements+Working+Group/1_31kobatg

Agenda:


Notes:

Uses cases reviewed:

  1. Use cases added by Laura
    1. Charlotte: A broader perspective on use cases is important, not just catalogers. Will ask the RM working group for feedback.
    2. Natascha: It is important how the results list displays. Not just list of bibs
    3. These kinds of comments can be added to the notes column on the search improvements uses cases table.
      1. Laura: Added separate column: expected data on the results list
  2. Questions on what was already added to the search improvements table:
    1. Searching by resource title/alternate title: would you like to be able to specify title all/alternate title?
      1. Laura: In most cases we want title all, but in some cases we want alternate title with a specific type (i.e., uniform title)
      2. Charlotte: Identify any alternative title type and see if it was applied consistently?
        1. Laura: I have never wanted to do that. Do want to be able to search for an exact phrase for title all/alternate/series. Especially important for acquisitions
          1. Exact search implemented on back end, but not available through UI
      3. Magda: Do you want to be able to search specifically by resource title? There is no way to search instance title except by title all.
        1. Laura: Not by resource title, but definitely by alternative title (i.e. uniform)
        2. Natascha: Agree. Except in some cases, we would prefer for it be bunched together. We would maybe expect results to be sorted alphabetically, but that doesn’t seem to be happening
        3. Charlotte: In UI group, we are talking about an action window for sorting
        4. Magda: In Elastic Search, by default, ordering is by rank relevance, but can be sorted alphabetically
          1. Charlotte: This should be fixed when working on bugs. Order by index title
          2. Laura: Default sort would be determined by kind of sort. I.e., if searching by call number, search should be sorted on call number
    2. Resource title has same weight as alternative title. Is this not wanted?
      1. This sounds like what we want. Don’t want to have to know variations of title to be able to find resource on list. i.e., time.
      2. Magda: I believe this is the default. The algorithm takes into account frequency of word
      3. Magda: What about alternative titles?
      4. Kimberly: I think I would just use title all
      5. Magda: So only uniform title would be of interest
      6. Laura: Combining uniform title and contributor is especially important to catalogers
    3. Instance – contributor: would inverted names be an issue?
      1. John Steinbeck; Steinbeck, John, etc.
      2. Use cases needed.
      3. Laura: Should be able to accommodate both
      4. Sort order default would be index title if more than one contributor found
    4. Magda: Please continue adding use cases