Page History

Attendees: Greg, Simeon, Huda, Steven,

Regrets:

DC Debrief

LD4P Partner Meetings
- Want to review which authorities we support in QA and, in particular, which we need to support in the cache. Steven will work on this
- There was discussion of messaging about gains in discovery but we note that Steven and Huda have been on tour the last year or so giving talks. Huda thinks affinity group can be used
Linked Data SummitLD4P Partner Meetings
- Questions about how we might make progress toward a more fine-grained shared cataloging practice
- Underlying goals
  - Shared creation of the most useful metadata
  - Link to all appropriate data
  - Use cataloger resources most effectively to improve discovery - focus work where most useful, low friction sharing work, connect to data
  - Avoid duplicated work
  - Build discovery systems that leverage the available data in usable ways

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)
BANG! (Bibliographic Aspects Newly GUI'd)
- 1011/27: Lessons learned and documentation still outstanding17:
  - Draft for lessons learned
  - Documentation for scripts for data analysis forthcoming
BAM! WOW! (Browsing Across Music With Obtainable Wikidata)
- 2022-10-13
  - Kevin (Stanford) returned spreadsheet of properties present in Wikidata that are not commonly found in library metadata for musical works – to help guide which data would be an enhancement; need to monitor for additional content. Steven wrote query connecting musical work to what it was created for (e.g.: song created for a soundtrack) AND finding if LCCN exists... to then query whether we have that in the catalog.
  - Huda started a GH branch - plan is to pick use cases and set something up that represents that (e.g.: musical work in catalog has info button to Work that'll include K-number and other properties). pulled latest from Blacklight-Cornell and having issues getting Dev to run – D&A has been in multi-week updating to Ruby3; what is in Dev right now will not run in without significant updates to machine and code. Greg'll need to make tasks to get work done; not insignificant effort.
    - Hoping to go live with the new D&A code today or early next week; can start work for LD4P to run this code right away – will take a new work days but has good notes since has run this twice for D&A. Not urgent need.
- Worked on setting up info box on item page. Info box retrieves information in this way: get values from "authortitle_facet" field, parses to remove "|" to generate a form that can be used to query the LOC suggest service for name title authorities, uses the localname to query against Wikidata for properties of interest. Currently displaying heading, Wikidata entity, date of first performance, location of first performance, and music created for. Next steps are to add remaining properties of interest from Kevin Kishomoto's group's spreadsheet.
  - Options for display: Repurposing author title browse page similar to how we updated the author and subject browse pages to include more information, or incorporating information into the item page similar to how we incorporated Discogs information
- 2022-10-27
  - Using properties provided by MLA librarians, experimenting with bringing in information to the Info pop-up
  - One SPARQL query for entity; updated code to look for multiple values for any property and then removes duplicates. Allows for grouping in the results/UI
  - Some properties require special handling - catalog codes (2 pieces of information that go together: catalog + code. Another is "music for", which has two pieces of data)
  - Example without results: Puccini's Turandot: our heading is different from the authorized heading. BIBID: 4983368. The author-title is constructed in this case for the raw data. Vendor record for NetLibrary, Inc. - is there a pattern we can use to better build the SOLR index (e.g.: using the first 600 as seen in 4983368)?
    - Question for Tracey - how do we increase coverage for the feature Huda is building? E.g. netlibrary 600s with correct Name/Title (not reflected in the author_title_facet)
    - Question for later: hide bad data through queries OR expose that and deal with it later?
    - Question: where should button to go to connect to existing author-title browse from the item-view?
    - Question: When to link back to the catalog, and when might want to link back to Wikidata for context about related thing (e.g.: work is dedicated to (person). (person) may have an LC heading, which can be used to pull up related resources... but if they do not, do we then link back to Wikidata?
  - Mid-November: get interviews with music students with what we have at that time and assess which pieces of information interest them; gather feedback.
DAG Calls
- 2022-11-17
  - Worked on bringing in information directly into the page as opposed to using the info box approach. Did two different approaches for (a) single returned entity and (b) multiple entities (due to multiple author title facet values represented for the record where these values also link to LOC URIs with Wikidata connections).
    - Will work on updating the author title browse page to bring in this information. At this point, leaving out putting in a connection between the item page and the author title browse page, since unclear where that should go.
  - Tracey also provided a link to the Vivaldi Wikidata entry she and her group have been working on: https://www.wikidata.org/wiki/Q114601197. Will try to see if there is a library catalog item we could link to,
  - Usability testing/feedback: Reached out to Tracey to see if there are music students who we could recruit for getting feedback on prototype and to ask questions around what they may find useful. Will reach out to finance department soon to start setting up gift cards.
    - Timeframe: early to mid Decemberish
  - Will plan to wrap up this phase in January, after the user tests. Perhaps will have a discussion with D&A in January.
  - Post-January - might use Usability Working Group for testing
DAG Calls
- 2022-11-17 - Meeting next Tuesday, likely will discuss coordination10-27: Nat'l Lib of Sweden presented on 10/25 - two points of note: card/chip model where ask what are the properties of interest for a particular entity and what is the graph for that entity? Similar to what Phil has in a linked data summit question: record. These are the data points needed to make sense of the entity. Card = data displayed; Chip = search snippet. Implementation specification. Internally used custom ontology as a mapping/hub so they have equivalences and subclassed off other ontologies (schema, BF, DC, others) to allow for system needs alongside other needs. JSON-LD blob that represents graph and ElasticSearch index runs what users are seeing (catalogers AND discovery). Triplestore exists but sits separately to populate postgres. Lots of questions. Great session.

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)
- 2022-1011-0617
  - Greg and Steven have been working with Dave on new LOC Countries authority. Still running into problem that the cache is crashing, need more guidance from Dave
  - Yesterday Steven got a request for a change of context, result of PCC meeting last week
- 2022-10-13
  - Continue to try to troubleshoot getting countries to run. Proposed standing short meetings for the foreseeable future to work through issues.
  - A request for context changes to LCNAF has raised a question about whether Dave has indexed the fullest RDF representation. https://github.com/LD4P/qa_server/issues/492
  - Asking Dave for a recurring meeting to knock out a couple issues/week
  - FOR NEXT WEEK with Simeon: How can we let Dave retire: someone to run triplestores, run lucene index, make sense of Dave's code. Dave has a lot of hand-built infrastructure on his premise that we cannot economically replicate. Greg put up containerized LD4P services but the indexers that run, query and create caches has not been done and we don't have resources to do that – another big project. Only going to get worse. Need a plan.
- 2022-10-20
  - Working to discuss plans with Dave
- 2022-10-27
  - Dave found that there was more amiss than just the syntax error (prefix definition) in the CONSTRUCT; Fuseki needed to be restarted.
  - Countries is available now in https://lookup.ld4l.org/authority_list; Greg found a couple non-critical errors about expected size of reseults https://lookup.ld4l.org/check_status?utf8=%E2%9C%93&authority=LOCCOUNTRIES_LD4L_CACHE&compare_with=&validation_type=all_checks. Basically QA by default seems to expect 200 or more results for connection test. Steven found a way in the yml config file to override this. Will make the change, but not important to push to production.
  - Steven made a pull to Sinopia to add Countries as a lookup. https://github.com/LD4P/sinopia_editor/pull/3610#event-7674173787. Been approved/merged, waiting for it to be pushed to production. Not sure if these changes are saved for named releases. <STEVEN TO CONFIRM WITH JUSTIN>
- - Countries have been pushed to production
  - ACTION ITEM: Steven to spend time thinking about how to minimize QA footprint/commitments for lookups needed by the Sinopia/PCC Users. What lookups should use the QA direct option? What lookups should use data provider APIs? (LOC data). What lookups aren't currently being used in Sinopia. How do we think about stale caches?
Best Practices for Authoritative Data working group (focus on Change Management)
- 2022-10-27: considering de-nesting related activities and proposed strategy to handle placeholder for any number of different properties between entities; have feedback and plan to simplify proposal. Addresses issues ranging from nesting, deprecation, merges, splits. Once decided, will need to update recommendations
- 2022-11-17 Haven't met in a while due to travel. TODO get meetings back on our calendars and prompt folks to engage with issues.
Containerizing the QaServer - DONEInitial work done, still exploring migration from CloudFormation to Terraform
- 2022-08-04 Greg digging in to terraform as a potential replacement for cloudformation, not ready to move yet!
- 2022-09-15 Still exploring, have only tried baby steps so far. Need to focus on current system first
Containerizing the Cache Indices
- 2022-0711-21 : 17 No progress. Have not heard anything from Dave; Jason will ask him at Monday's PI meeting to respond to Greg
- 2022-08-04 There wasn't a PIs meeting so haven't yet checked with Dave
- recent progress

Next Meeting(s), anyone out?:

...

Page tree

Versions Compared

Old Version 1

New Version 2

Key

DC Debrief

Discovery (WP3)

Linked-Data Authority Support (WP2)

Next Meeting(s), anyone out?: