-
Notifications
You must be signed in to change notification settings - Fork 0
1 8 2024 Tech Team Report
qqmyers edited this page Jan 8, 2024
·
1 revision
Date | Task | Hours (Main) | Hours (EOLS) | Hours (PII) | Hours (QDAS) |
---|---|---|---|---|---|
18-Dec-2023 | Reporting, meeting, update dev/stage to Drupal 10.2.0, full text index on prod, initial attempt to change listCurationStates to admin role, explore MFA options in keycloak | 5 | |||
19-Dec-2023 | Verify full text success, investigate Keycloak conditional OTP, create new browser flow testing otp_auth attribute, read Auth plugin docs, level of Auth capability | 4 | |||
20-Dec-2023 | Update 6.1-qdr branch, deploy to stage, coord, coord re: OTP options, check Google validation emails | 2 | |||
21-Dec-2023 | Debug/fix prod issue w.r.t. creating new users in ldap - up db size limit, deploy latest Drupal/Dataverse to prod, merge oidc branch into develop for Drupal, open metrics URLs on prod/stage, update stage metrics code, update github to use new gdcc metrics repo, investigate use of email in Keycloak, ways to access ORCID/Google ids, change storJ passwd/use 2FA. | 5 | |||
5-Jan-2024 | Update dev/stage to Drupal core 10.2.1 | 1 |
- Deploy Drupal 10.2.0 to all, 10.2.1 to dev/stage,
- Run full-text indexing on prod after recent update,
- Debug/fix prod issue w.r.t. registration failure - up'd LDAP db size limit,
- Track Google validation issues,
- Opened metrics URLs on stage, prod (closed with change to nginx)
- Change to 2FA for storJ after warning,
- Further investigation of MFA options, otp_auth option to skip/force use of OTP, level of auth option to potentially require OTP when accessing specific datasets,
- Investigate where/if/how email is used as uid in LDAP, Keycloak, Drupal, Dataverse to identify what needs to change to allow email to change over time, and how/where Google and ORCID Ids are available,
- Allowed /listCurationStates report to be run by any authenticated user, showing datasets they can publish, deployed to all machines,
- Updated metrics code on stage, updated github to use new GDCC repo rather than the original IQSS one,
- FYI - checked that January bad PID report with no entries appears to be correct - not related to changing to Payara6, changing paths, etc.
- DCM 2024 - OK to do some cost split again this year?
- Work on authentication issue #43(non-email account id, MFA, etc.)
- Work on metadata issue #44 (more metadata to DataCite, etc.)
- Fix Stata-14 ingest by allowing file inspection during direct upload or adjusting the Stata ingester.
- 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
- check missing globalidcreationdates and fix via /modifyRegistration or alternative
- Dataverse
- Make PR for guestbook adding datasetversion fix
- Popup info accessibility - IQSS likes the recommendations from the source I linked to, so this can be implemented along those lines.
- QDAS Previewer
- Updates per request
- Investigate writing aux file/previewing lower-sensitivity version and/or other write options
- TBD: FRDR Security