...
- 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 Discogs code is in production!
- ACTION: Tim will speak to Melissa about tracking for the Discogs link.
- 2021-02-05 Still need to follow up with Melissa
- 2021-02-12 Had discussion with Melissa and now Tim will create a issue for the March D&A sprint. Followup will be to track that this gets done
- 2021-02-05 Still need to follow up with Melissa
- ACTION: 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
- 2021-02-12 Started text (as in copied Steven's content). In progress. Will send out draft text today. Also discussed in DOG meeting on Monday with useful feedback
- Steven notes LD discussion where he was asked about how external data is acknowledged and shared with the group how we do it on D&A. Miel Vander Sande:
Widget Connector url https://twitter.com/miel_vds/status/1359781757000818690?s=21
- 2021-01-29 Discogs code is in production!
- 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 still today). Can be marked done after.
- 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.
- 2021-02-12 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.
- Done. IRB application submitted.
- 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.
- 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 still today). Can be marked done after.
- 2021-02-05: 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? We think users would find this valuable. Are there options that minimize index changes?
- 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?
- We need to be aware of which options require significant indexing changes. There is already a sense that we want to add ids to the index
- What about the open syllabus project? This relied on the open syllabus API, not sure whether it is available in LD. Essentially a mapping from domain→CSIP codes→ ISBN, very few wikidata connections
- Concern that full KP linked from
- What would be the smoothest next step for production?
- Which option would give us real linked data connections via URI?
- Steven notes that LTS authorities in FOLIO group is looking at the insertion of URIs into MARC records (resources willing)
- ACTION - Huda Khan Tim Worrall document options and implications as preparation for user reps presentation in order to get a steer on where to continue experimentation with a view to future implementation
- Dashboard (perhaps for some entity types only)
- Autosuggest with KP-lite
- Regular facet with KP
- Open syllabus related items
- Brainstorming notes
- ACTION - Huda Khan to line up meeting with D&A user reps
- What would D&A user reps favor?
...
- Qa Sinopia Collaboration – Support and evolve QA+cache instance for use with QA
- 2021-02-05: Met with Stanford. The discussion focused on closing the loop to get ShareVDE data into Sinopia. Specifically, this is data derived from Stanford catalogers submitting RDF translated from their MARC data that was submitted to ShareVDE. The plan is for Stanford to take the lead to establish connections with ShareVDE to start up meetings focused on this topic. We documented questions in meeting notes.12:2021-02-12:
- Dave, Steven, and I met to review the status of issues related to the indexing approach. 4 were closed (returning too many results, newline issue, all tests passing for geonames and ligatus). 2 more will likely be closed today (accuracy tests for locgenres and locnames). 4 others are under active exploration by Dave (getty looking for subject to end with -place
- and -agent, some subauths not returning any results, mesh hierarchy and description issues). 5 other issues awaiting closing of the current set under exploration. Some may be fixed by the current set of issues.
- Vivian at Stanford sent email to Anna at ShareVDE to restart discussions about moving data round trip from Sinopia to ShareVDE, form Stanford's MARC converted records to ShareVDE, from ShareVDE to Sinopia, and direct access to ShareVDE through QA.
- Michelle announced the release of ShareVDE's PCC data. They are provided as downloaded data, not direct access to ShareVDE. Dave is reviewing for import to the cache.
- 2021-02-05: Met with Stanford. The discussion focused on closing the loop to get ShareVDE data into Sinopia. Specifically, this is data derived from Stanford catalogers submitting RDF translated from their MARC data that was submitted to ShareVDE. The plan is for Stanford to take the lead to establish connections with ShareVDE to start up meetings focused on this topic. We documented questions in meeting notes.12:2021-02-12:
- Cache Containerization Plan - Develop a sustainable solution that others can deploy
- 2021-02-05 Greg says "I've finished expanding the CloudFormation template to include a container service, which will make the container much more useful to adopters. There are still several steps which are not automatic, involving networking and security groups, and making those automatic will require the template to create the cluster of machines that the whole thing runs on. That will be super nice, but it will be a pretty big expansion of the template."
- Search API Best Practices for Authoritative Data working group
- 2021-02-05 Met again on Monday, some small refinements (advance search and filter are interconnected). Expecting to get review finished by today.
- ACTIONSteven Folsom will send document to PCC
- ACTION E. Lynette Rayle will send announcement to Samvera and put a note on #general, also link from main LD4P page.
- 2021-02-12:
- The summary document is almost complete. There is one question about the wording around broader and narrower terms and related user stories. I am adding in an introduction that describes the working group and defines the 3 perspectives for catalogers, developers, and providers.
- Began writing the announcement that Steven and I can use for the various communities.
Developing Cornell's functional requirements in order to move toward linked data
...