Page History

...

Attendees: Lynette, Greg, Huda, Simeon

Regrets: Tim, Steven, Jason

Last meeting: 2021-02-19 Cornell LD4P3 Meeting notes

...

• https://github.com/LD4P/discovery/projects/2 for issues etc. 
• Draft of a discovery plan: https://docs.google.com/document/d/1zKYW7FQVVNvyd0XjjW0qWznX9PC3jbmOE6Kz_yygPjs/edit?usp=sharing
• Strand 1: production piece 
  • Production requirements and functionality – Production decision points
  • Discogs data use - in production since January 2021
    
    • ACTION (after March D&A sprint) - Tim to follow up on implementation and look at data from tracking use of the Discogs
    • ACTION (during March D&A sprint): Tim Worrall will raise usability testing for D&A queue (don't carry forward in notes as now outside of LD4P)
•  Strand 2: research: how to go from knowledge graph to an index
  • Research decision points, Use cases 
  • First goal: DASH! dashboard (full page for entity) that extends on the idea of an embedded knowledge panel, aim to have functional prototype for end of year
  • DASH! (Displaying Authorities Seamlessly Here)
    • Dashboard design meeting kickoff notes - will also try to understand what our data will support or connections to other data sources
    • https://docs.google.com/document/d/1PgQi3xobsPhr9DUHU_YGeimL1OjNiiTdkiNWb36r3Gg/edit
    • 2021-01-29: Huda working to get scripts in place to populate index; bringing in period-O info; focused on locations with Wikidata URIs for consistency. Subject headings: script that takes-in components & breaks those out... and parses into timeline info. On Dave's fuseki, 34 distinct temporal terms with labels. Will finish today with actual index. Will break-down the loading to increase load speed
      • ACTION ITEM: adding Wikidata URIs for any subject headings and broader/narrower URIs to index (today) - DONE for dev VM index, to do next for LD4P3 Solr index (will be done still today). Can be marked done after.
        
        • 2021-02-12 Each LCSH now has a Wikidata URI where available, broader and narrower URIs where available, periodO extracted spatial URIs and time periods where available, a list of components for multi-part subject headings with URIs and labels for each component, separate lists for temporal components with start and end times mapped, and geographic components with LCSH URIs and equivalent Wikidata URIs extracted and added. 
          • One error (for review perhaps later): two of the LCSH temporal component labels have special characters and are not being matched
        •  20212021-02-19: Kicked off script, will mark when done but not done yet.26: DONE - One script relies on SPARQL queries against Fuseki and took about 5h on dev ad data copied to production
      • Reached out to IRB to ask about testing: if we want to disseminate results as research data, need to do IRB protocol; has a follow-up. Waiting to hear back but will submit protocol if no word. Simeon's interpretation of reply is that we are crossing line into research and the approval will likely be positive. Depending on how we describe what we're doing it either falls under research OR improving a product... but we're essentially doing research to improve a product so yes to IRB review.
        • ACTION ITEM: IRB did respond and say they wish us to proceed with sending in an application.  Huda will work on this and reach out with any questions if needed.
          
          • 2021-02-19 DONE. IRB application submitted.26 After some discussion and clarification there remain to submit details of consent forms, addition of potential interview and focus group questions, de-identification data, and compensation information
    • 2021-02-19 Tim has been working on entity page. Notes a number of issues with the Historopedia timeline such as items with same date being hidden, but performance is good.
  • 2021-02-05
    • What would D&A user reps favor?
      • Concern that full KP linked from button is too much
      • Is "KP-lite" on autosuggest a good route? We think users would find this valuable. Are there options that minimize index changes? 
      • What warrants a KP?
      • What is the redundancy between KP work and DASH!? Does dashboard mean a fundamental change or is just an enhanced KP?
      • We need to be aware of which options require significant indexing changes. There is already a sense that we want to add ids to the index
      • What about the open syllabus project? This relied on the open syllabus API, not sure whether it is available in LD. Essentially a mapping from domain→CSIP codes→ ISBN, very few wikidata connections
    • What would be the smoothest next step for production?
    • Which option would give us real linked data connections via URI?
    • Steven notes that LTS authorities in FOLIO group is looking at the insertion of URIs into MARC records (resources willing)
    • ACTION - Huda Khan Tim Worrall document options and implications as preparation for user reps presentation in order to get a steer on where to continue experimentation with a view to future implementation
      • Dashboard (perhaps for some entity types only)
      • Autosuggest with KP-lite
      • Regular facet with KP
      • Open syllabus related items
      • Brainstorming notes
      • 2021-02-12 Agreement that streamlined KP is a good starting point, with possibility of later extension to a full dashboard. Autosuggest and open syllabus good alternative options. 
    • ACTION - Huda Khan to line up meeting with D&A user reps
      
      • 2021-02-12 Ready to set up meeting2021-02-19 Sense 26 Understanding that we shouldn't burden the D&A user reps at this point
  • Tim working on the author panel and  timeline, will continue working on this next week. Also spent time on graphical representation of influenced-by and influence-for. Steven thinks that the lists of results may be ordered by some sense of strength, so perhaps top results are useful
  • • • aren't going to be asking for review of anything to be deployed before the FOLIO go-live. Not yet clear whether the user reps will have time to provide us with any guidance for ongoing development work before the summer
  • Tim on ESMIS for next weeks, Huda working on IRB and also looking at dashboard with new version of historopedia which is much faster. Huda also looking at avenues for recruitment, have found out about student worker lists for Olin and for Mann, and grad carrel users list
  • Planning for discovery work
    • Work so far has focused on authorities and what we can do in catalog
    • How might we use BF modeling and data from SVDE? At DOG meeting on Monday there was discussion, also similar discussions in DAG about specific use of modeling
    Tim on ESMIS next two weeks, Huda will work on tasks for user tests and perhaps pilot test with the team (pending IRB approval). Open questions about how to recruit students right now - perhaps talk to usability WG 

Linked-Data Authority Support (WP2)

...