Skip to content

6 10 2024 Tech Team Report

qqmyers edited this page Jun 10, 2024 · 2 revisions

6-10-2024

Logged Tasks

                            Date             Task Hours (Main) Hours (EOLS) Hours (PII) Hours (QDAS)
3-Jun-2024 Reporting, meeting, ARDM slide prep, Investigate/fix dvwebloader issues w.r.t. Crypto libs, check folder assignment 6
4-Jun-2024 Updated several Drupal modules, deploy to dev/stage, finish last ARDM slides, coord, send to Chicago, start updating dvwebloader repo, develop localinstall script 4
5-Jun-2024 Investigate/fix additional path validation error for dvwebloader, discover/fix async script loading issue with sha512 hashes, create multiple dvwebloader PRs with fixes, deploy to dev/stage, document deploy-from-github approach in QDR repo readme, signup for ARDM slack, coord re TKLabels/LocalContext, update DataCite XML PR 5
6-Jun-2024 Presentation, breakout session at ARDM 2
7-Jun-2024 Breakout discussion at ARDM 1

Operations

SSO

Drupal

  • Updated multiple modules on dev/stage

Dataverse

  • Investigated/fixed further issues in dvwebloader w.r.t. failure when paths contain prohibited chars, race condition with sha512 library loading, created PRs for all changes
  • Created a localinstall script for dvwebloader
  • Finalized the DataCiteXML PR and requested feedback from IQSS on changes from old DataCite and OpenAire

HEAL

TKLabels

  • coordinated re: participation in LocalContext's early adopters program

AnnoRep

Discussion

  • ARDM whitepaper continues to evolve - new idea of a Mesh 'card' detailing what standards/APIs a mesh supports to simplify integration. I brought up the downside of minting a second DOI for datasets, but it seems like the interest in having a citable ID for a dataset with full HEAL metadata when that metadata doesn't exist in the original repo, e.g. FigShare, has to be accommodated somehow. ~A mesh should use PIDs to reference datasets and other objects, minting new PIDs when objects aren't already managed elsewhere or where the original repository doesn't support required metadata.
  • FWIW: I had a couple good talks with Anthony Juehne, the program manager for the HEAL Data Platform.

Plans

  • Keycloak update to 24.0.2
  • Finish work on metadata issue, e.g. adding a relationship type entry in metadata block #44 (more metadata to DataCite, etc.)
  • Work on MFA w.r.t. on authentication issue #43(MFA, 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
Clone this wiki locally