tomkralidis on fix-metadata-parsing-typo
tomkralidis on master
fix metadata parsing typo Merge pull request #762 from ge… (compare)
tomkralidis on fix-metadata-parsing-typo
fix metadata parsing typo (compare)
kalxas on oarec-pg-fts
kalxas on master
OARec: detect PG backend and en… Merge pull request #760 from ge… (compare)
@KoalaGeo this template needs some updating, then: https://github.com/geopython/pycsw/blob/master/pycsw/ogc/api/templates/item.html
Can you open an issue?
@KoalaGeo in the microservice context, pycsw can be deployed with one config per WAF folder, say. You can then map the various HTTP endpoints to the relevant PYCSW_CONFIG
env var. See example of how we used to do this on demo.pycsw.org:
Having said this, here's how we do it these days: https://github.com/geopython/demo.pycsw.org/blob/master/docker-compose.yml (so more containerized).
As well, RFC10 implements the multiple collections support, but only if you have child/parent metadata.
Hope this helps.
Hi everyone: FYI we will be holding a virtual sprint on 23 - 25 May 2022.
The purpose of the sprint will be to focus on features for the 3.0 release
(OGC API - Records support, JSON backend support, custom transformations,
etc.).
More information on the sprint can be found on https://github.com/geopython/pycsw/wiki/Code-Sprint-2022-05
Looking forward to seeing you there!