...
- Jason Kovari will continue functional requirements efforts, starting with workflow diagramming
- Organizing cohort effort around this is on-hold until January; Jason has not yet made progress beyond: https://miro.com/app/board/o9J_lfXUUj8=/ ; will pick up work either before Break or immediately following
- E. Lynette Rayle to finalize the survey for cataloger user stories for PCC feedback and ranking by working group, check with IRB
- 2020-12-04 - Distributed with 19 participants in less than 24 hours. Will send another reminder today. Closing mid next week if there are weak responses. DONE
- Top three: seeing contextual info, filter by class-type, see broader/narrower
- Bottom three: updating local data if changed in original source; which field triggered a keyword match; if cannot find in local look-up don't want to go to original source and search there (need to dive further into these)
- 2020-12-04 - Distributed with 19 participants in less than 24 hours. Will send another reminder today. Closing mid next week if there are weak responses. DONE
...
- C.f. Stanford functional requirements document: https://docs.google.com/document/d/18H6zYGwKuCg3SZqm9Q_cxkZThcdmBjknE6HdtQ-RRzk/edit#heading=h.4fu64x8jzm6e
- What does success look like? And then how do we get there?
- 2020-12-04: discuss next weekStarting with diagramming: https://miro.com/app/board/o9J_lfXUUj8=/
Other Topics
- OCLC Linked Data / Entities Advisory Group
- PCC Sinopia Profiles Working group
- 2020-12-04: remove from the agenda. when update, Steven will bring to the group. Now discussion is focused on who will own the work
- PCC Task Group on Non-RDA Entities
- 2020-11-20 The PCC non-RDA report was finalized and submitted to POCO earlier this week. It will be discussed at a future meeting.
- 2020-12-04: on PoCo agenda for 1/14; more after that
- 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. Steven has reached out to LTS folks to see how we query the data in MARC to understand what useful queries would look like (there are 2 places for this data with some variants in our MARC data, not always up-to-date, shows as Frequency field in Blacklight (perhaps from 310 rather than 321, or 008))
- 2020-12-04: came up on Sinopia QA meeting – around Sinopia design principles (lookups happening using QA) but have entertained within-ontology property and class look-ups. Raises question of whether QA should afford ontology term look-ups. QA allows method of small set of look-ups - trivial to create. Can remove from agenda for next meeting.
- Default branch name - WAIT until we can use github tools January 2021
- Samvera community meeting this month.
- Discogs & 024s. Steven led 024 conversation among music catalogers
- how do we completely break the connection to Discogs? to ensure that a record in Blacklight with the wrong match to Discogs... and does not have a representation in Discogs...
- can check whether we have solved this issue for other external sources (e.g.: book covers, etc.). prioritizing 024 above the search... and also look for local field if there is a nodiscogs flag. We can wait to discuss this until the post-implementation assessment
- issue: dynamic database so a no match today may be a match tomorrow
- will code look for 024 before doing search? code has not yet been updated...
- how do we completely break the connection to Discogs? to ensure that a record in Blacklight with the wrong match to Discogs... and does not have a representation in Discogs...
...