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

11-20-2023

Date	Task	Hours (Main)
13-Nov-2023	Reporting, meeting, investigate OIDC offline_access scope, configure DV on dev to accept bearer tokens to API, start debugging validation failure	5
14-Nov-2023	Resolve validation failure, retest, write up OIDC doc for HEAL/Gen3 integration, coord on edits, setup in HEAL slack, coord re: payara6, create new dev6 branch, start fixing merge conflicts.	5
15-Nov-2023	Finish merging 6.x, build war locally, update jenkinsfile, add java 17 to dev, fix tree view for tabular files, make local updates to stage/prod, fix D10 issue w.r.t. qdr_helpful_resources, deploy manually to all machines, download payara6, start looking at differences in config.	5
16-Nov-2023	Work through merging changes in domain.xml, dowload/install Payara6.2023.10 and then 6.2023.11 (just released), worked through mail and network listener updates, tried deploying DV 6.0-qdr-dev, coord w/Seba re: missing db passwd, Java version resetting to 11, need for Java/mvn updates on jenkins machine, restore p5/v5.14-qr-dev for now.	4
17-Nov-2023	Investigate 500 error when adding dataset logo in large storJ dataset, check s3/db changes for manual work-around, suggest api call, coord re nginx/samesite cookie setting, new db user with known password.	2

Fix D10-related issue with the qdr helpful resources module/page, deploy manually to all machines

Start integrating 6.x changes, merge IQSS develop branch into new QDR/dev6 branch, resolve merge conflicts
Build war file locally with Java 17
Install Java 17 on dev, set it to the default Java, investigate/report default changing back to Java 11
Try Jenkins build, fixed some Java version issues in jenkins file, report need for Java17+/newer maven on jenkins machine
Download payara6.2023.10, and then payara6.2023.11 when it came out, install on dev
Investigate differences in the domain.xml config file between payara 5 and 6, create new config for dataverse, debug issues
Add mail config and network listener config to payara6
Try deploying, find/report lack of a known password for dvnuser Postgres account, validate new dv account/password provided by Seba
Restore DV 5.14/payara5 on dev to stop slack warnings
Fixed the tree view w.r.t. displaying the original file name/size for ingested files, made local fixes on stage/prod (a .xhtml file edit)
Investigate 500 error when adding dataset logo in large storJ dataset. Investigate db changes needed to manually set logo, report API option to set it to Sebastian

Investigate OIDC offline_access scope and workflow
Configure Dataverse on dev (via 'feature flag') to accept OIDC access tokens for authentication
Test, debug, write up OIDC doc for HEAL/Gen3 Integration, coordinate on edits
Join HEAL slack channel, shared doc there (Sebastian also emailed the link)

Java version is managed by chef (per Seba), but not per machine. I plan to look into running Dataverse 5.14/payara5 on Java 17 so we can update to Java 17 across the machine before moving to payara6

Finish payara6/Datverse 6.x updates, deploy to dev, stage for testing
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