-
Profile Validation action
- Validation is now done on the server side and can be returned requesting the list of layers throught the API /borehole/profile/layer, action=LIST and extra parameter withValidation=true. (This action will be then used in other situations, like in the workflow progress or general borehole validation), example:
{
"success": true,
"validation": {
"missingLayers": true,
"wrongDepth": true,
"missingBedrock": true
},
"data": [
{
"id": 12293,
"depth_from": 1,
"depth_to": 28,
"msm_from": 1104.7,
"msm_to": 1077.7,
"title": null,
"subtitle": null,
"description": null,
"rgb": null,
"pattern": null,
"validation": {
"bottomOverlap": true
}
},
{
"id": 12294,
"depth_from": 26,
"depth_to": 30,
"msm_from": 1079.7,
"msm_to": 1075.7,
"title": 15201338,
"subtitle": 15001003,
"description": 15201338,
"rgb": [
220,
230,
155
],
"pattern": "15101001.svg",
"validation": {
"topOverlap": true,
"bottomDisjoint": true
}
},
{
"id": 12297,
"depth_from": 31,
"depth_to": null,
"msm_from": 1074.7,
"msm_to": null,
"title": null,
"subtitle": null,
"description": null,
"rgb": null,
"pattern": null,
"validation": {
"missingTo": true,
"topDisjoint": true
}
}
],
"config": {
"title": "custom.lit_str_top_bedrock",
"subtitle": "custom.chro_str_top_bedrock",
"description": "custom.lit_pet_top_bedrock"
}
}-
REST API Changes:
action: GET /api/v1/borehole: kinds is removed from the borehole's stratigraphy subelement array. It will now have only one kind. example:
{
"success": true,
"data": {
"id": 948,
// ...
"stratigraphy": [{
"id": 1860,
-- "kinds": [3000], // before
++ "kind": 3000, // now
"name": null,
"primary": false,
"layers": 0,
"date": null
}],
// ...
}
}-
Added Support for Minio
- Users can now use minio instead of Amazon S3 for storing the files.
-
Async Export
- Export action is done asychronously.
-
Export and Import
- Export of data and files that later can be used to be imported into another bdms instance. Import can add data to an exisitng workgroup or they can be added to a read only supplier workgroup. Importing data into this kind of workgroups overwrite all existing data.
-
Borehole copy
- A borehole can be copied into the same or other workgroups. All field are copied exept of the coordinates and altitude.
-
New REST API:
/api/v1/user/workgroup/edit
- ACTION=LIST_SUPPLIERS return the suppliers list
-
REST API Changes:
- GET borehole returns also information about data suppliers (import feature), and author fullname.
- Fixed wrong status in the editor grid page
-
Borehole identifiers multilanguage
- Identifiers can be created and modified in each supported language.
-
Text content management
- This feature is developed to handle multilanguage text (title and body) contents. Currently this feature is used to manage the text displayed in the login screen of web-bdms. (some default text is added in the databse)
-
Handling database update process on upgrade
- The service will check the current version of the database and apply the required changes automatically if the
-
Feedback:
Added new REST actions to handle user feedbacks.
-
Terms of service:
Added new REST actions to handle user agreements on terms of service.
-
Login as viewer:
Guest users can now access with the VIEW role.
-
Attachments:
You can now upload files attachments for each borehole on a AWS S3 Bucket.
-
New configuration options:
-
To configure the file repository some options have been added to configure the AWS S3 Bucket (file_repo, aws_bucket, aws_credentials)
-
feedback can be send throught and SMTP server to a configured email address.
-
-
New REST API:
/api/v1/feedback
- ACTION=CREATE logged-in user can send a feedback message
/api/v1/terms
- ACTION=ACCEPT logged-in user accept the current terms of service
- ACTION=GET get the currently valid terms of service.
/api/v1/terms/admin (admin users only)
- ACTION=GET Get the current draft terms of service.
- ACTION=DRAFT Admins can update the current terms of service flagging it as draft.
- ACTION=PUBLISH Promote the draft of terms of service to go public.
/api/v1/borehole
- ACTION=LISTFILES list all files with less metadata linked to a given borehole
/api/v1/borehole/edit
- ACTION=LISTFILES list all files metadata linked to a given borehole
/api/v1/borehole/edit/files
- ACTION=ATTACHFILE (multipart/form-data) and attach files to existing boreholes
- ACTION=DETACHFILE unlink an uploaded file from a borehole
- ACTION=PATCH update metadata of a file
-
Database changes:
To handle the new attachments feature, two new tables were added to the schema bdms: files and borehole_files
-
Simple Import with CSV:
As editor, importing new data using csv now handles more fields. In particular you can import easily a list of boreholes using this columns descriptors:
- location_east (numeric): mandatory
- location_north (numeric): mandatory
- public_name (text): mandatory
- location_z (numeric): optional
- original_name (text): optional
- project_name (text): optional
- drilling_date (text): optional
- total_depth (numeric): optional
- top_bedrock (numeric): optional
- remarks (text): optional
Note: The column order can be exchanged.
-
REST API Changes:
CSV importer API path has been changed from '/api/v1/borehole/upload' to '/api/v1/borehole/edit/import' and the POST-ed action param changed from 'UPLOAD' to 'IMPORTCSV'
Install boto3 in your python virtual env
source venv/bin/activateUpgrade the postgresql schema by running this SQL script:
psql -U postgres -d bdms \
-h localhost -p 9432 \
-f assets/sql/1.0.0_to_1.0.1-RC1.sql