-
Notifications
You must be signed in to change notification settings - Fork 0
5 23 2022 Tech Team Report
qqmyers edited this page May 23, 2022
·
1 revision
| Date | Task | Hours (Main) | Hours (EOLS) | Hours (PII) | Hours (QDAS) |
|---|---|---|---|---|---|
| 16-May-2022 | Report, mtg, review licenses spreadsheet | 2 | |||
| 17-May-2022 | Start planning postgres/sql update license strategy | 1 | |||
| 18-May-2022 | Create regex queries to separate subclasses, update spreadsheet | 2 | |||
| 19-May-2022 | Investigate other fields, create queries to update main groups, identified a few more with null termsofuse and non-null termsofaccess | 2 | |||
| 20-May-2022 | Make backup of prod termsofuseandaccess table, mappings of entries to released dataset versions, map spreadsheet to specific queries or table ids, coord re: how to manage termsofaccess. | 3 |
- Updated Drupal core and Honeypot module, deployed to dev/stage.
- Cherry-picked Google Archiver updates(performance, error handling)/refactor from new PRs, deployed to dev
- Investigated/documented license terms for published datasets on prod
- Updated spreadsheet to map all entries to a query or termsofuseandaccess id that can be used to make updates
- Identified a few datasets with null termsofuse but termsofaccess
- Made backup of termsofuseandaccess table
- Documented where termsofaccess don't include everything in the termsofuse
- Tested queries to delete termsofuse and add a license, or to move termsofuse to termsofaccess and add a license on dev.
License updates - aside from deciding specific text on a few corner cases, I have one open question: for datasets that get one of the licenses, should the termsofaccess repeat that info (as most do now) given that the request/download dialogs now show the license (used to only show the termsofaccess). Regardless, I think the license updates can be done, but it would be useful to standardize the termsofaccess as we do that.
- AnnoRep - continue to explore/fix docx/pdf github issues
- Deploy updates to dev/stage/prod
- Ops
- Convert prod datasets with custom terms to use QDR licenses/other per discussion.
- Dataverse
- StorJ testing
- Popup info accessibility - IQSS likes the recommendations from the source I linked to, so this can be implemented along those lines.
- QDAS planning/design/prototyping
- Investigate performance of community zip previewer
- Add error handling for format variations
- Assess whether zip access is enough/project/other files need to be cached as aux files, etc.
- Still want to investigate the guestbook responses re version info not being included.
- TBD: FRDR Security
- Other tasks as discussed in strategic planning