Versions Compared

Old Version 1

changes.mady.by.user Simeon Warner

Saved on

compared with

New Version 2

changes.mady.by.user Simeon Warner

Saved on

Key

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

...

  • Enhanced Discovery - WHAM! (see also https://wiki.duraspace.org/x/sJI7Bg and https://github.com/LD4P/discovery/projects/1)
    • See: Organizing doc and Pseudonym thought. Updates also on running notes page
    • John set up a video demo for packaging approach. Figured out how to make a gem an engine that is included in Rails app alongside Blacklight. Gem can modify Blacklight's behavior. Can do whatever we want to modify how Blacklight works. Modification we want to make is to point BL's autosuggest feature to index being built by Huda and Tim. Modify BL's assumptions of how SOLR interacts with it
      • Autocomplete and Autosuggest in BL: Duke uses modifications to out-of-the-box. Stanford looked into this but landed on using a diff request handler (ie not built-in... but a separate search mechanism).
      • Since there are multiple examples of people wanting to use diff search index, endpoint, handler – this packaging would be welcome.
    • Slides about work for Discovery Affinity Group
    • Will regroup next week. Have index with examples of all the entities... and working UI code... and approach for packaging. Have additional possibilities to try index-only approach. Identify whether additional use cases need to be met. Identify whether we should integrate knowledge panel work. 
    • Also note that had conversation with Kevin (Usability Working Group) to assess usability testing with students.  Currently, not looking at testing with students so would need to do testing with staff.
    • Have a working demo!
  • Authority Lookups for Sinopia (Lookup infrastructure: https://github.com/LD4P/qa_server/projects/2, Authority requests: https://github.com/LD4P/qa_server/projects/1)
    • 2020-05-06 discussion where Astrid shared feedback about Sinopia and QA from catalogers at https://docs.google.com/document/d/14Sh2mBqkB2i9xml-Y7Aw-BGyvSAGwIS0I40jQXz88Pw/ . We note trade-offs between cached access and direct access in control/speed/scalability
    • 2020-05-15:
      • some things failing b/c tests are in-place before enough direction to Dave; not just Dave having to change indexing – need to instruct how to do so. Some are in index and available in QA that have not been instructed about what context we want / what we want to search.
      • ran 64 tests in last set.
        • 19 tests failed to find result at-all. severe failure
          • GeoNames interesting. Use same test for Direct and Cache and both fail. Perhaps need to rethink how we are looking for things. GeoNames keeps data separate (e.g.: New York and US are separate fields... cannot search for New York, US and get a result).
          • No failures are diacritics-related or special characters related (i.e.: hyphen and parentheses are both passing)
        • 3 failed to find result in the desired position (e.g.: not in results 1-5), not a severe failure.
        • 3 tests do not have a query... might be an issue with the input
        • Next step: look at tests to see if it is unique to authority of if the data is not there. Do we really expect these tests to work? Should be able to report on some next week. Steven will also work thru queue and ensure that this still reflects our priorities... while managing expectations around turn-around. If can get attention on queue, will also get attention on the tests.
        • When doing triage, there were 6 or so requests for authorities; two were transferred to Sinopia. A few others need to be investigated and followed-up
    • Discussion with Sinopia team around searching, following thread of a few weeks ago
      • spoke about indexing this week. Agreed that user testing needs to be done to determine best route forward. 
      • Lynette suggested: by default, could just do URI and label and, if cannot choose from that, select button for more context. OR have minimal context identified to have smaller amount of data passed around. Has UI impact for "select more context". Perhaps have extra-data option per-entity rather than per-search? User studies can determine best approach... but should not do this prior to Dave's work
  • LD4P3 Planning
  • Meetings (see LD4P2 Cornell Meeting Attendances)
  • Next meetings
    • ...