9 11 2023 Tech Team Report - QualitativeDataRepository/TechnicalTeam GitHub Wiki

9-11-2023

Logged Tasks

                            Date             Task Hours (Main) Hours (EOLS) Hours (PII) Hours (QDAS)
5-Sep-2023 Reporting, find solution to Keycloak not using custom theme, coord re: status, keycloak config changes on stage 3
6-Sep-2023 TAB Mtg, create branch, merge gb-at-request functionality, deploy to dev, create qdr theme for login page with header/footer/styling, deploy on dev, investigate how to deploy on stage with changed config there. 5
7-Sep-2023 Deploy provider/theme to stage, fix docker-compose, create 5.14-qdr-gb-at-request branch, deploy to stage, investigate keycloak email failures, review profile appearance, try fixes, check adding ldap mail param; fix new prod account per request 5
8-Sep-2023 Run mail update on dev, fix script, update Drupal to write mail attribute, minor cleanup, continue testing, revert changes w.r.t. turning off profiles, add changes to qdr-keycloak repo, fix hardcoding of dev-aws for header/footer/styles.css, run ldap mail update on stage, deploy latest D8, document additional install steps, coord re further testing, ORCID member API reqs, MFA config. 4

Operations

  • TAB meeting
  • Remove specified ldap account on prod (allows that person to re-register and complete login to Drupal/Dataverse)

SSO

  • Create a QDR theme for Keycloak to change background/styling/messages/header/footer, deploy to stage via qdr-keycloak repo
  • Fix qdr-keycloak volume dirs to handle deployment of provider and theme
  • Fix hardcoded dev-aws locations in theme
  • Investigate/fix keycloak email failures - broken by changes to allow creating new accounts from ORCID/Google, fix required redesigning to add a mail attribute in LDAP, changing keycloak config and updating Drupal to populate mail (currently still the same as uid/account name/email still have to match, but a step towards being able to change email). Deployed changes to dev/stage.

Drupal

Dataverse

  • Created branches with guestbook-at-request functionality (merging current qdr code with the GB-at-request PR at IQSS), deployed to dev (5.14-qdr-dev)/stage (5.14-qdr)

AnnoRep

Discussion

  • For ORCID, awaiting word re: potential to use Syracuse credentials to access the ORCID member API which should allow requesting trusted access to email when it isn't public. If not, I have identified how/where we can make text changes to indicate that public email is required.

Plans

  • SSO
    • Support testing as needed
    • Handle ORCID error w.r.t email not being public or add warnings/guidance
  • Fix #113 if possible
  • Matomo - investigate event-level tracking via tag manager, remove non-working google scripts
  • AnnoRep - explore round-trip, configure auto-start and log rotation
  • Ops
    • Clean out old corrupt test datasets
    • check missing globalidcreationdates and fix via /modifyRegistration or alternative
  • Dataverse
    • Track ADA guestbook branch and merge when working, Make PR for guestbook adding datasetversion fix, deploy to stage
    • 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