Huda Khan will work to get a draft PR to add context in Sinopia lookups and seek review from the Sinopia team, goal is to get this ready for cohort before Sinopia is released at the end of work cycle 4 (end July)
Has been working on refactoring to do this. Hope that there might be a PR today with loading icon and search code. Sinopia team have changed QA code recently to save label as well as URI
2019-07-27: Draft PR on Friday. Still working on it – some changes were happening on Sinopia side so downstream changes into Huda's code. Going to figure out tests and then run it past Michelle & Jeremy. Dev should continue thru next week. Continue update on this next week.
Tim Worrall and Steven Folsom to try the load tab with data from Discogs and an appropriate template
Troubleshooting distance b/t profiles created and new target based on Sinopia changes. Sinopia has narrowed amount of BF profile spec used and expanded in other areas... have to abide by those rules or error prevents loading profile. Refactoring profiles. Tim took resource template with only a title... and tried to load N3 into it; nothing happened when submit hit - javascript error generated.
When work on title resource template, there are 4 different fields to enter (e.g.: main title, subtitle, etc...): entered data into all fields and hit preview RDF - has an empty node for subject... and isGeneratedBy. Seems to be reverting in its functionality...
Huda: end of next week, should have a better sense of what is working... likely/scheduled to be end of work cycle 1
Due to changes, work now by LC to create Sinopia-compliant LC Profiles. Michelle recommended waiting for this. We are not waiting for this for Sinatra as that would entail extra effort.
ACTION ITEM: Steven Folsom will complete a first-pass complete with one full day of work (COB Monday, 7/29); there will be many concessions (cannot create a different form experience based on the type of entity for which the form exists - second pass, not first).
Tim Worrall to talk to folks to try to get a sense of how much work it would be to connect Discogs lookup to data import
Exchanged emails with Jeremy. He said: for next work cycle (September), big deliverable is loading RDF from external source via QA. Do search against QA sources in new search tab and user is able to load resulting RDF into editor. Rather than template with look-up field, the search page will have option of querying discogs and then load. Guess: there needs to be code to take data from discogs and map... but mapping cannot be uniform / fully automated.
Based on response and that there is something happening soon, assume that we would not do this ourselves; there would be a lot of duplication.
Huda & Tim idea: do something outside scope of Sinopia - do one-off rails app to meet cataloging requirements.
ACTION ITEM: Jason to contact Michelle re: is this really a thing in September?
Kaleidoscope article (continuation of the LD4P MWG update)
ACTION ITEM: Jason will start draft. Deadline sometime before mid-August, let's say 8/10
Year 1 Report: Key achievements, per statement of work sections:
Perform cataloging experiments within the sandbox editing environment, providing iterative feedback to the development team (WP5)
cataloging work scheduled for year 2
preparatory work to understand material and develop Discogs "authority" completed, including mapping to RDF; look-up portion has been tested within Sinopia. Not doing anything with data yet but can connect within Sinopia and get RDF back.
application profile development for Sinatra
Huda spent significant effort working on behalf of Stanford to develop Sinopia – specifically focusing on context and lookups
Implement authority lookup services for the sandbox editing environment (WP1)
Lynette should be consulted. She did all the things and is not here today. Also talk to Dave.
refactoring, configuration, infrastructure, cohort engagement, many presentations
Implement reconciliation services (WP3)
Basic SPARQL analysis around existing recon in hub data sets (i.e.: wikidata, ULAN, FAST, LC)
Enhance catalog discovery (WP4) – in collaboration with Stanford
user stories in conjunction with speaking to actual patrons
knowledge panels and testing therein
prototying and dev around knowledge panels and work to pull in related works and suggested searches
tying in lots of diffferent info wikidata
Tim's prototyping related subjects from wikidata, dbpedia and LCSH
Huda's examples around Lincoln : motivating search examples to inform prototype development and evaluation
Affinity group formed, led by Huda and Jessie
committed code that removed suggested search results that do not retrieve CUL results (i.e.: made relevant the extended context within our local environment)
analysis of coverage of connections, specifically wikidata to catalog & OCLC works
Community??? (left off the initial list)
affinity group engagement: discovery, profiles, ethics, sinopia user group, wikidata, rare materials
Jason co-organized LD4 conf
liaise with PCC
Coordinate and disseminate project work – , regular call attendance, conference presentations (all should post slides to some relevant)
ON HOLD pending more work in Sinopia to import data. Sinopia work through work cycle 4 will include the ability to read in RDF back from Trellis. We hope that we can leverage this to import RDF from a lookup in Discogs or ShareVDE
Huda has mockups and need to buy candy bars and do the testing
Work Area video: John, Tim and Huda will make a video – informal walk-thru of the functionality. Whomever would like to engage, talk to Huda. Tim is out.
Dave loading all of the SHARE-VDE data to DAVÉ rather than focusing on only the institutions planning to use S-VDE data. Perhaps confirm with Dave. If so, voting process would be ignored by S-VDE. Outside of S-VDE, all requests are valid but we lack capacity to complete all. Prioritization should be under the program as-a-whole
ACTION ITEM:Simeon Warner should speak with Dave to better understand his capacity
ACTION ITEM:Jason Kovari will speak to Michelle to ask her to manage the prioritization process