Page History

...

• Qa Sinopia Collaboration – Support and evolve QA+cache instance for use with QA
  
  • 2021-03-12:
    • No meetings this week for QA/Sinopia this week.There will be a meeting
    • with ShareVDE + LD4P teams on Monday.  Previous meeting of this group were focused on how to get Sinopia data into ShareVDE.  The upcoming meetings will focus on how to get ShareVDE data into Sinopia.  There are two tasks: 1) find a ShareVDE resource of interest, 2) clone a ShareVDE resource into a Sinopia resource.  QA seems like a likely candidate for the search.  There are several options for cloning which might include direct de-reference through ShareVDE, de-reference directly from Dave's cache, or de-reference through QA. See Steven's comments on ShareVDE data.  Dave wants to look at making a direct connection to ShareVDE GraphQL API and translate it on-the-fly to something that QA can work with.  There are going to be some complexities with how to structure queries and extended context based on the variability.
• Search API Best Practices for Authoritative Data working group
  • 2021-03-1219:
    • There were 53 responses.  If you only take into account the first choice, Change Management is the top choice.  If you take into account the top 2 choices, Linked Data Tooling takes the lead.  With the top 3, Language Processing just barely moves to the top.  With all 4 choices taken into account, all but moving to specifics from user stories are roughly equal.  I'm inclined to take on Change Management because it it the most straightforward and would be a quick win.  Then move to Linked Data Tooling for a 3rd charter.
    • Image Removed
    • Created the charter for the next working group describing the expected outputs for change management.  I plan to announce the charter on Monday and begin reaching out to individuals to get folks on board.
• Cache Containerization Plan - Develop a sustainable solution that others can deploy
  
  • 2021-02-19 Greg completed CloudFormation template that allows someone to spin up a QA service in AWS easily. About 500 lines of template code that brings this very close to being a turnkey solution (in services-ci branch).Greg notes pre-reqs for spinning this up: S3 bucket for configs etc. which could be added to another template.
    • When complete Lynette will test, then ask Dave to test, then ask Stanford folks. Greg will also create a demo screencast.
    • What about replacing the current QA setup with this new approach? Would need to check authority configuration and correct setup for load. Lynette notes need to copy over the DB to retain history
    • Next steps
      • start to look at containerize Dave's setup. Two steps: 1) code to serve from cache, 2) indexing process
      • think about instructions for a vanilla linux server setup
  • 2021-02-26
    • Cache containerization discussion in QA-Sinopia meeting: We mostly talked about the next steps for the cache creating two containers: 1) container for API requests to retrieve cached data, 2) container to ingest data downloads and creation of the Lucene index.  This is fairly straight forward in the current approach of a full-data dump and ingest.  It is expected that there will be some complexities to resolve in how to update indices when change management techniques are deployed by authority providers that allow for incremental updates.  We punted that discussion until later when the format of change management streams is defined.  Stanford was asked their preferred deploy platform and they indicated that AWS was preferred.  
    • Greg will work with Dave when he starts work on containers and tester and sounding board
    • CloudFormation - Greg has written templates and Lynette is going to test these out (will document time taken). Hope to find anything missing in template or documentation, perhaps some permissions issues will be revealed too that will allow documentation of critical permissions
    • Next Greg will look at prerequisites that need to be set up and work to template these in a helper template
  • 2021-03-05
    • Completed prerequisites template which includes S3 bucket and EFS filesystem - next step is to document instructions and how then to move to next template
    • Greg/Lynette to coordinate Lynette's testing next week - use feedback to refine documentation
    • Then create demo screencast
  • 2021-03-16
    • Working on writing documentation
    • Need to discuss approach with Dave Eichmann.  Good to test run the containerization process.  Greg and/or Lynette will follow up with Dave.
    • Lynette can try out the lookup container next week
  • 2021-03-19
    • Lynette began documenting the deployment to AWS adding in an overview, background knowledge, and architecture sections.  Next is to start looking at how to use the templates.

Developing Cornell's functional requirements in order to move toward linked data

...

• OCLC Linked Data / Entities Advisory Group
  
  • 2021-03-05 See comments above
• 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 - Working through repositories in Renaming of LD4P Repositories
  
  • Created Renaming of LD4P Repositories page to identify Cornell repos, provide instructions, and track progress.
  • ACTION - Huda Khan to look at changing to `main` for LD4P/discovery (and update the Blacklight Cornell fork for LD4P3 to bring in the latest)
  • 3/19: Update: DONE with respect to discovery.  Need to wait on Blacklight upstream for LD4P3 fork
• SVDE Workshop - several attended
  • Impressed by clear presentation of models and active APIs (REST and GraphQL)
  • Expecting models to be fully implemented this summer
  • At some time might want to add module to QA to query against GraphQL
• Authorities in FOLIO
  • Hope to include URIs as part of Cornell FOLIO migration, possible LD4P work

...