wps-toolbox merge requestshttps://git.scc.kit.edu/aw6481/wps-toolbox/-/merge_requests2020-07-08T10:48:15+02:00https://git.scc.kit.edu/aw6481/wps-toolbox/-/merge_requests/2implementing metacatalog API2020-07-08T10:48:15+02:00aw6481implementing metacatalog APIThe first of possibly many changes to wps_toolbox to implement the new `metacatalog.api`
The new api should work more properly and some of the really dirty should be removeable from wps_toolbox now.
It needs a connection to the database...The first of possibly many changes to wps_toolbox to implement the new `metacatalog.api`
The new api should work more properly and some of the really dirty should be removeable from wps_toolbox now.
It needs a connection to the database. to connect, the `metacatalog.api.connect_database()` function takes any input that is accepted by [sqlalchemy engines](https://docs.sqlalchemy.org/en/13/core/engines.html). For convenience, a connection string can also be saved using metacatalog cli. Then the string is saved to `~/.metacatalog/config.json` with the password **in cleartext**.
Thus, you should decide how and if we store the connection into a file. If not, all wps functions that need database connection would need a connection string or open session to the db.
You can see that the json for metadata and the pickle for the data are created here. This would therefore be the perfect place to add a function that actually creates these files and the json template as a common interface for the structure and contents it needs. e.g. data types etc.
Please check the stuff and comment if you have sugegstions.fq3407fq3407https://git.scc.kit.edu/aw6481/wps-toolbox/-/merge_requests/1Dev hydrobox2018-08-23T13:07:17+02:00aw6481Dev hydroboxNew untested version of the WPS processes.New untested version of the WPS processes.