Skip to content

5 22 2023 Tech Team Report

Jump to bottom
qqmyers edited this page May 22, 2023 · 2 revisions

5-22-2023

Logged Tasks

                            Date             Task Hours (Main) Hours (EOLS) Hours (PII) Hours (QDAS)
15-May-2023 Reporting, add caching for isThumb avail, test, add method to save failed flag, deploy to dev, cherry-pick all to v5.13, deploy to stage, check for storJ files on stage, provide testing examples, investigate prod draft dataset not showing curation label in search, investigate stage outage re: storJ, restart, coord. investigate Keycloak theming and profiles, investigate ORCID and Drupal errors in Keycloak log. 6
16-May-2023 Add givenName to Keycloak profile and map it to LDAP, work through some LDAP errors, try removing posixAccount class/uidNumber, etc. in LDAP to avoid needed a unique number from Keycloak, create branch for thumb updates, start adding api calls to reset flag, weekly mtg. 5
17-May-2023 Work through removing posix in ldap, test, address accessibility #114/#115, investigate #113, add api calls for thumb failure flag, cleanup, deploy, deploy Drupal ctools/metatags to dev/stage, coord re: progress spinner remaining when large dataset is updated. 6
19-May-2023 Investigate backup-related failure in infra channel, check prod backups, fix drupal backup 1

Operations

  • Provided examples of storJ files on stage, thumb failure examples, for testing
  • Investigated prod dataset not showing curation label in search - some indexing failure, no obvious cause, reindexed and working now
  • Investigated stage outage due to storJ, restarted
  • Investigated backup errors being auto-reported in the #infra channel. The database backups are still being created, so the warning appears to be a problem in the warning system itself rather than a backup problem.
  • In reviewing backups, I noted again that the backup script is trying to get the 'drupal' database (which doesn't exist) rather than the 'drupal8' database we use. I took a snapshot backup of drupal8 on Friday and tried to change the script but it appears to be managed and thus gets reverted to the incorrect copy before the script runs.

SSO

  • Investigated Keycloak theming and declarative profile functionality - started adding new fields (e.g. givenName) and tried mapping to LDAP.
  • Removed LDAP dependence on posixAccount fields (which we didn't use)
  • Continued investigating LDAP errors when trying to create new account via Google

Drupal

  • Deployed new ctools and metatag modules to dev/stage

Dataverse

  • Added caching of the isThumbmnailAvailable call to minimize store access during page display, added storage of thumb generation failure flag and api calls to reset it, cleaned up code, deployed to dev, cherry-picked changes to the v5.13 branch, deployed to stage
  • Investigated/fixed accessibility issues #114/#115, investigated #113
  • Started investigating issue where progress spinner doesn't go away after a dataset update (but is gone when opening same dataset in a new tab).

AnnoRep

Discussion

  • FYI: I'll be away Friday-Monday (holiday).
  • Are there QDR/HEAL slides or background material that I can use in the DCM talk?

Plans

  • Fix #115 if possible
  • Check on source of managed backup script and see if it can be fixed in github.
  • Deploy indexing fix to prod and reindex
  • SSO - continue to explore/build OIDC options
    • Handle failure for Google login when no local account (unless/until supporting new accounts from Google)
    • Investigate ways to simplify user interface (multiple clicks to get through Keycloak)
    • Restore redirect to current page after login
    • Investigate creating a new account via Keycloak, i.e. starting from a Google or ORCID account
    • Try ORCID?
    • Investigate automating recovery from Drupal logged in /Keycloak&Dataverse logged out
  • Matomo - help with transition from Google
  • AnnoRep - explore round-trip, configure auto-start and log rotation
  • Dataverse
    • Make PR for accessibility fix (once finalized)
    • Make PR for guestbook adding datasetversion fix, deploy to stage
    • Continue towards guestbook at request based on ADA's original work
    • Popup info accessibility - IQSS likes the recommendations from the source I linked to, so this can be implemented along those lines.
  • Drupal - v10 - review compatibility and start updates.
  • QDAS Previewer
    • Updates per request
    • Investigate writing aux file/previewing lower-sensitivity version and/or other write options
  • TBD: FRDR Security
Clone this wiki locally