diff --git a/README.md b/README.md index 117a696..bd42d56 100644 --- a/README.md +++ b/README.md @@ -3,6 +3,7 @@ A **living preview** version is published at: https://main.soilwise-documentation.pages.dev/ A fixed production version (for delivery) is published at: https://soilwise-documentation.pages.dev/ + A fixed **1st prototype version** (for delivery) is published at: https://prototype-1-0.soilwise-documentation.pages.dev/ # Mkdocs diff --git a/tech/docs/technical_components/metadata_authoring.md b/tech/docs/technical_components/metadata_authoring.md index c2d1232..12f86bc 100644 --- a/tech/docs/technical_components/metadata_authoring.md +++ b/tech/docs/technical_components/metadata_authoring.md @@ -8,7 +8,7 @@ ## Functionality -**No implementations are yet an integrated part of the SWR delivery. Metadata authoring and generation is, however, possible using the hale»connect workflows.** +**No implementations are yet an integrated part of the SWR delivery.** Metadata authoring and generation is, however, possible using the hale»connect workflows. ## Foreseen functionality diff --git a/tech/docs/technical_components/metadata_validation.md b/tech/docs/technical_components/metadata_validation.md index d538e06..73ec437 100644 --- a/tech/docs/technical_components/metadata_validation.md +++ b/tech/docs/technical_components/metadata_validation.md @@ -164,20 +164,21 @@ The methodology of ETS/ATS has been suggested to develop validation tests. 5. **Quality Assurance:** Assessing the overall quality of the metadata, including its accuracy, consistency, completeness, and relevance to the underlying data or information resources. 6. **Documentation:** Documenting the validation process itself, including any errors encountered, corrective actions taken, and recommendations for improving metadata quality in the future. -### Technology & Integration +#### Technology & Integration [hale»connect](https://wetransform.to/haleconnect/){target=_blank} has been deployed. This platform includes the European Testing Framework ETF and can execute Metadata and Data validation usign the ETS approach outlined above. The User Guide is available [here](https://help.wetransform.to/docs/getting-started/2018-04-28-quick-start){target=_blank}. The administration console of the platform can be accessed upon login at: . -#### Validating metadata +The metadata validation component will show its full potential when integrated to (1) [SWR Catalogue](catalogue.md), (2) [Storage of metadata](storage.md#storage-of-metadata), and (3) Requires [authentication](user_management.md#authentication) and [authorisation](user_management.md#authorisation). + +#### User Guide When using the ‘Metadata only’ workflow, the metadata profile can be validated with hale»connect. To do this, after logging in to hale»connect, go directly to the setup of a new Theme (transformation project and Schema are therefore not required) and activate ‘Publish metadata only’ and specify where the metadata should come from. To validate the metadata file, upload the metadata and select ‘Metadata only’. Once validation is complete, a report can be called up. [A comprehensive tutorial video on setting up and executing transformation workflows can be found here](https://www.youtube.com/watch?v=U1lxzlUquE8&list=PLoyBfgUelhNOwA_GGkd4hSwDnwNhxGC87&index=3){target=_blank} -The metadata validation component will show its full potential when integrated to (1) [SWR Catalogue](catalogue.md), (2) [Storage of metadata](storage.md#storage-of-metadata), and (3) Requires [authentication](user_management.md#authentication) and [authorisation](user_management.md#authorisation). -### Future work +#### Future work - full development of the ETS, using populated codelists - display validation results in the SoilWise Catalogue diff --git a/tech/docs/technical_components/transformation.md b/tech/docs/technical_components/transformation.md index c38400a..4a3c227 100644 --- a/tech/docs/technical_components/transformation.md +++ b/tech/docs/technical_components/transformation.md @@ -37,7 +37,7 @@ We have deployed the following components to the SWR infrastructure: Another part of the deployed system, [GDAL](https://gdal.org/index.html){target=_blank}, a very robust conversion library used in most FOSS and commercial GIS software, can be used for a wealth of format conversions and can handle reprojection. In cases where no structural or semantic transformation is needed, a GDAL-based conversion service would make sense. -#### Setting up a transformation process in hale»connect +### Setting up a transformation process in hale»connect Complete the following steps to set up soil data transformation, validation and publication processes: @@ -48,13 +48,10 @@ Complete the following steps to set up soil data transformation, validation and 5. Add a new transformation configuration. Note: Metadata generation can be configured in this step 6. A validation process can be set up to check against conformance classes -#### Executing a transformation process +### Executing a transformation process 1. Create a new dataset and select the theme of the current source data, and provide the source data file 2. Execute the transformation process. ETF validation processes are also performed. If successful, a target dataset and the validation reports will be created 3. View and download services will be created if required -To create metadata (data set and service metadata), activate the corresponding button(s) when setting up the theme for the transformation process. - - - +To create metadata (data set and service metadata), activate the corresponding button(s) when setting up the theme for the transformation process. \ No newline at end of file