| 98 | | ''What do we want?'' |
| 99 | | |
| 100 | | User 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 (including ordering, control of transparency) |
| 111 | | * Map functionalities (zoom, pan, layer on/off) |
| 112 | | * On-map editing of layers (point corrections) |
| 113 | | * Integration of alternative data bases like CBDB |
| 114 | | * Fast response |
| 115 | | * Rights management |
| 116 | | * Persistent tagging of data sources |
| 117 | | |
| 118 | | Developer demands: |
| 119 | | * Functional developer environment |
| 120 | | * Functional admin interfaces |
| 121 | | * Standardized interface between front- and backend (REST) |
| 122 | | |
| 123 | | |
| 124 | | ''What do we have?'' |
| 125 | | |
| 126 | | * Spatial data base (potsgres/postgis) |
| 127 | | * Non-intuitive, but working web-client/server (zope) |
| 128 | | * Import of formated ASCII-files |
| 129 | | * Manual table definition and data input |
| 130 | | * Attribute search |
| 131 | | * Mapping of one user data layer vs. some standard layers |
| 132 | | * Map functionalities |
| 133 | | * Simple rights management |
| 134 | | * New , more intuitive user interface layout |
| 135 | | |
| 136 | | |
| 137 | | ''What do we still have to do?'' |
| 138 | | |
| 139 | | Now (until April 1st): |
| 140 | | * Setup of developer environment |
| 141 | | * List and table access via REST |
| 142 | | * Create and edit functions via REST |
| 143 | | * Local and global search via REST |
| 144 | | * Refined access rights management |
| 145 | | * Implementation of WMS to !GoogleMaps |
| 146 | | |
| 147 | | Soon (until May 1st): |
| 148 | | * Folder/worklspace structure |
| 149 | | * Import of image-files into WMS via frontend |
| 150 | | * Implementation of GUI function for digitized (XML)-texts |
| 151 | | * Search and input from maps |
| 152 | | |
| 153 | | Later (with eSciDoc): |
| 154 | | * User communication |
| 155 | | * Publication rules |
| 156 | | * Repository interface |
| 157 | | * Versioning of data |
| 158 | | * Feedback of editions (corrections) to linked external databases |
| 159 | | |
| 160 | | * Interface to correlate place names with GIS data |
| | 98 | * [http://it-dev.mpiwg-berlin.mpg.de/tracs/GIS/wiki/Protocols/04March2010 Protocol] |
