-
Notifications
You must be signed in to change notification settings - Fork 0
1 25 2021 Tech Team Report
qqmyers edited this page Jan 25, 2021
·
2 revisions
| Date | Task | Hours (Main) | Hours (EOLS) | Hours (PII) |
|---|---|---|---|---|
| 18-Jan-2021 | Upgrade dev to Java 11 (install, config default), fix payara J-11 issues, report, merge latest dev, merge 6497-semantic-api, manual build, start testing | 5 | ||
| 19-Jan-2021 | Anno-Rep - update to use new sem api, investigate forgot password redirect, fix 5.3 display issues (transparent dropdown, icon spacing in file table) | 4 | 2 | |
| 20-Jan-2021 | Update dev with D8 core sec. release, commit fixes | 1 | ||
| 21-Jan-2021 | Fix /forgot redirect/message issue, deploy to dev/stage | 1 | ||
| 22-Jan-2021 | Fix 2 more style issues, deploy payara 5.2020.7, DV5.3, and Drupal updates to prod, Anno-Rep - adjust Dataset/md/files code | 4 | 1 | |
| 24-Jan-2021 | Anno-Rep dev | 2 |
Drupal
- Fixed 2 style issues specific to FireFox and resolved the problem of the forgot password process redirecting you to the login page (which you can't use if you don't know your password and which doesn't display the success message indicating you should check your email (because this page is in Shibboleth, not Drupal). This was a complex issue since the initial processing is done by the core user module in Drupal while the last step is our SSO redirect. I didn't find a way to modify an initial redirect by the user module to the Drupal8 user page (which we then redirect to the Shib login page if you aren't logged in), but I was able to add a token to the session when you're going through the forgot password process and to then check for that token when you go to the user page and redirect to the Drupal QDR home page if you have the token.
- Updated Drupal core with a security fix (related to uploading tar files)
Operations
- With Dataverse updating (probably in 5.4) to use Java 11, and to enable use of the RDA-supported API extensions (see Anno-Rep below), I updated the dev machine to run Java 11 and then fixed the issues involved in making Payara run with Java 11. (While GDCC supported updating Dataverse to be Java 11 ready, the deployment at QDR was instrumental in identifying the Payara updates required for anyone who started with Dataverse 4.x or earlier. The instructions for updating are now part of the release notes.)
- Updated prod with the latest Drupal and Dataverse, which included updating payara to v5.2020.7 and changing how Dataverse connects with the database.
AnnoRep:
- To simplify development and enable richer functionality, I updated our dev Dataverse to include the new semantic API (dev supported by RDA). This allows AnnoRep to work with metadata representations mirroring the ORE map file.
- Started updated Java classes to use the semantic API
##Discussion
- With the dev update to Java 11, we now need an analogous update so that Java 11 can be used in the build process. Until then, deploying the latest Dataverse branches to dev require manual compile/install.
- AnnoRep initial implementation - any prep for meeting tomorrow?
- PIDapalooza coord: Any standard slides on QDR or Dataverse? FWIW: Current draft slides (notes: video won't play in Google slides, there are a couple unused slides at the end)
- Anno-Rep work
- Missing values when selecting 'Other' in reg form cause failure rather than a validation issue. Awaiting decision as to whether to make value optional or to add code to validate it.
Still TBD:
- Drupal 9/composer 2/3