Date:
Attendees: Huda, Greg, Lynette, Steven, Jason, Simeon
Regrets: none
Discovery (WP3)
- https://github.com/LD4P/discovery/projects/2 for issues etc.
- Draft of a discovery plan: https://docs.google.com/document/d/1zKYW7FQVVNvyd0XjjW0qWznX9PC3jbmOE6Kz_yygPjs/edit?usp=sharing
- Research: how to go from knowledge graph to an indexDASH! (Displaying Authorities Seamlessly Here)
- 2022-02-11 - Documentation is DONE
- See WP3: Discovery
- 2022-02-11 - Documentation is DONE
- BANG! (Bibliographic Aspects Newly GUI'd)
- Jamboard link
- Expect to include Works. Need to do something beyond what we already have live from the OCLC concordance data.
- Huda has works on HTML/Javascript graph explorer code and showed demo. Steven notes how this will be useful to explore datasets. Where to take this work? Perhaps discuss with Dave based on the set of queries used, and to see whether this can run over his Lucene/ES index for more responsive.
- Huda working to get counts of items under the same LC Hub. Steven and Huda will discuss the data further
- For past research on works and usefulness to users, Huda will also revisit FRBR/BIBFRAME + user research references previously suggested for KULA paper
- 2022-02-11
- Calls next Tuesday for DAG, and the following for WAG focusing on DASH! production and experimental work
- Calls next Tuesday for DAG, and the following for WAG focusing on DASH! production and experimental work
Linked-Data Authority Support (WP2)
- 18
- References/bibliography list (beginning)
- Plan: Continue reviewing and looking at references
- Huda added a "feeling lucky" page to fuseki UI which picks random statements to show so people can start exploring. Needs to send info to/show to Michelle (Stanford), and ask Jim Hahn (Penn) if interested.
- Plan: Add click functionality on the graph to generate a side panel with details for that node/entity. May be easier to understand than spaghetti expansion
- Steven mentioned classes/predicates summary to Dave
- Hubs analysis: Huda changed approach after discussing with Steven what we're trying to explore with this analysis.
- Main question for ShareVDE and Hubs aggregation: Can this data yield relationships between/groupings of works that yield related items in the catalog? We want to extract sets of ISBNs grouped under an aggregation or under a property between works, and then see if any of those sets yield at least two catalog matches (i.e. translate into relationships between items in the catalog)
- Approach for ShareVDE: Evaluate how many opera there are with at least two works and at least two related ISBNs, and how many of these ISBN groups yield at least two catalog matches. (Only one catalog match means that, if we were on that item page, we would not have any related items to see using this data).
- Steven notes that a link via Hub from an ISBN we hold to one we don't hold is a possible ILL use case
- Now for Hubs: Get sample of hubs from LOC search. Changing start parameter to page through list to work around LOC side throttling. For each hub, see if ISBN set can be generated. For each set with > 1 ISBN, determine if there > 1 catalog matches.
- Plan: Continue to do so. Current results: For 4000 hubs from LOC, 87 sets of ISBNs (with > 1 ISBN) where hub has > 1 work = 367 unique ISBNs => catalog matches where you have at least two catalog items for that ISBN set: 12 ISBN sets yield matches for total of 73 ISBNs
- References/bibliography list (beginning)
- 18
- DAG Calls
- 2022-02-18
- Had first crossover call with WAG group focusing on DASH! and usability testing. Some questions to follow up on, report of our page selecting one citizenship statement where wikipedia has multiple statements that might be a bug
- Next week will talk more about this work and also about getting and using feedback from use reps etc.
- Had first crossover call with WAG group focusing on DASH! and usability testing. Some questions to follow up on, report of our page selecting one citizenship statement where wikipedia has multiple statements that might be a bug
- 2022-02-18
Linked-Data Authority Support (WP2)
- Qa Sinopia Collaboration
- 2022-02-18
- No meeting with Stanford this week. Steven, Dave and Lynette met to discuss current priorities
- 2022-02-04
- Met this week and covered 3 topics:
- pagination stopped working in Sinopia probably due to a bug fix in the cache system. Previously, the number returned would be different than the total number which would trigger pagination to show, but the number returned was greater than the number requested. This bug was fixed. A second bug has the number returned equal to the number requested which makes it look like you have all the results. Dave has a planned fix.
- Standards committee may be making vocab requests, but don't expect many. Definitely requesting homosaurus.
- Renamed existing ISNI auth to ISNI_LD4L_WRAPPED. Used the existing name, ISNI_LD4L_CACHE for the new cached RDF download. These updates are in production.
- Met this week and covered 3 topics:
- 2022-02-11
- No meeting this week.
- Jim Hahn asked "if an NAR (name authority record, ref. to LCNAF) is updated, when do we expect to see that change populated through QA?" My response was that we currently take a full dump periodically, but it is not on a predictable schedule. Not the best answer. As auths adopt the working group recommendations, it sets the stage for Dave to use incremental updates on a regular basis (e.g. nightly).
- Current priorities include
- fix of total_number_found to make pagination work to get pagination working again in Sinopia (Dave)
- add homosaurus authority - Dave uploaded in cache, but needs to run indexing, Steven defined context defined, Lynette defined QA config and waiting on index to be able to test prior to deploy
- create documentation of search queries for cache (Dave)
- try using LOC or Getty activity streams to update the cache (Dave). This is proof of concept. It may prove insufficient as none of the feeds include patches. But makes for a good exploration.
- Update pagination in QA linked data module to use json-api as output (Lynette)
- 2022-02-18
- Best Practices for Authoritative Data working group (focus on Change Management)
- 2022-02-04
- There was discussion in Slack about the usage of Add vs. Create. I believe we have settled on Create indicating the entity is brand new and Add indicating that the entity wasn't available and now it is (e.g. permission change, temporary removal reinstated, etc.) I expect Remove and Delete to follow a similar pattern.
- Meeting on Monday to review EMM Change Document API and Notifications Example
- Updates include incorporating suggestions from last meeting, adding reference links at the start of each section, specifying property examples common across activity types in one place, adding more content across all sections. Sent both recommendations document and notifications examples to the group for review.
- There are two other use cases which need examples, but wanted to get feedback on the notifications before working on those
- Working on external documentation for EMM Change Document API. This was running just on my machine, but it is now available at ld4.github.io, which will make it easier for the working group to review. I am incorporating feedback from the last working group meeting.
- Coming soon: Simple working examples at ld4.github.io. Dave plans to work on connecting to LCNAF's feed as a proof of concept.
- 2022-02-04
- Containerization
- 2022-02-11
- Chile and Antarctica, yay!
- Delivered CloudFormation templates to Stanford, they had only partial success, got stuck and then moved to other work. Next work cycle much later in the year
- Containerized version of lookup quite stable but looking on changes for customization etc.. Lynette feels good about build and deploy workflow. Need to finish off customization before moving to production
- Lynette will look at how it would be to move the current version live, before the customization is complete
- Would like to get started on containerizing Dave's cache – need to discuss with Dave. Plan to set up call with Dave to discuss how to containerize the index
- 2022-02-11
Other Topics
...
- 18
- QaServer - Evaluating status of docker deploy to determine how close it is to being ready to become production.
- working as expected: has all authorities installed; spot tests showed all queries tested were successful; check status page is functioning; API Documentation displays; Fetching a single URI works
- not working as expected:
- monitor status page gets an error that looks like it might be database related
- not sure how to connect to debug
- once working, it needs a nightly job
- most customizations are for the monitor status page, so unable to evaluate customization requirements for production
- Greg and Lynette will work on these items, perhaps consider framework for maintenance jobs and maybe consider for nightly rebuild too (needs two requests at specific times)
- Cache Search API - Planning meeting next week with Dave and Greg
- QaServer - Evaluating status of docker deploy to determine how close it is to being ready to become production.
- 18
Other Topics
...
.
- Sinolio - Sinopia-FOLIO
- 2021-12-17 - Work Cycle finished, sprint video out
- OCLC Linked Data / Entities Advisory Group
- 2021-12-10 OCLC presented at bigheads meeting this week, in testing
- PCC
- 2021-01-21 Definitions and non-RDA final report to POCO (hopefully) to be submitted next week
- 2022-01-14 Nothing new to report.
- Authorities in FOLIO
- 2022-01-14 Working on "deletes" workflow (actually deprecation with replacement process for references). Current workflow uses browse in Blacklight and benefits from links into FOLIO2022-01-29 Making good progress, in part because of new Slack channel. Doing user acceptance tests for FOLIO Authorities module02-18 Mary met with team and making progress with deletes, Frances is getting experience building out the index with hope to have and API Nick can work against by end February. Steven has diagram of vision
Upcoming meetings/presentations
...
Next Meeting(s), anyone out?:
2022-02-25 - Simeon out... moved to 2022-02-24 9am - Jason and Steven out
2022-03-05 - Simeon out, Jason will run