Page History

...

• Qa Sinopia Collaboration
  • 2022-04-08 - Lynette out15
    • One new direct access authorities (i.e. Humord) added to QA.  All 3 new authorities for the Norwegian project (i.e. Bibbi, Genre/Form) and Homosaurus are in production Sinopia.
    • Dave still needs to fix of total_number_found to make pagination work to get pagination working again in Sinopia.  Once that is done, it will just feed through to Sinopia without any additional work.
• Best Practices for Authoritative Data working group (focus on Change Management) 
  • 2022-04-0815
    • Met with the group and had a long conversation about the complexities of identifying the edges of the graph for delete.  LOC gives the edges by using blank nodes.  Getty does not use blank nodes and returns a significant amount of data beyond the subject entities triples.  Possible recommendations: 
      • delete only triples matching <subject_uri> ?p ?o
      • plus any triples in the same namespace that are in the return graph AND that are now orphaned (This could have unintended consequences.)
    • Had meeting earlier in the week. Reflected on different styles of activity streams (Getty and LC). Similar complexities but different means of consuming them. Discussion of the difficulty of dealing with deletes
• Containerization 
  • 2022-04-0115
    • Containerizing the QaServer
      • Added GithHub actions to sync authorities and locale customizations from GithHub repo to S3.  Fully tested with -int and working as expected.  Testing on -stg images are built with the env variables that support customization. (LD4P/qa_server_container)
      • created cul-it/qa_server_aws_deploy repo to hold our customizations.  It is currently just a fork of the LD4P/qa_server_aws_deploy repo.  The plan is to put the set of authority files we support in this repo, and the footer customizations.  Explored a github action that will copy these customizations to our S3 which should be picked up automatically.  This provides a way for us to update authorities over time without having to manually copy them to S3.
      • Lifecycle questions still working on...
        
        • how to update out local deploy when the image changes?  This is proving tricky.  There is a way to have the actions that build the images announce the change using repository_dispatch, but so far, it looks like the only place that can process that is the LD4P/qa_server_container repo using a webhook.  What we want is all the downstream repos to be able to receive a message that they can process in a github action to update their deploys.
    • Containerizing the Cache Indices
    2022-04-08
    • • and -prod are pending finalization of the deploy process.
      • Added GitHub actions for redeploy for -stg and -prod based on the action Greg wrote for -int.  This will likely address Issue #4, but is also pending finalization of the deploy process for -stg and -prod.
      • The other part of customization is adding ENV vars to drive components included on the monitor status page.  That is being done manually in the file stored on S3.  This is completed for -int, and pending finalization of the deploy process for -stg and -prod.
      • We are doing some renaming of components to make the naming consistent.  There may need to be some adjustment to action scripts once that is complete.
      • Greg setup Pingdom is setup to ping the monitor status page.  It correctly sent a 'site is down' message.  There is a bug in qa_server when the monitor status page is run for the first time in an app. Lynette will debug this and create a new image.  Hopefully it is a straight-foward problem and will be done this afternoon. 
      • There is a problem with precompiling of assets on -int.  Presumably this is a problem in the built image.  Perhaps it will be resolved when the image is rebuilt after resolving the monitor status page bug.  If not, there will need to be some debugging on this issue too. 
    • Containerizing the Cache Indices
    • Lynette and Robbie out this week
    • Greg push tagging changes through could formation, required 19 new permissions. Also worked in github actions to deal with separation of template and container repositories - have this working in integration instance and will work with Lynette to merge PR. Next step is to create a staging environment. Perhaps can get this to production in another week or so. Also writing an FAQ about how infrastructure interacts with container and continuous deployment

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-03-25 Some transitions in team. Useful meeting with Jenn, Frances, Nick, and Darcy to decide what needs to be provided to build queue. Mockups look good and allow filtering on types of change (new, deleted, updated). Quite different indexing requirements for data maintenance vs discovery

...