Roadmap to Metamod 2.4, "Osisaf"

Minutes of meetings between Heiko and Egil, 2009-12-03 and 2009-12-04.

Objective

The Osisaf-project wishes to use Metamod for search and serve of data as http or opendap, but the most important users of Osisaf want to have data in well-defined places on a ftp-server. To avoid data-duplication, it is therefore important that Metamod leaves full control about data-placement to the data-production step. Metamod should not move any Osisaf-data, or set requirements to data-names.

Implementation ideas

A independent upload task will be written. This task will be triggered based upon an url which is:

http://metamod.../...?dataset=...&dirkey=...&filename=...&filename=...

Calling this url will extract the metadata from the files named by filename and add the metadata to the dataset. The dirkey is used as a password and needs to be set up when setting up the dataset. The data-files need be uploaded to the final data-store (ftp-server) before triggering that task. This task will only harvest metadata, but not move any data.

Timeline

Tentative date: 2010-01-15

Possible Changes for Metamod 2.5

There are some thought about switching the internal map-search to a standard PostGIS based map-search. This would solve bug 45, and improve the change of projection in other implementations of Metamod.