Versions Compared

Key

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

...

  • E. Lynette Rayle QA performance
    • 2020-04-24 Lynette did an analysis of performance to try to understand whether speed is clearly related to data size or complexity of extended context. Result are that there isn't clear correlation. Tried to parallelize parts of QA and in some places saw slowdown, one place found speed improvement where the complexity is high. However, in the complex cases the times are often still rather long (0.5–2s) but not markedly longer than somewhat less complex queries. Still the worst cases are because of the retrieve time from Dave's cache, he is looking at why CERL is slow when we might not expect it to be. Unfortunately no clear path to improving everything from the QA side: Lynette will try to understand why the OCLCFAST graph load is so slow.
    • 2020-05-15: Dave still working on performance. Reported accuracy results earlier this week. Steven input more tests... will run these in 15 and report then.
    • 2020-05-22 Dave is working through LoC authorities with new caching scheme, expect to hear about now
  • E. Lynette Rayle  to set up best practices working group around linked data APIs for authorities → documenting on Linked Data API Best Practices for Authoritative Data Working Group
    • 2020-05-15: Starting first Monday in June and then every other week for 4 months, logistics put into place. Slack channel. Pointed toward Lyrasis to sign-up. Meeting invite for all meetings. People are responding on invite

Status updates and planning

  • 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
    • Huda set up Solr index on personal dev vm to use solr configuration and schema modifications to mirror suggest index and try out pseudonym/see also solutions and update indexing process scripts. 
    • Tim working on RSpec tests to evaluate if autocomplete behaves as expected based on original set of use cases.
    • John set up version of gem (called "Nectar Guide") that now connects to Huda's dev VM Solr index to test out connection to separate Solr search index and display of info. 
    • Additional next steps: 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 – want to have ideas by June 8 Usability WG meeting, then decide on plan to do some tests (through UWG or not) by end of June.
    • 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)
    • Have worked on CERL issues with Sinopia that will be released soon, otherwise mostly working on Exhibits
  • Linked Data API Working Group
    • Starting first Monday in June and then every other week for 4 months, logistics put into place
    • 2020-05-22 - Doing pre-work for WG start
    • 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
    • ...