Create a runable version of this code with maven and java 8:
mvn clean package
The JAR file will be created in the /target
folder, for example:
|-target
|---data-model-lib-1.0.0.jar
|---...
With Maven you can include the recent library version as dependency with:
<dependency>
<groupId>life.qbic</groupId>
<artifactId>data-model-lib</artifactId>
<version>version-number</version>
</dependency>
or Groovy Grape:
@Grapes(
@Grab(group='life.qbic', module='data-model-lib', version=<version-number>)
)
Make sure, that you have defined the Github package Maven repository, in order for Maven to resolve the dependency properly:
<repositories>
<repository>
<id>github</id>
<name>GitHub OWNER Apache Maven Packages</name>
<url>https://maven.pkg.github.com/qbicsoftware/data-model-lib</url>
<releases><enabled>true</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</repository>
</repositories>
A Nanopore NGS measurement output is delivered to us as a nested folder structure, following this model:
For usage examples, see the usage documentation.
For directory examples, see the JSON example files provided for the unit tests.
The Nanopore data structure is saved in an openBIS 18.06.2 database. An overview of the openBIS data model and the location and entity relationship of the Nanopore data stucture within it can be seen in this diagram:
A NF-Core pipeline directory output is provided as a nested folder structure, following this model:
For usage examples, see the usage documentation.
For directory structure examples, see the JSON example files provided for the unit tests.
The following figure displays the current openBIS model of a nf-core pipeline result dataset:
A MaxQuant directory output is provided as a nested folder structure, following this model:
For usage examples, see the usage documentation.
For directory structure examples, see the JSON example files provided for the unit tests.
The following figure displays the current openBIS model of a MaxQuant result dataset:
DTOs are objects that we pass around crossing architectural boundaries. They don't contain any business logic, they are just representing data.
This DTO collection contains classes, that represent real world life-science domain data assets.
The following figure describes the entity relation of the imaging DTOs.
Please have a look at the detailed JavaDoc class description of the DTOs.
The following figure describes the entity relation of the DTOs related to Offer Management.
Detailed Information can be found in the GroovyDoc class description of the DTOs.
This work is licensed under the MIT license.