2 7 2022 Tech Team Report - QualitativeDataRepository/TechnicalTeam GitHub Wiki
2-7-2022
Logged Tasks
Date | Task | Hours (Main) | Hours (EOLS) | Hours (PII) | Hours (QDAS) |
---|---|---|---|---|---|
31-Jan-2022 | Report, QDAS prototyping, All-hands mtg | 1 | 3 | ||
1-Feb-2022 | QDAS - fix example from spec, add error handling in js, investigate/fix replace file issue, fix edit file metadata acc. Issues. | 1 | 3 | ||
2-Feb-2022 | Investigate Google search issue/add patch, fix failing URL redirects in Drupal db, deploy file replace fix to prod. QDAS- add table, explore style/rendering possibilities | 2 | 3 | ||
3-Feb-2022 | Drupal update to 9.3.4/view module update, investigate login fails, QDAS source/selection table | 1 | 3 | ||
4-Feb-2022 | Merge Tika update, start merge of ~5.10 | 3 | |||
5-Feb-2022 | Finish ~v5.10 merge | 2 |
Operations
- Updated old Drupal aliases that did not specify the status code (now use 301 like newer ones) to fix a Google search issue (dev/stage/prod)
- Deployed file replace fix to dev/stage/prod
- Updated Tika version to 1.28
- Deployed Drupal update to prod including metatags patch
Dataverse
- Fixed issue breaking file replace
- Found/fixed accessibility issue related to file replace/edit metadata view
- Made initial merge of ~v5.10 and multi-license functionality
Drupal
- Added a patch for the metadatags module that was causing errors in the log. (Not clear if these were only being triggered by robots or not.)
- Updated to 9.3.4 and 9.3.5 and updated views module.
- Investigated odd behavior on dev where I was being logged out whenever accessing the Drupal admin menu. I assume this related to some odd cookie state perhaps induced by server restarts, etc., but I did not find a root cause before the issue resolved itself.
QDAS
- Continued proof-of-concept development
- Copied/repaired example file from spec (had malformed GUIDs, dates)
- Added tabular displays/jQuery DataTable
- Added display of Sources and Selections
- Used GUIDs to crosslink from sources to Codes
Discussion
- Is there a QDAS mimetype? Either for the zip file or the xml one? (not a blocker - we can create unregistered ones but better to use what's already there, easy to change later)
- Do we have a full QDAS Zip example I can develop with?
- Noticing some enable cookies messages - if these are seen by others, I may need to update the logic for supressing them (e.g. only allow the cookie test on login instead of only blocking it on logout).
- Any thoughts on QDR license to use with multilicense?
- FYI - v5.10 should be released this month - multi-license is the biggest part of that and probably the biggest thing to test
Plans
- Dataverse
- Deploy mutli-license ~v5.10 for testing on dev/stage
- Popup info accessibility - awaiting IQSS feedback?
- QDAS planning/design/prototyping
- Add display of other fields
- Investigate Dataverse code, add QDAS mimetype support, explore how to alter upload process to unzip QDAS archives as desired.
- Explore referencing files for Sources in previewer (e.g. to open those pages)
- 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