...
Regrets: none!
Discovery (WP3)
.
- https://github.com/LD4P/discovery/projects/2 for issues etc.
- Research: how to go from knowledge graph to an index
- Research decision points, Use cases
- Jamboard link
- Expect to include Works. Need to do something beyond what we already have live from the OCLC concordance data.
- References/bibliography list (beginning)
- BAM! WOW! (Browsing Across Music With Obtainable Wikidata)
- 2023-01-05
- 5 people for testing: 3 grad students and 2 staff members
- Draft link for usability report, expect to complete by end of week
- TODO: Huda will set up a meeting with Tracey to go over these results and also discuss potential directions for the future
- Will then work on demo video
- Also need to finish lessons learned page for this phase
- Working on the BAM! WOW! video
- Steven and Huda met with Tracey to talk about what would need to be done for things to go to production https://docs.google.com/document/d/1B7KaLJKDl746luFzlpZk81bXmfFN02YnfnERyuQJObs/edit. There are design questions that Melissa might be able to help with. Steven and Tracey might bring prototype to D&A User Reps after discussion with Melissa, maybe with mockups from Melissa
- Usability report done! (Unless folks have edits to add)
- Lessons learned: Draft
- Musical work examples
- What remains
- Main demo recording
- Script for the acting portion
- Meeting with Tracey on Friday to review results
- Next steps?
- Based on discussion with Tracey might present to user reps (Steven and Tracey)
- Consider: Would we want to update author/title browse pages with info from wikidata
- Next steps?
- BAM! WOW! demo now running on ld4p3 server
- 2023-01-05
- DAG Calls
- 2023-01-12 - There is in fact a meeting 1/17. Will go over coordination, roles, topics for the new year. 18
- A small call, went over possibilities for roles and run sheets, and outreach. Rob Sanderson will talk about Lux on Feb 14.
- Huda has noted that zoom URL will change
- Who from Cornell should be engaged going forward? Potentially anyone from D&A, Matt/Jim/Frances all possible. Might have folks attend particular working sessions. Perhaps there should be a D&A "rep" ?
- Question: Still using the Cornell Zoom URL for 1/17. The Zoom needs to be started by someone with a Cornell email (no external hosts allowed), so will need to determine what the Zoom URL will be 1/31 (meeting after 1/17) onwards.
- 2023-01-12 - There is in fact a meeting 1/17. Will go over coordination, roles, topics for the new year. 18
Linked-Data Authority Support (WP2)
- Qa Sinopia Collaboration - Meetings with Stanford will only occur on an as needed basis. Authority request issues: https://github.com/LD4P/qa_server/projects/1 (prioritized based on "important" authorities and ease of completion)
- 2023-01-0518
- Steven added sections to the "Less reliance on caching" planning document to account for heavy Sinopia Users (Nat. Library of Norway and University of Washington). Each has a slightly different emphasis in terms of lookups.
- Broadly speaking we have the following questions:
- With no plan for a continued cache for Getty, do we want to look into Getty APIs?
- Dave is going to refresh MESH for 2023. Do we need a plan for after 2023? Their model/queries are a little more complicated than others, size is relatively big.
- RDA is made up of a bunch of very small static vocabularies. How low can we rely on Dave’s existing cache for these?
- Do we add these as static lookups in QA?
- For LOC vocabularies, what plan needs to be in place for switching to LOC APIs? E.g. Data will be more up to date, but it will lack the same context.
- Can we add “direct” lookups through QA?
- ISNI and DBpedia are large dynamic datasets. Would we consider direct lookups for these?
- Big Question: Do we rely on separate data source APIs? Or add “direct” lookups in QA?
- 2023-01-13
- Steven has done as much as he can for now on document
- We should plan to share our information with colleagues at Stanford well before trip
- PLAN to review 2023-01-19 and then share
- Reviewed Steven's summary. Steven will do a final tidy and then share with Stanford colleagues
- 2023-01-0518
- Best Practices for Authoritative Data working group (focus on Change Management)
- 2023-01-1218
- Working through activity types. Decision to flatten activity pattern rather than use nested structure
- Need some wordsmithing on order recommendation
- Reached out to Dave to see if he needs help.
- Steven rescheduled the meeting to 2023-01-17. Reviewing issues now to start discussions in Slack prior, hoping to make decisions in meetings.Asking around about whether/how/can we expect the rumored RDF SRS in FOLIO to be ActivityStreams aware.
- 2023-01-1218
- Containerizing the QaServer - Initial work done, still exploring migration from CloudFormation to Terraform
- 2023-01-05 Sticking with CloudFormation for now
- Containerizing the Cache Indices
- 2022-11-17 No plan to move on this at present
...
- 2/14-2/16 Meeting at Stanford (Simeon, Jason, Steven)
- Need to develop plan for pre-work
- Steven working on documentation of QA authorities and cache use
- "What is the linked data cataloging ecosystem we would like to see?" AND "Are we using our effort in the most efficient manner for ourselves and the community?"
- Cornell hopes in this space (ecosystem expectations, standards, services)
- Begin envisioning a new collaboration model so we can define ways to provision for that
- Who else should be part of discussion: Laura, Jenn, Mary, Simeon, Steven, Jason
- Scheduled for 2/1
- Successful meeting: take Cornell and Stanford view, understand gaps and overlap, review what we have done thus far, identify next steps to build the ecosystem
- Need to develop plan for pre-work
- BIBFRAME at ALA - Would be great for Jason to talk about the work of the FOLIO Entity Mgmt WG
- Reached out to Sally as JAK is concerned about overlap / duplication given the stakeholders she plans to invite
- Other meeting requests: PCC LDAC (Fridays at end of March possibly) and LOC (February 2)
Next Meeting(s), anyone out?:
2023-01-18 - all likely present-26 -
2023-02-02 -