-
Notifications
You must be signed in to change notification settings - Fork 0
7 10 2023 Tech Team Report
qqmyers edited this page Jul 10, 2023
·
2 revisions
Date | Task | Hours (Main) | Hours (EOLS) | Hours (PII) | Hours (QDAS) |
---|---|---|---|---|---|
19-Jun-2023 | Reinstall using standard beta12 keycloak, fix python3 issues with drupal deployment, investigate/fix pdf thumb issues on dev/stage/prod, report, meeting | 7 | |||
20-Jun-2023 | Finish thumb improvements, update separate branch in prep for PR, merge latest IQSS develop into QDR dev | 6 | |||
21-Jun-2023 | Create thumb PR, add api docs/notes | 2 | |||
3-Jul-2023 | Catch up, investigate ingest lock issue, coord re no unzip with direct upload, meeting | 2 | |||
5-Jul-2023 | Investigate Matomo config on dev, find/report Matomo (analytics.qdr.syr.edu) server failure, update open PRs | 2 | |||
6-Jul-2023 | Configure Matomo on dev/prod - add module, try two sites/switch to one, add search tracking, investigate tag manager, update Drupal core, metatag, schema, token modules on dev/stage, update dev branch with python updates from oidc branch. | 2 |
- (older) Investigated/Fixed issues on prod with pdf thumbs not being generated
- Check on reported ingest lock issue, coordinate on removing it
- Coordinate on the change to no unzipping due to direct upload being enabled
- Investigated/reported Matomo server outage
- Configured Matomo on dev and prod for Drupal (used new module) and Dataverse to use one site, turned on search tracking
- Investigated options with Matomo tag manager - looks like it will create the type of button-push event scripts we have for Google
- (older) Merged with latest keycloak beta and switched to the standard/non-custom module
- Updated Drupal core, and 3 other modules
- Fixed build for develop branch (needed same python 3 updates as done for the OIDC branch before)
- (older) - Created a branch with various thumbnail scaling improvements including the QDR work to avoid retrying to create failed thumbs
- Updated open PRs
- Matomo has updates that can be auto installed and we may also want to turn on tag manager - can we decide? Who should do this (looks like it can all be done via GUI)
- FYI - looks like all of the small QDR-related PRs will get into 5.14 except for the thumbnail updates which I've still marked as draft
- SSO - continue to explore/build OIDC options
- Handle failure for Google login when no local account (unless/until supporting new accounts from Google)
- Investigate ways to simplify user interface (multiple clicks to get through Keycloak)
- Restore redirect to current page after login
- Investigate creating a new account via Keycloak, i.e. starting from a Google or ORCID account
- Try ORCID?
- Investigate automating recovery from Drupal logged in /Keycloak&Dataverse logged out
- Fix #115 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
- Clean out old corrupt test datasets
- check missing globalidcreationdates and fix via /modifyRegistration or alternative
- Dataverse
- Make PR for guestbook adding datasetversion fix, deploy to stage
- Continue towards guestbook at request based on ADA's original work
- Popup info accessibility - IQSS likes the recommendations from the source I linked to, so this can be implemented along those lines.
- Drupal - v10 - review compatibility and start updates.
- QDAS Previewer
- Updates per request
- Investigate writing aux file/previewing lower-sensitivity version and/or other write options
- TBD: FRDR Security