Versions Compared

Old Version 7

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)
          • Update 10/9/2020: Manually cleared out the assets folder on the two rails servers and ran Jenkins deploy more than once and saw only one copy of the files, so hopefully this is fine now.  Will keep an eye on the assets folders.   
          • How do we run the demo meeting next week? Simeon intro mention demo and mockups of alternatives, turn over to Steven to mention catalog override and then demo from Tim
    • 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)
  • 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-09
        • Had a meeting with ShareVDE this week.  I provided them with the API doc I put together last year.  We discussed issues related to Change Management more and I offered to have discussions with them and Dave about how best to do this. In related work the Sinopia team provided sample records which SVDE will do a trial ingest with to understand any data changes from round trip. Sinopia team now off work cycle until perhaps Jan 2021.  Next meeting with ShareVDE is Tues, Oct 20.

        • Added LC small vocabs to cache and through QA (example: carriers q=audio).  They have requested the ability to get all terms for vocabs that are super short.  My plan is to add a config for {terms: allowed=true | false}.  Most linked data authorities should not have this because there are hundreds of thousands of term, so it will default to false.  This requires changes minimally at the QA level and possibly at the qa_server level as well.  QA does support fetch all terms for some non-linked data authorities already, so the infrastructure to handle this is already there.

        • Dave has now released most authorities under new index scheme. Lynette is doing a before/after analysis with accuracy tests
    • Cache Containerization Plan
      • 2020-10-09 -Update under action items.
    • Search API Best Practices for Authoritative Data working group 
      • 2020-10-09
        • Working through developer user stories.  Next meeting is next Monday.
        • ACTION: Lynette needs to put together survey for cataloger user stories for PCC feedback and ranking by working group. 
  • 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
      • 2020-10-09 Almost done, questions about role of item template which doesn't fall within PCC scope
    • 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 lists, now creating MARC examples. Interest is working the German national library on alignment – perhaps influence that and then adopt instead of creating a new list
      • 2020-10-09 Discussions of how reconcile RDA list with Non-RDA entities. Possible effects on id.loc.gov
  • Default branch name - WAIT until we can use github tools January 2021
  • Upcoming meetings
    • 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
      • Pre conf workshop Tuesday on blacklight customization (4h on zoom!), continuing with 2h/day
      • Huda gavgave talk on Blacklight and linked data
    • 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?: 

  • ...2020-10-16 - Steven out