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