Changes between Version 6 and Version 7 of Protocols


Ignore:
Timestamp:
Mar 4, 2010, 1:59:25 PM (14 years ago)
Author:
fknauft
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Protocols

    v6 v7  
    9494      * export map: as image - some days; as map - 1 week
    9595      * user rights management: at least 2 to 3 weeks
     96
     97== 04. March 2010 ==
     98What do we want?
     99
     100User demands:
     101•       Intuitive user interface
     102•       User documentation
     103•       Import of data-files
     104•       Manual input of data
     105•       Table editing
     106•       Search functionalities
     107•       Definition of table relations
     108•       Saving of relations, layers and maps
     109•       Import of images as raster layers
     110•       Mapping of data layers
     111•       Map functionalities (zoom, pan, layer on/off)
     112•       Integration of alternative data bases like CBDB
     113•       Fast response
     114•       Rights management
     115
     116Developer demands:
     117•       Functional developer environment
     118•       Functional admin interfaces
     119•       Standardized interface between front- and backend (REST)
     120
     121
     122What do we have?
     123
     124•       Spatial data base (potsgres/postgis)
     125•       Non-intuitive, but working web-client/server (zope)
     126o       Import of formated ASCII-files
     127o       Manual table definition and data input
     128o       Attribute search
     129o       Mapping of one user data layer vs. some standard layers
     130o       Map functionalities
     131o       Simple rights management
     132•       New , more intuitive user interface layout
     133
     134
     135What do we still have to do?
     136
     137Now (until April 1st):
     138•       Setup of developer environment
     139•       List and table access via REST
     140•       Create and edit functions via REST
     141•       Local and global search via REST
     142•       Refined access rights management
     143•       Implementation of WMS to GoogleMaps
     144
     145Soon (until May 1st):
     146•       Folder/worklspace structure
     147•       Import of image-files into WMS via frontend
     148•       Implementation of GUI function for digitized (XML)-texts
     149•       Search and input from maps
     150
     151Later (with eSciDoc):
     152•       User communication
     153•       Publication rules
     154•       Repository interface
     155•       Versioning of data
     156•       Feedback of editions (corrections) to linked external databases