Skip to content

0.7.0 - Improved Usability
Compare
Choose a tag to compare
@hhund hhund released this 18 Oct 00:35
· 59 commits to main since this release
v0.7.0
This tag was signed with the committer’s verified signature.
hhund Hauke Hund
GPG key ID: 15A40D58B4BF6C78
Verified
Learn about vigilant mode.
7de3bb8
This commit was signed with the committer’s verified signature.
hhund Hauke Hund
GPG key ID: 15A40D58B4BF6C78
Verified
Learn about vigilant mode.

General remarks:

  • This release is compatible with the Data Sharing Framework version 0.9.0. This release does not work with older versions of the DSF.
  • See NUM-CODEX internal mail communication for upgrade deadlines, especially regarding expiring client certificates of the GTH in the test- and production environments.
  • To Update an existing DSF 0.7.0 installation, please see the 0.7.0 -> 0.8.0 Upgrade Guide.
  • To Update an existing DSF 0.8.0 installation, please see the 0.8.0 -> 0.9.0 Upgrade Guide.
  • For a fresh deployment please see the NUM‐CODEX DSF 0.9.0 Deployment and HiGHmed DSF 0.9.0 Deployment guides.
  • Additional information about the NUM-CODEX data transfer process plugin can be found int the repositories Wiki.

Features include:

  • The trigger process has been reworked. When started the trigger process, will signal existing process instances to stop executing.
  • The process timeouts between the Data Integration Centers (DIC) and the Gecco Transfer Hub (GTH) as well as between the GTH and the Central Research Repository have been increased to support validation of larger data-sets at the CRR.
  • The log level for some of the startup messages during validation support initialization has been reduced.
  • A validation result summary has been added to the completed Task resource of send process executions (including dry-runs). The summary includes the number of resources validated successfully and the size (in bytes) of the resulting encrypted transfer bundle.
  • An automatically send e-mail can be enabled for successful send process dry-runs. The mail will be send to the default recipient mail addresses configured in the DSF and will contain the completed Task resource for the dry-run execution.

Process released in the binary assets and GitHub Packages Maven Registry:

Stand-alone validator release in the binary assets:

Issues closed:

  • Send Mail if Dry-Run Successful #107
  • Upgrade to DSF 0.9.0 #100
  • Add a Validation Result Summary To the "start-data-send" Task Output #95
  • Add a Warning Every Time the Stub Implementations Are Called #94
  • Reduce Log Level at Startup #93
  • Increase Process Timeouts #92
  • GeccoFhirClientStub Throws Error #91
  • Only one active instance of trigger process #90
Assets 6
Loading