8 10 2020 Tech Team Report - QualitativeDataRepository/TechnicalTeam GitHub Wiki

8-10-2020

Date	Task	Hours (Main)	Hours (EOLS)
3-Aug-2020	Report, meeting, check prod php, investigate stage sync options	2
4-Aug-2020	Fix create dates on d8 prod, copy prod dbs for syncing, fix DV description display logic in qdr.theme	3
5-Aug-2020	Sync d8 and dv from prod to stage, update s3 for 3 teasers, configure separate stores for synced and test content, continue debugging mdc endpoint	6
6-Aug-2020	Debug mdc, file endpoints	4
7-Aug-2020	Add tree endpoint, investigate jqtree widget, update error handling, update D8 to 8.9.3	5
9-Aug-2020	Investigate file replace code in Dataverse		1

Metrics:

Fixed bugs in new metrics API endpoints
Updated error handling in the metrics API to return valid messages and appropriate error codes
Added a dataverse tree endpoint (returns a json tree of the existing dataverses) and found a widget to allow it to be diplayed in the dataset-metrics page (i.e. as a way to select which dataverse to show metrics for)
Contacted TDL about their metrics and added the column names for the three sheets in their report (Dataverses, Datasets, Users) to our online metrics spreadsheet

Operations:

Updated Drupal 8 to v 8.9.3 on dev and stage
Fixed some user create dates that were not updated correctly during the migration
Synced Drupal and Dataverse content between prod and stage and configured stage with multiple stores to support testing (read/write to qdr-dataverse-stage bucket) and viewing prod content (from qdr-dataverse bucket once read-only permissions are in place). I also copied prod content for the 3 datasets used in Drupal teasers to stage and configured dataverse to get their content, and the content for datasets published before ~9/18 from the stage bucket (so the teasers work without needing read-only permissions and so that tests editing the content of those datasets can be done on stage if desired). In syncing I removed recent stage testing accounts and brought new prod accounts over, without enabling them on stage (they're viewable in lists of users but you can't login to them). Nominally this is a repeatable process that can be done whenever we want to resync and we can add/remove specific datasets from the stage bucket as needed if/when we need to test with specific prod content.

EOLS:

Started looking into the current design of the /replace API call to understand what changes will be needed to make it work with draft content.

Update dataverse-metrics to show per-dataverse metrics and show buttons to download csv files for any graph
Start work to update the /replace API

and possibly:

Ready for read-only access from stage to the qdr-dataverse bucket - easy test is to preview/download any file from https://data.stage-aws-new.qdr.org/dataset.xhtml?persistentId=doi:10.5064/F6HTXF0H - if it works, the content has to come from qdr-dataverse.
FYI: Metrics discussion - brought up the idea of redesign and expansion with IQSS in tech hour and planning to announce/discuss in community calls this week
FYI: May be away Friday