Page tree

Skip to end of metadata
Go to start of metadata

Date: 

Attendees: Huda, Tim, Steven, Simeon

Regrets: Jason

Agenda & Notes

Review actions from 2019-06-07 Cornell LD4P2 Meeting notes

Status updates and planning

  • LD4P2 year 1 update for CUL in July 17 MWG @ 3pm
    • Good to include interface stuff as all of our work in metadata focused
    • Simeon - project intro, positioning, Stanford and Sinopia (7min)
    • Lynette - QA / DAVE (7min)
    • Tim - discogs (5min)
    • Steven - Profiles (links QA and Discogs work) (7min)
    • Huda - Discovery and user perspective on lookup (7min)
    • Jason - LD4 community, cohort and future (7mins)
    • Discussion - 20mins
  • Enhanced Discovery (see also https://wiki.duraspace.org/x/sJI7Bg and https://github.com/LD4P/discovery/projects/1)

  • Authority Lookups for Sinopia (Lookup infrastructure: https://github.com/LD4P/qa_server/projects/2, Authority requests: https://github.com/LD4P/qa_server/projects/1)
    • How do we do both adding vocabularies and reflecting the ldpaths in the context spreadsheet? Can't make progress with ISNI as no RDF available; Wikidata progress limited by data in API results; others complete on the spreadsheet. Steven has added a number of new issues that will require changes both in DAVE and in QA – Lynette will shepherd these though DAVE and QA. Top priorities are LCSH, LCGFT and Mesh
    • How do we deal with feedback when Sinopia goes live? Or how do we soft launch? – Possibilities for expectation management at the cohort meeting, how do we recruit people for testing and get good mechanism for feedback. ACTION - Lynette Rayleto put together a lookup status board. Need also to make it clear that each authority in SInopia/QA has an owner that is responsible for getting to agreement about how we want the authority to work (e.g. ranking) and that the YAML test settings should reflect these decisions. Steven to suggest possibility of regular lookups update on Sinopia use group calls
  • Prep for Cataloging Sinatra and other 45's (Discogs data, https://github.com/ld4p/qa_server/issues?q=is%3Aissue+is%3Aopen+label%3ADiscogs)
    • ON HOLD pending more work in Sinopia to import data
    • Huda demonstrated discogs lookup in test Sinopia instance... hoping to get changes merged in soon. But will still need import and save functionality before useful
  • Travel and meetings (see LD4P2 Cornell Meeting Attendances)
    • LD4P June 2019 Meeting: Agenda formation: https://wiki.duraspace.org/x/p4B7Bg
      • Lynette, Steven, Jason, Huda
      • Partner meeting is day after cohort
      • Cohort discussion topics:
        • How do we handle SHARE-VDE data for cohort institutions in QA? Should these appear as a separate "authority" for each institution or as one commingled set? The latter is perhaps better for taking advantage of reconciliation and promoting improved ways of working with linked data → Steven Folsom to try to get this question on the agenda for the "Sinopia and Share-VDE interaction" 2:15pm session, Lynette Raylewill also attend
    • Other meetings
      • IPLC Discovery Day is July 22 – what is overlap? 
      • Blacklight Summit will be at Duke, dates not yet announced 9, 10, 11 October at Duke
        • Huda and/or Tim?
      • LD4 BL meeting either September of December, buffer around BL summit
      • European Bibframe summit in September, call for proposals expected soon
        • Jason considering ARM/rare-cohort proposal
      • SWIB19 25-27 November (Thanksgiving week (sad)) - call deadline passed 26 May 2019, no submission
        • Possibility of QA + Dave in container
        • Consider discovery proposal
      • Samvera Connect
        • Lynette to present on QA
      • 5th International LODLAM SUMMIT at the The Getty Center in Los Angeles. February 3-4, 2020
      • WikidataCon, Oct 25-26, 2019, Berlin, Germany
        • Hilary will propose talk
      • rdfs:seeAlso Conferences Related to Linked Data in Libraries
  • Next meetings:
    • 2019-06-28 - just after meetings, Simeon out => cancel
    • Think more about wikidata engagement