Page History

...

• 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
  • Implementation work
    
    • 2021-01-29: In Production - DONE
      • Assessment: outside of LD4P; consider engaging D&A group with usability testing and/or user feedback. For browse, melissa put in some tracking to monitor user interaction with browse. can we do something similar with Discogs (e.g.: are people clicking the highlight link and/or the link to get to discogs? What have we learned from virtual shelf browse tracking
        
      • ACTION ITEM: Tim will speak to Melissa about tracking for the Discogs link. 
        • 2021-02-05 Still need to follow up with Melissa DONE (2021-02-05)
          
      • ACTION ITEM: Tim Worrall will raise usability testing for D&A queue (don't carry forward in notes as now outside of LD4P)
        • 2021-02-05 This won't happen until the next sprint, starting second week of March
      • ACTION Huda Khan Tim Worrall Steven Folsom to develop a post for #general, #discovery and partners email about Discogs going live
•  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 today)
        
        • 2/5/21: Dev VM index populated with the content above using a script that will be reused for populating the LDP43 discovery solr index.
        • 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
      • 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-01-29: Next piece to go into production? discuss in Discovery on the Ground and then here
    • For reference:  Use Cases and production idea discussion
    • Tim was looking to reuse some of the ajax calls Huda did for knowledge panel; reworking portions of HTML but focused on getting LoC URI and calling wikidata. making good progress. Considering layout and not duplicating what we already have in catalog. Working on authors/subjects. Wants another week to work on this
  • 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?
      • 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?
    • What would be the smoothest next step for production?
    • Which option would give us real linked data connections via URI?

Linked-Data Authority Support (WP2)

...

• https://kula.uvic.ca/index.php/kula/announcement/view/1 .  Call for Proposals - Special Issue: "The Metadata Issue: Metadata as Knowledge".  Due January 31, 2021 (abstract 300-500 words).  Includes "The use of linked open data to facilitate the interaction between metadata and bodies of knowledge" and "Cultural heritage organization (libraries, archives, galleries, and museums) and academic projects that contribute to or leverage open knowledge platforms such as Wikidata"
  
  • Folder Link, CFP + Brainstorming
  • 2021-02-05 Huda submitted abstract
• code4lib - virtual next year
  • Expecting to attend: Huda, Steven, Lynette
• Lynette doing a QA presentation at Samvera partner call in June
• Mann  All-Staff : Huda (Dashboard), Tim (Discogs) and Lynette (QA) presenting next Wednesday at Mann All-Hands meeting (2/7)
  • Done, positive feedback
  • Chat comments about dashboard, questions about how that works for e-resources. Jason thinks that for journals we donmay have good data but the subjects will be higher-level unless the journal is very focused - but won't have much information in the catalog, and no article data that we can manipulate. For e-books there are options and we might consider at-scale enhancement perhaps with connection to physical book

...