2 1 2021 Tech Team Report - QualitativeDataRepository/TechnicalTeam GitHub Wiki

2-1-2021

Logged Tasks

                            Date             Task Hours (Main) Hours (EOLS) Hours (PII)
25-Jan-2021 Report, meeting, AnnoRep - upload file, aux files, convert stub, fix aux file limit to tabular, investigate aux file impl. 1 5
26-Jan-2021 AnnoRep -doc, meeting, setup react/java test project 5
28-Jan-2021 Investigate impacts w.r.t. changes re: institution.name, checksum display 1
29-Jan-2021 Merge various branches with dev for PRs (updating to J11) 1

Summary

Dataverse

  • Coordinated with IQSS concerning changes that would affect QDR customizations: moving institution.name from the Bundle to a property and broadening its use, e.g. optionally for the publisher in DDI metadata files, and showing a truncated checksum with copy to clipboard (shows a few numbers from the hash but otherwise copying from what QDR has). The former is easy to manage while the latter could be a replacement for our custom code.
  • Merged various branches with IQSS/develop, updating our open PRs to use Java 11 and other recent updates.

AnnoRep:

  • Explored the Dataverse aux file functionality and removed a limitation that only allowed them for tabular data files, making them available for use with AnnoRep.
  • Attended meeting to coordinate front-end/back-end design. The discussion was useful and clarified that we're looking at a ~React front-end and looking at the back-end as a separate service. It may not make sense to have as complete a ~wrapper over Dataverse in this case (e.g. for file upload/downloads), but, conversely, a simpler data model could simplify the front-end.
  • Post meeting, I focused on implementing a "Spring-Boot" service, which embeds a Java application server to simplify deployment, and have started adding a web API to access the file conversion/annotation extraction capabilities. Depending on the need from the front-end, I can add more of the functionality to list datasets/documents/data sources and view/edit metadata as needed. (Nominally direct calls to Dataverse can be made, but, if the not-fully-restful API is an issue, I can still wrapper things.)

##Discussion

  • PIDapalooza: Talk seemed to go well but, aside from a couple people asking for the current javascript, there hasn't been other follow-ups. I'm hoping that this will tie into the Controlled Vocabulary metadata discussion in Dataverse and hopefully simplify how we connect with the SKOSMOS service as proposed by DANS/Slava. I also attended Sebastian's talk and some others - overall an interesting crowd and probably valuable to stay connected to.

Plans

  • Missing values when selecting 'Other' in reg form cause failure rather than a validation issue.
  • Prod display issues
  • Anno-Rep work

Still TBD:

  • Drupal 9/composer 2/3