3 8 2021 Tech Team Report - QualitativeDataRepository/TechnicalTeam GitHub Wiki

3-8-2021

Logged Tasks

                            Date             Task Hours (Main) Hours (EOLS) Hours (PII)
1-Mar-2021 Report, Meeting, check backups, investigate blacklisting UT Dorkbot 2
2-Mar-2021 Find tmpreaper, review transaction-related QDR code (hoping to reduce fork) 1
3-Mar-2021 Webform security update to dev/stage, investigate build fails/delete old d8 builds, TAB mtg, review Beyond Bag profile 2
4-Mar-2021 D8 to prod, update entity-ref module on dev, fix ldap-only account, investigate fix for partial account creation 2
6-Mar-2021 Update modules on dev, deploy D8 to stage, make space on stage, style fixes, deploy to dev/stage, merge with IQSS/dev, merge file replace PR 4
7-Mar-2021 Fix merge/style issues 3

Summary

Dataverse

  • Made style fixes to checkboxes, list items per slack discussion (and a few more I found)
  • With v5.4 approaching, I did a merge of our dev branch with the latest from IQSS. 5.4 has a variety of style updates that once again made merging interesting. Ones that are worth some testing/comparison with 5.3:
    • IQSS ~adopted/adapted our hiding of the file fixity hashes - they decided to add a few chars from the start and end of the hash in addition to the icon and to make the 'copy to clipboard' icon change to a checkmark when it's used. We could potentially adopt this and drop our custom code. (that's how it is on dev now)
    • IQSS made some changes to deal with positioning of the footer that conflicts in areas where I made changes to handle Schema's background panel. I think I've adapted our changes, but it would be good to test for footer positioning, any buttons/other items hidden behind the background gray panel (e.g. behind the file table), that the pop-up menu in the file table is in front of other elements.
    • IQSS made some changes to responsiveness and word-wrapping. I fixed one conflict with our recent update for long file titles, but verify that works as expected and watching for other issues with resizing the window would be good.
  • I also took a brief look at some of the changes we made w.r.t. transaction issues (a call to find the root dataverse failing) to see if I could fit it to the theories IQSS has for other rare failures. Not sure there's a conclusion yet but some of the discussion may help find a way to replace our custom fix.

Drupal

  • Updated the webform module with a security update and then deployed across all machines after testing
  • Updated several modules with routine updates - on dev and stage

Operations:

  • Verified that our recent backup testing did not cover S3 (which has 99.999999999% durability)
  • Continued to monitor disk space - (prod / usage has increased 1% to 74%), cleared space for D8 builds on dev/stage
  • Suggested tmpreaper as a possible alternative to a cron job for managing temp dirs
  • Quick check to verify that we should be able to blacklist UT Dorkbot in the PID reports
  • Fixed a broken account (registering but never logging in leads to an account in ldap but not in Drupal (previously known) that then makes it impossible to request a new password (not recognized as an issue before). Did some quick checking to see how we might avoid this state in the future.
  • TAB Meeting, discussed ORCID integration, briefly checked the Beyond Bags profile effort (would be useful to follow up with Tim)

##Discussion:

  • Plan for automated cleaning of older files in /tmp (which tool, who does the work)
  • Should stage be updated to match dev (with ~5.4 changes) or just style fixes that could go to prod ~now?
  • discuss DataCite 4.x support (question from Sebastian)

Plans

  • DataCite updates?
  • Blacklist UT Dorkbot
  • Anno-Rep work -- continue docx parsing to get generate and then store an annotations file (as aux file in dataverse) -- start deploying service on dev once the basics are in place -- support use of Dataverse API as needed

Still TBD:

  • Drupal 9/composer 2/3