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
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.
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
ACTION ITEM: 2018-12-21. Huda will fork Sinopia editor to see what it takes to get front-end to do things to get them in-line with what we want to see... without affecting Stanford's dev
Covered in Action Items section. Working on QA for Discogs is in-progress. Once done, will mock it up in instance of BFE
Enhanced Discovery
In early January, meetings will begin to transpire. For more, see previous section in notes
LD4 Conference
Organizing committee kicked off work this week. We will use a process similar to WikiCite whereby people apply to attend with the expectation that this is a participatory conference. More on this soon.
The application/nomination process will shape the event. Themes include implementation and community (at the very high level)... with questions in the application around whether people are willing to present... and also a question geared to scope potential facilitated discussions.