Add changelog

LayerManager · Dec 23, 2019 · f4b46a7 · f4b46a7
1 parent 9131346
commit f4b46a7
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -0,0 +1,11 @@
+# Changelog
+
+## Version 1.1.0 (2019-12)
+- Publish metadata record of [layer](doc/models.md#layer) to Micka on [POST Layers](doc/rest.md#post-layers). Connection to Micka is configurable using [CSW_*](doc/env-settings.md) environment variables.
+- Delete metadata record of layer from Micka on [DELETE Layer](doc/rest.md#delete-layer).
+- Add `metatada` info to [GET Layer](doc/rest.md#get-layer) response, including CSW URL and metadata record URL.
+- [Documentation of metadata](doc/medatata.md)
+- Save write-lock to redis on POST, PATCH and DELETE of Layer and Map
+- Enable to run Layman using multiple WSGI Flask processes by moving information about tasks from memory to redis
+- Use Flask decorators
+- Unify async task names, call task methods in the same way (src/layman/common/tasks.py#get_task_methods, src/layman/common/tasks.py#get_task_methods#tasks_util.get_chain_of_methods, src/layman/celery.py#set_publication_task_info)
diff --git a/README.md b/README.md
@@ -155,7 +155,7 @@ Pipenv is recommended tool for installing **python-level** dependencies. Both Pi
 
 Npm is recommended tool for installing **node.js-level** dependencies. Both package.json and package-lock.json are located in [`hslayers/`](hslayers/) directory.
 
-Next you need to choose how you deploy Layman. As Layman is Flask application, check Flask's [deployment options](https://flask.palletsprojects.com/en/1.1.x/deploying/). Layman is safe to run with multiple WSGI Flask process and with multiple Celery worker processes.
+Next you need to choose how you deploy Layman. As Layman is Flask application, check Flask's [deployment options](https://flask.palletsprojects.com/en/1.1.x/deploying/). Layman is safe to run with multiple WSGI Flask processes and with multiple Celery worker processes.
 
 Configure Layman using [environment settings](doc/env-settings.md). Demo configuration is a good starting point to setup Layman for production, however it needs to be adjusted carefully. First focus for example on
 - [LAYMAN_SETTINGS_MODULE](doc/env-settings.md#LAYMAN_SETTINGS_MODULE)

diff --git a/doc/medatata.md b/doc/medatata.md
@@ -5,7 +5,7 @@ Layman is able to publish partial metadata records to [OGC Catalogue Service](ht
 - [metadata properties guessable by Layman](#metadata-properties-guessable-by-layman) (not yet implemented) 
 - [metadata properties unknown to Layman](#metadata-properties-unknown-to-layman), that are needed to create metadata record acceptable by Micka. 
 
-Although metadata records sent to Micka are partial, they can (and should) be completed using Micka web editor GUI.
+Although metadata records sent to Micka are partial, they can (and should) be completed using Micka web editor GUI. URL of layer's metadata record leading to Micka's GUI is available in [GET Layer](rest.md#get-layer) response as `metadata.record_url` property. To complete metadata records, just open this URL in browser, log in to micka as editor or admin, and complete the record.
 
 Properties listed below contains XPath expression pointing to specific placement of the property inside metadata document. All listed metadata properties on Micka can be synced with metadata properties provided by Layman, whereas only some properties on Layman can be synced with properties provided by Micka (only `title` and `abstract`). No synchronization is implemented yet.