| | 71 | |
| | 72 | == 22. Febr. 2010 == |
| | 73 | * Discussed Issues: |
| | 74 | - [http://chinagis.mpiwg-berlin.mpg.de/gui_prototype/ CHGIS-GUI actual Version] |
| | 75 | * The use of views was changed on the frontend; it was suggested, that the user only works with tables (editable and noneditable) to reduce the terminological complexity. |
| | 76 | * An option to export tables or layers should be integrated everywhere in the workspace interface to allow easy saving of data. |
| | 77 | * The icon on the main screen should change, if new notifications are available. Notifications should be easy accessible centrally, not in seperated in every workspace. |
| | 78 | * Should changes immediately effect other blocks (which requires a live update routine running in the background), or should there a button for update/refresh views? Other blocks would be affected by this only after pressing this button, but changes maybe not automatically saved. |
| | 79 | * The question of the most suitable order creating layers remains; tow ways were suggested: |
| | 80 | - doing a search, followed by the option to create layers from columns of tables from the search result |
| | 81 | - starting by creating layers |
| | 82 | * A question concerns the subdivision between maps and layers: since layers always require a map, is it appropriate to handle "create layer" as part of the map function, or should layers be created/ edited independently, and just join them in the map? |
| | 83 | - Future functionality of the GIS |
| | 84 | * Another functionality to be integrated would be the option to create maps from pictures/ photos/ drawings etc. (F.e. "Create map from table" - "Create map from picture" as basic options.) |
| | 85 | * Creating a map from text: The idea is, to add a specified text as a resource, and let the GIS script gather the place names from it automatically. This idea needs more specific consideration, but can be kept in mind as a prospective option. |
| | 86 | * The question of user rights and management remains, also concerning a quick release for interested beta testers: Should tables be open to all, or protected, and closed for the public, unless published by the user? How does the user gets the rights of usage? |
| | 87 | * A roespective feature would be an additional interface in Chinese. |
| | 88 | - Proposed timetable (approximately) for implementation of program functionalities into the GUI |
| | 89 | * notes: 1 week |
| | 90 | * create: 1 day (basic), 1 week Layers, 1 week Map |
| | 91 | * image import: much longer ... |
| | 92 | * import from text: 2 to 3 weeks |
| | 93 | * export tables/ views: 1 week |
| | 94 | * export map: as image - some days; as map - 1 week |
| | 95 | * user rights management: at least 2 to 3 weeks |
