4 5 2021 Tech Team Report - QualitativeDataRepository/TechnicalTeam GitHub Wiki

4-5-2021

Date	Task	Hours (Main)	Hours (EOLS)
29-Mar-2021	Report, meeting, fix aux file error handling, test with new example file.	1	2
30-Mar-2021	Review IQSS aux file proposed changes, AR UI mockups		1
1-Apr-2021	Debug/fix cron, investigate :InstallationName change points	1
2-Apr-2021	Find D8 reporting, update D8 module on dev, start 5.4 merge	2
3-Apr-2021	Merge latest ~5.4, fix tests, update brand-name related changes	3

Dataverse

Merged latest changes from ~5.4 including adding the new standard mechanism for using a specified 'brand name' instead of the root dataverse collection name in various places (metadata, citation, emails). I went through and removed the QDR custom mechanism (we had the name stored in the properties bundle file and used custom code to use it in the right places, the new mechanism defined :InstallationName and calls BrandingUtil.getInstallationBrandName() where desired, with that function switching from using the root collection to the InstallationName if/when the latter is set.). (FWIW - QDR still uses the brand name in a few more places that IQSS - our changes should address #7750 so I'll make a PR at some point.)

Drupal

Updated the custom search module
Responded to slack request for pointers to Drupal 8 report views (use stats, login history)

Operations:

Changes to Drupal and Dataverse deployed to dev
Debugged and fixed a path issue in the DataCite DOI failure report cron job that caused the monthly report to fail. (This was the first time it ran via cron job since DataCite added new statistics). I re-ran the report to get stats from July-Feb and the May 1 cron job should work.

AnnoRep:

Worked on Dataverse auxiliary file support to fix error handling. With this, and the prior updates to list, delete, catch duplicate file upload requests, etc., we should be set w.r.t. managing annotations and pdfs on Dataverse.
Looked through IQSS discussion of possible changes to aux files, e.g. a proposal to add a new 'category' tag to them - nothing that would be a concern for AnnoRep so far.
Took a quick look at the UI mockups to see if there were any inconsistent assumptions between front and back end work.

5.4 Testing foci:

Deactivate/delete user ($SERVER_URL/api/users/$USERNAME/traces to see if users have done anything that prevents delete)
Brand name versus root collection name in UI, citation, exports, email
replace file in draft (updates to kebab menu, UI logic)
archiving (aside from our fix, workflows had several changes)
Conditionally Required Metadata Fields - now possible to have required children in optional parent fields.

Anno-Rep work -- Make a PR to update aux files (in Dataverse 5.4, they are only allowed on tabular files, multiple copies can be uploaded which then breaks download, no delete, no way to list.) -- Start deploying service on dev once the basics are in place -- Cleanup code and post to annorep repo (I started from a Springboot example project and haven't removed irrelevant code, am considering keeping an in memory db to cache entries) --Investigate additional selectors (e.g. TextPosition) -- Support use of Dataverse API as needed

Still TBD: