08 24 2020 Tech Team Report - QualitativeDataRepository/TechnicalTeam GitHub Wiki
8-24-2020
Logged Tasks
| Date | Task | Hours (Main) | Hours (EOLS) | Hours (PII) |
|---|---|---|---|---|
| 18-Aug-2020 | Report, meeting, fix metrics per-dataverse links | 2 | ||
| 19-Aug-2020 | Check #49, deploy D8 and DV to prod, switch to direct download, move time series code to Java, add csv option, update dataverse-metrics to show download link | 5 | ||
| 20-Aug-2020 | Complete time series and csv for most metrics, add filenames to csv buttons, add basic styling | 6 | ||
| 21-Aug-2020 | Debug, update graphs | 8 |
Summary
Metrics:
- ~finished work on the API, adding additional timeseries endpoints (files, filesByType, MDC, downloads, unique downloads) with csv exports, moved all time-series generation code to Dataverse (from metrics app), and debugged, improved security checks for attempts to get info about unpublished items (in this public API)
- updated graphics/downloads display, added new graphs/types of graphs for new endpoints, nearing completion
- Updated the issue?PR for the community - see Issue 7177 for a summary of major changes and a link to a detailed spreadsheet about what has been added/changed (sheet2, yellow highlights).
Operations:
- Deployed latest Drupal and Dataverse to production, switching to use direct downloads from S3
- Investigated Issue #49, which we were unable to reproduce Updated stage with the latest Drupal 8 (a module update) and Dataverse (email updated in v4.20-qdr7) in prep for deploying to prod.
Plans
- Complete the per-dataverse time-series metrics displays - hopefully later today
- Start work to update the /replace API
and possibly:
- file DOI reservations
- Drupal 9
- Dataverse 5.0 merging
For Discussion
- A ping about Payara deployment - may be useful by later in the week/early next if merging goes well.
- Dataverse build issue - as noted in slack, Jenkins has started reporting test failures which look like they are caused by not being able to create a dir within /tmp. This isn't fatal, but I don't think it is due to Dataverse code changes.