02.01.2021 TT Agenda - QualitativeDataRepository/TechnicalTeam GitHub Wiki

People

@nniicc @adam3smith @stahs @qqmyers

Discussion Topics

Admin

  • New month new hours to log

Seba & Jim Coordination

  • Conversation from last week (rehash for Seba)
    • With the dev update to Java 11, we now need an analogous update so that Java 11 can be used in the build process. Until then, deploying the latest Dataverse branches to dev require manual compile/install

Seba

  • Infra re-provision
    • Updates

Jim

Next weeks work:

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

Notes

Jenkins can't handle Java 11

  • but it is backwards compatible so it can go back to Java 8
  • In case we need to rebuild ...

Oracle or OpenJDK

  • Licensing for OpenJDK is fine to update...

In Short: When build button is pushed it needs to build and deploy

  • Java 8 is getting called and not Java 11
  • In Jenkins file is where this is called ... (compiler may need to be updated)

On Dev

  • CSS and JSS files are timing out...
  • Fiber was cut last week in NYC
  • Anyone trying to get to AWS S3 from Comcast was having failures... which looks like issues we see on Dev and Stage ...

Seba

  • Working on problem definition and scope for Infra Reprovisioning
  • Will include some

Back-up

  • Some are silently failing
  • Verification of the DR

ToDo: Getting us (Nic and Sebastian) access to Selenium tests through Jenkins interface

PiD-Palooza

  • Preventing the release of unfinished DOIs at JOSS
  • JSTOR came and was amused / humbled
  • HvS - DANS for 1/2 year - signposting not on DV yet ...

Anno-Rep

  • Useful to have better idea of what frontend requires in terms of API functionality

  • Does it make sense to wrap Dataverse HTTP calls twice ... No

    • maintain encapsulation is our design principle

  • Spring boot - wraps java code like Jedi Server and turns into executable

    • Just click button and its up and running
    • This will be the backend server for React that To can use...

  • What makes react easier is that ... Dataset object with metadata - there are automated means of turning that into json to go smoothly over a webcall

    • You're always working with well defined objects
    • DV api - is only semi-Restful - may be harder to work with in React than To expects...

  • If too hard to handle then Jim can create a wrapper ...

  • To - needs to make an API call to go get X ... This is the DV call,,,, and if he doesn't like what he gets back Jim can wrap it...

    • To is to create a list by 02.02 - and we can point him in the right direction for pulling data out of the DV API

Assigned Tasks / Decisions