11 23 2020 Tech Team Report - QualitativeDataRepository/TechnicalTeam GitHub Wiki
11-23-2020
Logged Tasks
| Date | Task | Hours (Main) | Hours (EOLS) | Hours (PII) |
|---|---|---|---|---|
| 16-Nov-2020 | Report, meeting, update sitemap module on dev/github | 2 | ||
| 17-Nov-2020 | Investigate DataCiteStats, send support email, investigate access logs, initial 5.2 merge, try drupal/upgrade_status:^3.0@alpha | 5 | ||
| 18-Nov-2020 | Prod 5.1.1 update, D8 8.9.9 security update to dev/stage | 4 | ||
| 19-Nov-2020 | Fix terms redirect bug | 1 | ||
| 20-Nov-2020 | Fix redirect to dataset after login/t&c, adjust D8 widths to ~match DV, handle media sizes | 3 |
Summary
Drupal
- Update to xml sitemap module and security update to core (8.9.9) deployed to dev/stage
- Fixed bugs in redirect after accepting the terms and conditions (e.g. during registration) - both Drupal and Dataverse changes
- Adjusted the Drupal8 width and window-resize styling to more closely match how Dataverse adjusts with size, which helps keep the header menu aligned
- Temporarily installed the drupal/upgrade_status:3.0alpha module - it shows the list of modules that are compatible/have compatible versions/need fixes and can identify at least some problems. Should be useful in preparing for 9.x migration.
Dataverse
- Deployed 5.1.1 to prod
- Investigated DataCite Stats page/API and log analysis tools for #50 (tracking DOI resolution failures)
- Made an initial merge with Dataverse 5.2
Discussion
- Based on communication with DataCite: their Stats API only covers registrations, so the only way to get resolution failures is to scrape the stats webpage. Further, they only report the top-ten failures per month, and they are currently ~ 4 months behind in reporting (June is the last month available, they're hoping to catch up 'soon'). I can go ahead with trying to scrape the page, but it looks like getting a comprehensive list from them won't work/ the result won't be any more detailed than what's on their page.
- After looking through some log-reading options, its my guess that generating a specific log with DOI access failures with the info we want will probably be easier/faster to do. Should still be able to set up a cron job to email the results.
- Deploying to prod today (Nov 23) revealed problems with the auto-deploy scripts. Have contacted Seba in slack - should verify we have a fix when we meet.
- v5.2 Dataverse changes to using a 'kebab' menu for several functions and changes how previews are managed (previewers and 'explore' tools are separate categories, UI changes to reflect that). I've done an initial merge, but I/we need to go back and see how the new features interact with QDR's prior customizations (the use of words like 'View Image' instead of the eye icon is perhaps the most obvious). In the first merge, I've probably removed some of our custom code which, if we decide it's still needed, would need to be restored. (e.g. for previewers, the QDR change to show 'View Image' was partly because Dataverse otherwise showed the eye icon with a menu, usually with only one choice. Now that there's an explore category, it would be easier to always assure there's only one previewer.)
Plans
- Deploy latest fixes to prod, debug/fix any issues
- #50 - add specific logging to Dataverse, setup to screen scrape from DataCite.
- v5.2 integration
- Issue Queue
Still TBD:
- Drupal 9/composer 2