Skip to content

9 9 2024 Tech Team Report

Jump to bottom
qqmyers edited this page Sep 9, 2024 · 3 revisions

9-9-2024

Logged Tasks

                            Date             Task Hours (Main) Hours (EOLS) Hours (PII) Hours (QDAS)
26-Aug-2024 Reporting, mtg, start last name code 2
27-Aug-2024 Add last name handling to Drupal, start testing, coord re: deploy tomorrow, add banner 3
28-Aug-2024 Deploy all to prod, work-around broken Drupal deploy, find/fix Keycloak yml bugs, investigate login failures/odd test accts in prod 4
3-Sep-2024 Update PID relationship PR, fix typos in properties, coord re reauthenticating options, fix PID/MDC #10708 test 1
4-Sep-2024 QDR TAB mtg, start investigating why select2 works differently in Dataverse, coord re: Gen3 interview 3
5-Sep-2024 Investigate a11y issues with ROR, find/fix tabindex for main display, fix getting cursor in text box, add mutator to set/reset tab for clear button, test w/axe&wave, fix label issue with Cvoc 7
6-Sep-2024 Update dev/MFA branches to latest IQSS/develop, add cvoc label fix, account create constraint failure logging to v6.3, deploy to stage, update people.js to mirror ror changes, debug issues, deploy to dev/stage, merge latest into DataCite md PRs per reviewer request, add cvoc label update to author cvoc PR (v6.4), Gen3 interview 7

Operations

  • Deployed v6.3-qdr to prod with updates to all components
  • QDR TAB mtg

SSO

  • Started adding lastname and MFA opt-in to Drupal registration form
  • Investigate Dataverse account/access before reg/terms of use accepted. Looks like the auto-account creation in the passive login to Dataverse is not checking the terms accepted flag, and, due to the fact that OIDC login is complete prior to finishing Drupal login, one can get in. With the new code to have Drupal call the Dataverse API to create a user, the simplest fix is probably to just drop auto-creating the account. Alternately, or in addition, the OIDC code in Dataverse could check the terms accepted flag as it used to with Shibboleth.

Drupal

  • Investigated but haven't yet found a fix for Drupal deployment failing on prod.

Dataverse

  • Updated open PRs scheduled for v6.4 - the PRs with additional PID metadata had merge conflicts due to the merge of "Dataset Types" functionality, and there were minor typos and test fixes (being caught now as automated integration tests are running correctly again).
  • Investigated/fixed accessibility issues with new ORCID/ROR plug-ins. The Select2 library we use appears to have unresolved issues in its code, but I was eventually able to work-around them by setting up a "MutationObserver" to restore the tabindex whenever Select2 updates/replaces the involved DOM elements. Setting the tabindex didn't shift the cursor to the type-in box when one presses enter, so I added a listener to handle that. I also added a tab stop for the clear button. Lastly, when testing with Axe and Wave, I discovered that Dataverse wasn't correctly associating labels with fields where the external vocab mechanism is used. I fixed that in the Dataverse code and added that fix to an open ext. vocab. PR (scheduled for 6.4).
  • Updated the main develop and MFA branches to be near v6.4 with all of the existing merges. FWIW, v6.4 is expected in the next 2-3 weeks and the bulk of the un-merged PRs are ones that QDR already has.
  • Added additional logging for account creation failures into the 6.3-qdr and develop/MFA branches. That should help in finding any other cases where Drupal fails to create a Dataverse account.

HEAL

  • Had short interview with Gen3 (NSF POSE related). I raised the concern about duplicate DOIs again and pointed out the idea of using signposting, etc. to advertise metadata outputs and data download API calls rather than hardcoding on the Gen3 or Dataverse ends. I also suggested they might want to talk to Sebastian - in general and related to metadata mapping.

TKLabels

AnnoRep

Discussion

  • Drupal deploy failed on prod during the last upgrade. This was after a composer update which I think also caused problems on dev/stage. I think @Seba did something on those machines to fix it, but I'm not sure what.
  • Request for Sebastian's input on #10790 w.r.t. EndNote format

Plans

  • Fix Google login issue when last name isn't provided
  • Get MFA to a usable state w.r.t. on authentication issue #43(MFA, etc.)
  • Shephard relationship type entry in metadata block #44 (more metadata to DataCite, etc.) through testing/review/QA
  • Work towards v6.4-qdr release
  • Background work to change/remove deprecated Drupal modules in prep for 11.0.0
  • 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
Clone this wiki locally