2018 pycsw 3 roadmap dev meeting
Start: Monday 09 July 2018 0600h UTC
End: Wednesday 11 July 2018 1500h UTC
@kalxas @tomkralidis
- review of current 2.x tickets
- review of limitations/gaps of 2.x
- review of future requirements for 3.x
- review / relation to forthcoming OGC CSW 4 efforts
- 3.x roadmap definition
- 3.x roadmap definition (continued)
- draft model
- implementation plan
- meeting review (results, next steps, reporting)
- OGC CSW 4 efforts slowly building
- so far it appears that CSW 4 will be similar to WFS 3 (OpenAPI, JSON) with a different information model
- extension mechanism for CSW 4 (search)
- similar architecture as WFS 3 (clean break from traditional OGC service architecture)
- should pycsw 3 be a clean break as well?
- should pycsw 3 support ONLY CSW 4 or previous versions of CSW as well?
- should pycsw 2.x support ONLY CSW 3 and less?
- provide an autorun functionality to run pycsw by loading a directory of metadata
- pygeoapi provides WFS 3 server functionality
- pycsw 3 could be a pygeoapi implementation with additions for CSW 4 specifics
- information model
- search
- backends: PostGIS, SQLite3, ElasticSearch with default being SQLite as in pycsw 2.x basically what we discussed was that we need to keep Postgres around, most production systems use it
- we need to make the SQLite3 fulltext story better
Next meeting should happen in about 4 weeks
