Simeon Warner to coordinate work on final report with Michelle
2020-09-25 - This is really happening now
Jason Kovari will discuss plan for DIscogs display implementation with LTS directors (note similar to use of external ToC data)
2020-09-18 - It is on the queue for LTS directors, expect to have something next week
2020-09-25 - Have introduced topic but more discussion required. (Relates a little to discussion of current work to index TOC data from a vendor)
Jason Kovari and Steven Folsom to explore where/how/if a discogs id might be added to MARC that would then be used in place of dynamic search to find a matching record (and coordinate with Tracey re. best practice). Would be used to override dynamic search
2020-09-25 - Tracey/Laura/Jason have been discussing and have proposed location. Steven has been doing some work on catalog numbers (aka publisher id) in music cataloging
Steven will create wiki page for this project and document cataloging decision
Huda Khan and Tim Worrall to discuss with Adam how work might be coordinated with D&A team
Huda Khan and Tim Worrall work to continue to explore the dashboard design and requirements
2020-09-25 in progress, will discuss with Astrid & Tim next week
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
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
What do we need to do before showing to D&A User Reps?
We are ready to demo. There is a particular UI style at present. Do we want to keep this or do we want to blend it more? Or do we separate it out as a different block?
Jason thinks that integration of Discogs data is less worrying that Wikidata might be. However, we can't speak to its quality and it is probably good to flag as external
Are there any API usage requirements around credit? Yes - there must be a notice and link
ACTION - Make sure the live demo meets the Discogs API terms of service in terms of linking and ack.
ACTION - Create mockup pages for the cases of 1) a completely blended presentation, and 2) a presentation where the Discogs data is separated out
ACTION - Huda to discuss with Adam having a meeting with User Reps sometime after Oct 5
Steven asks whether there should some presentation of Discogs data in the librarian view? This would help with debugging but is perhaps only important if we decided to go with seamless integration – Only think about this if blended view selected
Tracey had suggested some language pointing out what data is not used in search. For example, what if a user sees the record label in Discogs data and then tries searching on that (which they can't)?
ACTION - Tim to look into how we might display this
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.
Interest in the dashboard idea (full page for entity) that extends on the idea of an embedded knowledge panel
Discovery Affinity Group is looking at design ideas
Can we get Blacklight fork to not hit the production catalog every time we do a pull request? Not clear way to specify that all pull requests should go to the fork rather than the main branch from which you forked. Huda is investigating with input from Code4Lib inquiry
2020-09-11 so far there appears no way to fix this from within the github UI, will explore command line options
2020-09-25 Issues with Solr updates resolved, fixed deployment to see JavaScript files but still issues with images in assets directory (not sure of issue). VPN issue - try CUL VPN as opposed to CU?
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
2020-09-25 - Next meeting with ShareVDE will be next week (09-29) on how to access CKB, whether through cache or direct through ShareVDE API. API structure tentative. Trying to encourage them toward creating a QA compatible API, but even if they are compatible, there are some concerns about whether it will be performant.
2020-09-25 - Getting authority configurations from an external volume. Sensitive data is coming from .env. Greg is working on deployment to AWS using the latest changes. I am working on updating the deploy instructions.
Will be meeting this Monday and continuing work on developer user stories. Consistent participants include LC, OCLC, ISNI, ShareVDE, Mesh, Harvard, Stanford, and Cornell
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?
Developing Cornell's functional requirements in order to move toward linked data
What does success look like? And then how do we get there?
2020-09-25 Jason drafted an introduction for LTS staff and no capacity right now in LTS, perhaps discuss again next week as to what next steps will be. Jason and Steven will discuss this week
Other Topics
OCLC Linked Data / Entities Advisory Group
Discussion of comprehensiveness and accuracy, "Minimum Viable Entity". There was a presentation at DCMI
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
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-09-18 There is a final report from the Samvera group. Seems sensible to wait now until the github tools are available. Expected January 2021. Have changed default for new repos in ld4p to "main" https://github.com/organizations/LD4P/settings/repository-defaults
NEXT STEP - Use github tools January 2021
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)
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"