Versions Compared

Old Version 4

changes.mady.by.user Huda Khan

Saved on

compared with

New Version Current

changes.mady.by.user Simeon Warner

Saved on

Key

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

...

Attendees: Huda, Tim, John, Steven, Lynette, Simeon, Jason

Regrets: 

Agenda & Notes

Review actions from 2020-06-12 Cornell LD4P2 Meeting notes

  • Steven Folsom - To work on prioritizing pending authority requests pending in the QA Issues
    • 2020-06-05 Still to do. Steven to review prioritization, then check in with Dave if there should be change in his work order
    • 2020-06-12 Still to do
    • 2020-06-22 Conclude that everyone is OK with what is happening, DONE 
  • John Skiles Skinner - To move the nectarguide code into the LD4P github organization
    • 2020-06-12 Still to do
    • 2020-06-22 DONE
  • Huda Khan - Schedule usability work. Will forward tasks draft to group and to Kevin/Usability Working group today
    • 2020-06-12 Met with Kevin and usability group on Monday. Agreement to do think-aloud and have reps interested in participating, might also get folks from access services. Plan to get tests done by June 25 giving time to create a report 
    • 2020-06-22 Three usability tests scheduled Monday + Tuesday
  • Huda Khan - To make slides and such to go through indexing approach, compared with client-side only, lessons learned, etc. 
    • 2020-06-12 slides, but not these slides yet
    • 2020-06-22 Started slides here
      • What about cases with many variants? All are added to the bucket field but only those matching the query are shown as `aka`
      • Why have a combined bucket field rather than searching multiple fields? Provides simple way to search although current implementation searches label and bucket fields to enable matches on the label to be boosted. Also the bucket field has special matching criteria such as start of word, which isn't the case for all fields we might be interested in

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
    • Updates from Dev chat meeting
    • Usability -  Document with testing plans. Slides with tasks and examples
    • Huda : Got to work on those other slides that explain indexing. (To Do above). Will also check errors at the Solr level which means errors when trying to ingest Solr documents generated by the indexing processing scripts. 
    • Tim did work to update for index changes and some code consolidation from JS to controller, will now get back to the tests
    • worked in incorporating knowledge panels for people/subject/etc. – demo
      • Note descriptions from wikidata are added to authors for example to help disambiguate. What is the description is very long? Current UI would expand width and then wrap as necessary? They seem mostly to be fairly short but we might want to force truncation for something that is long
    • Tim worked on rspec tests, now completed and pushed into dev
    • John worked on packaging, is moving Tim's code into nectarguide. Have decide not to adopt to use twitter typeahead but instead a more direct moveJohn has been porting Tim's work into Blacklight. Hoping to maintain the same experience but some things might change a little using native Blacklight features
  • Authority Lookups for Sinopia (Lookup infrastructure: https://github.com/LD4P/qa_server/projects/2, Authority requests: https://github.com/LD4P/qa_server/projects/1)
    • QA performance
      • 2020-05-22 Dave is working through LoC authorities with new caching scheme, expect to hear about now
      • 2020-06-12 Taking a back seat to accuracy work
    • QA accuracy
      • 2020-06-12
    • Lynette has mostly been focusing on exhibits. Dave is working on performance improvements to eliminate SPARQL quest after matches for LOC. Still have Steven's additional tests, want to see how capitalization tests work and should have same results – hope to get these set up this week
  • Linked Data API Working Group
    • Starting first Monday in June and then every other week for 4 months, logistics put into place
    • 2020-05-29 - Added initial working group documents...
    • 2020-06-05
      • First meeting is next Monday
    • 2020-06-12
      • First meeting was last Monday (meeting notes).  Brainstorming fell into several categories of topics: Caching (and management of cached data), Reconciliation, Accuracy (of results and of selection) (including extended context and ordering of results), API Approach, Data Structure, Scalability.  
      • Creating a list of terminology with definitions.  Discussions happening in Slack about terminology definitions including a question about the definitions for Reconciliation and Entity Resolution.  I used definitions that were used in the first LD4L workshop which defined Reconciliation connecting Things-to-Things and Entity Resolution as connecting Strings-to-Things, but it was suggested that these are actually the same thing.
    • Second meeting today - focus on use cases, so far Lynette has added one
  • LD4P3 Planning
    • Stanford functional requirements document: https://docs.google.com/document/d/18H6zYGwKuCg3SZqm9Q_cxkZThcdmBjknE6HdtQ-RRzk/edit#heading=h.4fu64x8jzm6e
      • Possible relationship to entity management work in FOLIO
      • How much full LD vs linky-MARC?
      • CUL LTS working group is hoping to add URIs to MARC before FOLIO migration as a substitute for some of the heading management we do in Voyager in other ways. Perhaps won't be done ahead of switch but as part of the data migration. Considering how to update/maintain going forward
      • 2020-06-05 Agree that doing some analysis/write-up for the Cornell context would be good, ACTION for July
    • Greg has been working on setting up a copy of Cornell Blacklight
  • Meetings (see LD4P2 Cornell Meeting Attendances)
  • Next meetings
    • ...Organize wrap-up on 30 June