== Protocol: 04 March 2010 ==
=== ''What do we want?'' ===

==== User demands: ====

 *  Intuitive user interface
 *  User documentation
 *  Import of data-files
 *  Manual input of data
 *  Table editing
 *  Search functionalities
 *  Definition of table relations
 *  Saving of relations, layers and maps
 *  Import of images as raster layers
 *  Mapping of data layers (including ordering, control of transparency)
 *  Map functionalities (zoom, pan, layer on/off)
 *  On-map editing of layers (point corrections)
 *  Integration of alternative data bases like CBDB
 *  Fast response
 *  Rights management
 *  Persistent tagging of data sources

==== Developer demands: ====
 *  Functional developer environment
 *  Functional admin interfaces
 *  Standardized interface between front- and backend (REST)


=== ''What do we have?'' ===

 *  Spatial data base (potsgres/postgis)
 *  Non-intuitive, but working web-client/server (zope)
   *  Import of formated ASCII-files
   *  Manual table definition and data input
   *  Attribute search
   *  Mapping of one user data layer vs. some standard layers
   *  Map functionalities
   *  Simple rights management
 *  New , more intuitive user interface layout


=== ''What do we still have to do?'' ===

Now (until April 1st):
 *  Setup of developer environment
 *  List and table access via REST
 *  Create and edit functions via REST
 *  Local and global search via REST
 *  Refined access rights management
 *  Implementation of WMS to !GoogleMaps

Soon (until May 1st):
 *  Folder/worklspace structure 
 *  Import of image-files into WMS via frontend
 *  Implementation of GUI function for digitized (XML)-texts
 *  Search and input from maps

Later (with eSciDoc):
 *  User communication 
 *  Publication rules 
 *  Repository interface 
 *  Versioning of data 
 *  Feedback of editions (corrections) to linked external databases

 *  Interface to correlate place names with GIS data