Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Qa Sinopia Collaboration – Support and evolve QA+cache instance for use with QA
    • 2021-02-12:
      • Dave, Steven, and I met to review the status of issues related to the indexing approach.  4 were closed (returning too many results, newline issue, all tests passing for geonames and ligatus).  2 more will likely be closed today (accuracy tests for locgenres and locnames).  4 others are under active exploration by Dave (getty looking for subject to end with -place and -agent, some subauths not returning any results, mesh hierarchy and description issues).  5 other issues awaiting exploration.  Some may be fixed by the current set of issues.
      • Vivian at Stanford sent email to Anna at ShareVDE to restart discussions about moving data round trip from Sinopia to ShareVDE, form Stanford's MARC converted records to ShareVDE, from ShareVDE to Sinopia, and direct access to ShareVDE through QA.
      • Michelle announced the release of ShareVDE's PCC data.  They are provided as downloaded data, not direct access to ShareVDE. Dave is reviewing for import to the cache.
        • When we do have a round-trip, where is the source of truth? How will we track this? How does QA deal with this and what portions of the graph should it handle? Lynette has been looking at GraphQL (which maybe isn't directly usable) for information about how to define a graph shape/selection in a flexible way
  •  Cache Containerization Plan - Develop a sustainable solution that others can deploy
    • 2021-02-05 Greg says "I've finished expanding the CloudFormation template to include a container service, which will make the container much more useful to adopters. There are still several steps which are not automatic, involving networking and security groups, and making those automatic will require the template to create the cluster of machines that the whole thing runs on. That will be super nice, but it will be a pretty big expansion of the template."
    • 2021-02-12 Not much progress, next step is to add cluster to template
  • Search API Best Practices for Authoritative Data working group
    • ACTIONSteven Folsom will send document to PCC
      • Pending announcement mentioned below
    • ACTION E. Lynette Rayle will send announcement to Samvera and put a note on #general, also link from main LD4P page. 
      • 2021-02-12:
        • The summary document is almost complete.  There is one question about the wording around broader and narrower terms and related user stories.  I am adding in an introduction that describes the working group and defines the 3 perspectives for catalogers, developers, and providers.
        • Began writing the announcement that Steven and I can use for the various communities – any feedback due by Monday 2/15

...

  • OCLC Linked Data / Entities Advisory Group
    • Request for UI and API testing from Jan 25
    • Lynette has Cornell key (a WSKEY) for testing
    • Call discussed seeding of data. Data for person includes VIAF and other sources;  place includes geonames. Steven, Huda, Jason and Lynette signed up for user testing
    • 2021-02-12 Attempts to test have been frustrated by lack of documentation of testing desires. Some users have been providing feedback about expected metadata details
  • PCC - Sinopia collaboration
    • 2021-02-05 Charge to form a new group for documentation, mentoring etc is under reviews
  • PCC Task Group on Non-RDA Entities
    • 2021-01-15 PCC reviewed proposal but no decisions made yet, looking at description wrt cataloger use, discussion will continue
  • Default branch name - WAIT until we can use github tools January 2021
    • Lynette is signed up to be a beta tester for github. Target for public release is end January
    • Github have provided the change button, Lynette has provided feedback as a beta tester. There is an issue that after the change to `main` someone can repush the `master` branch, has suggest a deny list of branch names. Links in comment will get forwarded to `main` unless there is a new branch with the old name
    • For forked repos there will be a message 
    • What will it take to make the change to `main` for LD4P repos?
      • Lynette has documented HERE
      • Lynette will rename for qa_server, work with Greg on qa_server container; document on LD4P wiki
      • For our blacklight fork we should wait until the D&A team change
    • 2021-02-05 12 E. Lynette Rayle still to reach out to fork owners
      • Think that forks aren't too problematic for LD4P repos because we don't have folks contributing back
      • Have done rename for CUL-IT qa_server and will for LD4P qa_server
      • ACTION: (DONE) Lynette will review set of LD4P repos with Cornell primary ownership so that we can change these to use `main` branch, later propose that other LD4P repo owners do it

Upcoming meetings

  • https://kula.uvic.ca/index.php/kula/announcement/view/1 .  Call for Proposals - Special Issue: "The Metadata Issue: Metadata as Knowledge".  Due January 31, 2021 (abstract 300-500 words).  Includes "The use of linked open data to facilitate the interaction between metadata and bodies of knowledge" and "Cultural heritage organization (libraries, archives, galleries, and museums) and academic projects that contribute to or leverage open knowledge platforms such as Wikidata"
  • code4lib - virtual next year
    • Expecting to attend: Huda, Steven, Lynette
  • Lynette doing a QA presentation at Samvera partner call in June

...