4 29 2024 Tech Team Report - QualitativeDataRepository/TechnicalTeam GitHub Wiki

4-29-2024

Logged Tasks

                            Date             Task Hours (Main) Hours (EOLS) Hours (PII) Hours (QDAS)
22-Apr-2024 Reporting, meeting, check Keycloak sec. issue, continue w/DataCite updates 2
23-Apr-2024 DataCite design/planning 3
24-Apr-2024 Coord/investigate not-logged-in at Dataverse edge cases, DataCite design 2
25-Apr-2024 Coord re: TKLabels, DataCite investigation 2
26-Apr-2024 DataCite refactoring, continue combining OpenAire and QDR changes, documenting issues 7

Operations

SSO

  • Investigate not-logged-in at Dataverse cases - as far as I can tell, they involve having a recent session in Dataverse, logging in from Drupal and then manually navigating to Dataverse again. Looking at a way to delete the session cookie for Dataverse to allow the passive login code to run in this case.

Drupal

Dataverse

  • Continue adapting DataCite export to use OpenAire-style of parsing and to merge QDR changes in the DataCite export into the merged version. FWIW: Decided to replace the current mechanism of swapping strings into an XML template doc with the OpenAire style of directly generating the XML. Keeping track of places where the current DataCite/QDR DataCite/OpenAire code/DataCite XML schema/examples differ and documenting what I've chosen so people can agree/request changes.

HEAL

  • Signed up for the Mesh workshop and two coord meetings.

TKLabels

  • Shared design options doc, suggested trying to get requirements formalized. Nominally there's a TKLabels WG that hasn't met recently. QDR should be involved/could ask for a next meeting if it's a priority to get moving.

AnnoRep

Discussion

  • Interest in NSF POSE proposal participation?
  • HEAL travel?
  • FYI: There are more security notices for Keycloak - should raise the priority of getting to 24.0.3+
  • (From last week) Any reason to keep old branches? (They take space on the Jenkins machine). Unless someone can think of a reason, I'll go ahead and delete anything that's been merged. Most of them are for PRs to IQSS since I've been making most QDR changes directly on the develop branch.
  • Any old accounts (e.g. ones with collisions) to delete from prod before the SSO update? Any preferred mechanism for resolving the collisions (nominally for most I've added '2' at the end of the older account but this pattern (or deleting) doesn't always work, e.g. there are three different info@ addresses that are truly different accounts and not cases where a person has changed institutions (and presumably won't be using their old account).

Plans

  • Work on MFA w.r.t. on authentication issue #43(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