Versions Compared

Old Version 9

changes.mady.by.user E. Lynette Rayle

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.

...

    • 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 – See actions above from last week
          • Have branch with discogs code on dev VM and demo server from LD4P fork, but still issues with the assets folder under Rails not showing current version (these are generally copied in during the Rails deploy process)
    • 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
      • Dashboard design meeting kickoff notes - will also try to understand what our data will support or connections to other data sources
  • 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-02
        • Meeting with ShareVDE this week (09-29).  ShareVDE will provide download for CKB and Dave will cache.  Dave plans to do a combined search index for all institution data.  There was a discussion on change management for CKB.  I provided them with documentation on issues related to Change Management.
        • Discussed direct access but that doesn't look possible because of API and performance, so Dave needs to cache
        • Added local authorities for property_type and property_attribute per request from Sinopia dev team.  Released on production (per links)
        • Open request to add small authorities from LC. Dave is adding to cache and Lynette will then add config to QA
    • Cache Containerization Plan
      • 2020-10-02 - Greg is working on deploying on AWS.
    • Search API Best Practices for Authoritative Data working group is still working through use cases, this seems very important to take sufficient time
      • 2020-10-02
        • Met last Monday.  Continuing work on developer user stories.  Wikidata participated in the conversation.
        • Need to get contact information from Steven to share with PCC.  Looking at creating a survey that will allow for prioritization by PCC and the working group.  Should the user stories for PCC only be the cataloger user stories?
          • Steven thinks we should go ahead with the cataloger use cases for PCC
          • ACTION - channel communication the Steven when Lynette has written up the use cases and created a survey for cataloger use cases
          • Developer use cases will have wider audience but still want to include PCC
  • Developing Cornell's functional requirements in order to move toward linked data
  • Other Topics
    • OCLC Linked Data / Entities Advisory Group
      • OCLC has described minimal viable entities and a number of small vocabs – are these new "standards" that we will have to engage with to ensure alignment?
    • PCC Sinopia Profiles Working group
      • 2020-09-18 - Still going through large spreadsheet comparing Sinopia profiles with BSR and CSR, close to having a comparison, will be part of report to POCO, still on target to complete in October
      • 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
    • PCC Task Group on Non-RDA Entities
      • 2020-09-11 - Preliminary report went to POCO suggesting a small vocabulary of entity types, discussion about how to host/implement
      • 2020-09-25 Now have a short list if possibilities and close to decision
      • 2020-10-02 Have definitions of short listm
      ld4l.org website - 
  • Default branch name
  • Upcoming meetings
    • LD4P(2/3) update for CUL-IT all-staff
      • Who/what? - Huda notes conflict with Blacklight summit
    • Virtual Blacklight Summit in early October. (Main site link and document to add lightning talk/breakout session ideas) - Huda is on unofficial committee. Expecting various follow-ons from earlier meeting this year. (Discussions still in progress and, at some point, draft program will be shared with the community). 
      • Agenda and registration link have gone out. Will be intro workshop, time for lightning talks and longer sessions. Sessions for plugin discussion including call-number browse
    • European BIBFRAME Summit; registration now open. Occurring 9/22-9/23 (9-11:30am Eastern each day): http://www.casalini.it/bfwe2020/ (no cost)
      • Steven talked on the panel in the second day
      • Some chat drama about RWOs...
      • Lots of questions about community process (some of which PCC is now dealing with)
    • 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"

...