-
Notifications
You must be signed in to change notification settings - Fork 0
1 24 2022 Tech Team Report
qqmyers edited this page Jan 24, 2022
·
1 revision
| Date | Task | Hours (Main) | Hours (EOLS) | Hours (PII) | Hours (QDAS) |
|---|---|---|---|---|---|
| 17-Jan-2022 | Report, mtg | 1 | |||
| 18-Jan-2022 | Read REFIQ-DAS spec/examples/schema | 2 | |||
| 19-Jan-2022 | Drupal investigate sec issue/update core on dev/stage, merge focus updates for deployment | 1 | |||
| 20-Jan-2022 | Drupal - merge dependabot updates by updating other dependencies | 1 | |||
| 23-Jan-2022 | Update version tables dates, fix api token issue, make PRs | 2 |
- Made 2 quick PRs related to prior QDR work:
- Use the releasetime rather than lastupdatetime for the publication date in version tables, which avoids showing versions changed with the 'Update Current Version' as being published at the last update date.
- Leave expired API tokens so that the UI will show a token expired/please update message instead of making the token just disappear.
- Core security update, module updates
- Make gulp/dev-only(not part of the deployed Drupal) changes to get rid of dependabot security warnings
- Went back through spec and examples and read planning google doc
- Dataverse
- popup info accessibility?
- QDAS planning/design/prototyping
- still want to investigate the guestbook responses re version info not being included.
- Anno-Rep work
- Help with deployment to dev
- TBD: FRDR Security
- Other tasks as discussed in strategic planning