...
- 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
- 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
- Implementation work
Following up after user reps meeting- New demo to User Reps 2020-11-06 Didn't manage to get demo for User Reps on Nov 5 due to other pressures. Still making some tweaks to the layout and highlighting
- Question of using QA vs going directly - will use Discogs directly for now to avoid adding QA
- Will do demo next Friday for User Reps
- Assuming User Reps approve to move forward, will plan to move code into LD4, add issues as part of D&A to add tests. Expect to deploy as part of January D&A sprint
- 2020-11-20 Tracey has provided examples of bib records with 024 $2 discogs for Frances and Tim to test out their code. Tim asked a great question about how much data we can expect in the bib from Discogs if the Discogs id is in the bib. This has prompted me to reach out to Tracey to establish local a policy for deciding what data is essential to include in the MARC record in order for it to be able to stand alone, and what can catalogers get away with not copying and pasting (and let Discogs feature pull in automatically).
- Steps:
- Strand 2: research: how to go from knowledge graph to an index
- Research decision points
- Use cases - first review 2020-09-18
- 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
- 2020-11-06
- Huda has continued work on dashboard page, discussions ui possibilities and analysis of prevalence of geographic and time data in subjects.
- Hope to be able to get a sense of how many catalog items have geographic or time data via the subject information.
- Looked at Harvard remote user testing presentation – approach was similar to remote testing we have done before. Will look at IRB and think about how to work toward evaluations by end of year
- Plan to work with Tim and Astrid on design ideas; and work out user testing approach
- 2020-11-13
- https://jamboard.google.com/d/1VHkygzzY-NWpwWEpZ9PqFjrnfPMADfTgjh8gFRi2MoE/viewer?f=5
- LD4P2 work reuse: Had set up LCSH index (i.e. most of the LCSH subject headings with URI and label) for search. Will reuse that and update with information from PeriodO, and separately temporal and geographic components.
- Design ideas: Will follow up with others, but generally, page load brings up aboutness and then enables browsing options/launching a page with LCSH
- Next steps: Prototype using 2-3 examples. Design follow up with Tim and Astrid. (Also need to get that IRB paperwork down in preparation for any possible usability evaluation)
...
- OCLC Linked Data / Entities Advisory Group
- PCC Sinopia Profiles Working group
- 2020-11-13 Going to LD Advisory group (a standing group of PCC)20 The PCC Sinopia Profiles Task Group Report was discussed at yesterday's POCO call, and it prompted big questions about where in the PCC will these profiles (or the platform agnostic version of them will live and be maintained). There will be a meeting in December with POCO, LOC NetDev, and Sinopia folks to discuss this.
- PCC Task Group on Non-RDA Entities
- 2020-11-13 Document ~87.5% written with some polish left to do. Discussion within PCC about possible collaboration/shared vocab with DNB-20 The PCC non-RDA report was finalized and submitted to POCO earlier this week. It will be discussed at a future meeting.
- Steven consulted with Kevin Ford on how publication frequency is modeled in BF. This could lead to an added node... classic RDF math, with a layer of abstraction in order to provision for frequencies that change over time and/or need to be qualified with exceptions to the rule. I'm going to reach out to LTS folks to see how we query the data in MARC to understand what useful queries would look like.
- Default branch name - WAIT until we can use github tools January 2021
...