Date: 

Attendees: 

Regrets: 

Actions from 2020-10-16 Cornell LD4P3 Meeting notes

  • Jason Kovarito ask Tracey if she has the capacity to discuss librarian instruction at CUL re. possible use cases. Question had come up in the context of the dashboard use case "Instructional librarians want to teach users how to navigate library materials using subject headings.  Combined with Classification/LCSH taxonomy mapping"
    • 2020-10-23 Tracey is happy to help but wait until November
  • Greg Delisleto explore how to get the container version that Lynette has on her laptop up on AWS. Question about how to handle environment variables outside of the checked in docker container so that users can config
    • 2020-10-09 On laptop Lynette had an entrypoint script which worked fine to allocate assets and connect to mysql etc., this doesn't work on AWS. Lynette is trying to move these processes into the Docker file. Works for bundling but not for precompile, has some input from Justin, Greg will look into the DB connection. Some concern that we are having to make many changes for AWS, will the new version work on laptop or other VM? (changes so far do work on laptop too)
    • 2020-10-23 Greg has pulled Lynette's branch and had a quick look, will have more time next week. Lynette comments that the precompile is the key problem

Agenda

Discovery (WP3)

  • https://github.com/LD4P/discovery/projects/2 for issues etc. 
  • Preliminary draft of a discovery plan- intended to get feedback: https://docs.google.com/document/d/1zKYW7FQVVNvyd0XjjW0qWznX9PC3jbmOE6Kz_yygPjs/edit?usp=sharing
  • Strand 1: production piece (i.e.: picking features we've already worked on to then push those into production): discogs, autosuggest. Feature branches in the code to work on features in isolation. Still need to discuss discogs with Tracey (post- 9/2). Preliminary pass with discogs features using latest production (from a few days ago) successful (tried on dev vm and will try on ld4p3 demo using continuous integration later)
    • Steps:
      • Discussion with Tracey re. use case and benefit – DONE
      • LTS engagement re. metadata - DONE
      • Production requirements and functionality – Production decision points
      • Demo and discussion with D&A User Reps and dev team – DONE
      • Following up after user reps meeting
        • ACTION - Tim will sort out code in LD4P3 repo and look at adding button to highlight Discogs field next week
        • Steven notes possibility of generalizing the highlight button functionality to other external data, not currently in scope. Book covers come in dynamically through ISBN. ToC is being looked at for addition to index (so slightly different)
        • Tim hopes to demo to the User Reps on the Nov 5 meeting
  • Strand 2: research: how to go from knowledge graph to an index - what decisions are needed. What are the data sources for each (e.g.: how many Cornell faculty in wikidata)? Present: reviewing data sources and questions. Should have more worked out in a week or two. Main areas of concern: browsing and dashboard... and anything we can do to help patrons navigate our collections and how we can highlight an entity... and what does that mean for the index? How do we capture the relevant bits of the graph for an index? Is there a repo for this? Not yet... but can use discovery repo (https://github.com/ld4p/discovery) we already have to capture any queries or related work.
    • Research decision points
    • Use cases - first review 2020-09-18
      • Interest in the dashboard idea (full page for entity) that extends on the idea of an embedded knowledge panel
      • Goal of functional prototype for end of year
      • How will we test it? Remote testing would work but will students want/have-time to talk with us? Can we pay them?
    • Discovery Affinity Group is looking at design ideas
    • 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
      • 2020-10-23 Demo! Huda will continue to work on design elements for the dashboard, wondering about additional data connections, get to a sufficiently good prototype to start to get some feedback. Next Tuesday there will be a discussion in DAG of data connections to support particular user tasks
      • Steven notes Matt Miller work on connections between library authority work and wikidata, also PCC has wikidata pilot project which has some people creating wikidata entities and linking to them from MARC. Most work in special collections so generalization not always immediate

Linked-Data Authority Support (WP2) - A key element of this work package is a sustainable solution that others can deploy. Questions of budget for deployment. Need to get all code into LD4P repository. What would a good end-product look like both for our maintenance and for others to use

  • Qa Sinopia Collaboration
    • 2020-10-23  - Dave's new approach to indexing
    • 2020-10-23 Ongoing discussion with Sinopia team and SVDE folks about integrations. We are not yet clear about whether SVDE will provide a direct search API or appropriate incremental mechanisms for using Dave's cache
  • Cache Containerization Plan
    • 2020-10-23 - See notes above.
  • Search API Best Practices for Authoritative Data working group 
    • 2020-10-23
      • Next meeting - 2020-10-26
      • ACTION: Lynette needs to put together survey for cataloger user stories for PCC feedback and ranking by working group. 

        • Started.  Requested feedback on prioritization wording, but received no comments.

          EXAMPLE:
As a cataloger, I want to … a user story will go here…
 * REQUIRED - The system is unusable without the feature represented in the user story
 * HIGH USE - The feature represented by the user story would be used a lot.
 * NICE TO HAVE - The feature represented by the user story would be helpful, but the system is useful without it.
 * DON’T NEED - I do not expect to use the feature represented by the user story.
        • Suggestions:
          • Change from ranking to sorting.  Might be problematic with the number of user stories (> 20).  
          • Going to look into a combination approach where there are 5 bins sorting from High to Low and each bin has a limit on the number of allowed user stories.
  • From 2020-01-19 Sinopia call

Developing Cornell's functional requirements in order to move toward linked data

Other Topics

  • OCLC Linked Data / Entities Advisory Group
  • PCC Sinopia Profiles Working group
    • 2020-10-02 - Submitted interim report yesterday. Feedback requested before deciding on a few directions and working to stay compatible with LC work. Some discussion of how to align with SHARE-VDE data which uses a rather different profile. Committee is supposed to wrap by the end of October
    • 2020-10-23 Serials profile done, final report being written up, will be discussed at POCO next week, deadline in November 
  • PCC Task Group on Non-RDA Entities
    • 2020-10-09 Discussions of how reconcile RDA list with Non-RDA entities. Possible effects on id.loc.gov
    • 2020-10-23 Outline for final report done and will be assigning writing...
  • Default branch name - WAIT until we can use github tools January 2021

Upcoming meetings

    • SWIB
    • https://kula.journals.publicknowledgeproject.org/index.php/kula/announcement/view/1 .  Call for Proposals - Special Issue: "The Metadata Issue: Metadata as Knowledge".  Due January 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"

Next Meeting(s), anyone out?: 

  • ...

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.