...
- Steven FolsomLC Names is in QA without going thru context workflow. Steven Folsomwill work with Huda Khan to set up.
- 2018-12-13: awaiting data dump. LC working on it but they have yet to achieve. Larger data set so it's taking time. No deadline provided.
- Jason Kovari to make a start at brainstorming/planning D&A ideas
- Earlier idea was to set up homework to brainstorm D&A ideas on Google Doc, then set up longer session together to flesh out. Scan the large set of D&A issues: https://culibrary.atlassian.net/secure/RapidBoard.jspa?rapidView=19&projectKey=DISCOVERYACCESS&view=planning.nodetail
- Huda Khan set up a call with Astrid that was fascinating (their weekly, informal calls). Huda made fun slides... and facilitated the conversation.
- Slides: discovery_brainstorming.pptx
- What is the Discovery Affinity Group? Did anything happen here? Tom and Simeon were supposed to be leading this???? (acc'd to wiki)
- ACTION ITEMS:
- Jason Kovari going thru CUL's D&A Jira (next week or so)
- Huda Khan is working on whether usability work on catalogs has been done internally as well as externally to CUL. Code4Lib journal and another has some details
- Astrid doing user interviews with microbiologists and music librarians
- Tim Worrall will join this effort moving forward
- Jason Kovari will schedule formal meeting for those involved in the Discovery work plan for early January
- Steven Folsomto follow up with Tim Worrallabout status of Discogs work and how it fits with expectations
- Takaway: until there is a UI to look at data showing up in form, it is hard to assess. Mapping has to happen – and then be in an instance of the BF Editor.
- Recon strategy around Agents. Huda doing some of this, as was Steven. Write up (link) found that under 50% of Agent IDs in Discogs had a WikiData or id.loc.gov URI. If dedupe, it is a little less but still highly promising. Did not consider performance... questions remain about what script will ping (QA server, Discogs API, etc.)?
- Tim: on white board, we had the recon work following the selection.
- Hybrid approach eventually... but first pass will be returning a string for an Agent. Returning JSON-LD and would be paired with BF property - but pointing to string rather than URI initially.
- E. Lynette Rayleto follow up with Tim Worrallabout whether we can publish Discogs lookup as part of QA because we think others might be interested in using it
- No progress at present.
- In earlier meeting, there was an understanding that we would do this. Tim is proceeding under this expectation. Discussed possibility of adding context in same way that context is added in the linked data side-of-things.
- ACTION ITEM: Tim Worrall , E. Lynette Rayle will take off-line and report back next week.
- E. Lynette Rayleto follow up with YAML for https://github.com/LD4P/qa_server/issues/13 and https://github.com/LD4P/qa_server/issues/26, then Steven will shepherd the process with the person requesting. Also with Christine and Marc around Wikidata
- Washington added what was needed for YAML. Needs E. Lynette Rayleto confirm we don't need more.
- ACTION ITEM: E. Lynette Rayle : one open PR for demographics. will run tests to see if pass or fail
- Simeon Warner to mention to Michelle Futornick the idea of starting a list of topics for our next partner discussion/meetings, and add the notion of what it might mean to "productionize" the QA/Dave setup
DONE, created https://wiki.duraspace.org/x/p4B7Bg and mentioned to Michelle
- Issues: https://waffle.io/LD4P/ld4p2-cornell
- Related to 43, Lynette will create a separate issue for Agrovoc re: URIs changing
...