8 26 2024 Tech Team Report - QualitativeDataRepository/TechnicalTeam GitHub Wiki

8-26-2024

Date	Task	Hours (Main)
19-Aug-2024	Reporting, meeting, update view_slideshow module on dev/stage	1
20-Aug-2024	Investigate oom error on stage, restart payara, find potential improvement/memory savings,	2
21-Aug-2024	Finish/deploy memory improvement for finding roleassignments to stage, investigate user DV account fail - Google w/no last name, investigate fix	3
23-Aug-2024	Deploy Curate fix on stage, continue w/Google name fix	1

Investigated Out of Memory error on stage related to changing a user role - identified a potential improvement (see Dataverse section)

Investigated reported Google account creation failure on stage. Identified that the issue is probably use of a Google account where no last name has been provided. This causes an issue for Dataverse where lastname is a required field. The problem is similar to the issue of ORCID accounts where the email is not available and I'm implementing a similar solution to ask the user for that info as part of social registration.

Investigated memory use in loading role management page - discovered that the algorithm loaded all entries for :authenticatedUsers to find the 1 or 2 related to the current collection. Reverted to the original algorithm, verified with IQSS that no one knows why this change was made (it was part of a big PR to improve efficiency but it looks like this particular change wasn't useful and probably wasn't reviewed closely.) Deployed change to dev/stage.
FWIW: Spent significant time last week for IQSS updating the Curate command (supports the 'Update-Current-Version' publishing option available to superusers) to avoid scenarios where metadata loss can happen. One issue was when DataCite is down - something that we fixed at QDR and had not yet gotten back to the community version - but another was when terms rather than metadata were changed. It's not clear if this was always the case, but it happened at QDR as well. The fix I created both resolves this issue and makes sure that deleting the now unused draft version of the dataset happens in the same transaction so that any failure (from as-yet-unknown bugs) would just leave the dataset unchanged, instead of potentially breaking the dataset. I've deployed this change to dev/stage.

FYI: This is now deployed at demo.dataverse.org as well and ADA/others are testing it.

v6.3 deployment plan?
Avoid use of Update-Current-Version on prod for any change of Terms/License info until the fix is deployed there with our 6.3 update.
Request for Sebastian's input on #10790 w.r.t. EndNote format

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
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