geonition / geoforms Goto Github PK

It might help and make the content adding easier if it was all done on the same page.

The solution is not going to be without a lot of work but let's do it at some point.

The elements should be named in a more user friendly way.

radiobutton --> select one
checkbox --> select multiple
element --> item
label --> choice

list more name changes here

The questionnaire should be visible to the organization admins so that they can sign in to see questionnaires in creation. There can additionally be a action that will publish selected questionnaires in the Django Admin interface.

When creating new elements from 'Questionnaire page elements' -page, data validation does not work.

To reproduce.

1. Press Add text input
2. Leave e.g. 'Question' text field empty and press save

Start of the error message:
ValueError at /admin/geoforms/geoformelement/add_text_element/

The TextElementModel could not be created because the data didn't validate.

Same happens with all elements

A possibility to add questionnaire widgets as pluggable entities could benefit and increase of available questionnaire formats. Documention of how to write pluggable widgets and functionality for it supported by the app should be planned.

This is an idea.

There is no easy way to know under which link the questionnaire will exist if the user does not know what 'slug' means.

There should be a 'preview' link for the questionnaire which is only open for the administrator until it is marked as 'published'.

and the 'preview' link should be easy to find.

The forms on the left sie of the page does not work when radio buttons and checkboxes are added. Beautify these and make them work visually in a better way.

The questionnaire should have a progress bar to make moving from one page to the other easier and also communicating where in the questionnaire the user is.

Non place based information is not saved in questionnaires. This requires an update first for geojson_rest

The owners should be the only ones with permission to modify the element, page or questionnaire. Other users should be able to see others element, pages and questionnaires and can in this way 'copy' the contents without having to modify other users contents.

In admin interface openlayers.js is loaded using http which causes security errors and prevents map to load in some browsers.

url to openlayers.js is defined in django/contrib/gis/admin/options.py

It is at the moment hard to find the right elements as they have no order in some lists..

This is related to visual preview of the questionnaire. But it would be good if the user could see which colors has already been used when creating a drawbutton.

The site choice should be automatic and not up to the user to choose. As it enables the user to create a questionnaire for other municipalities.

The user should be able to upload icon images in the admin that could then be used for the places positioned by the user.

Make a way to preview a newly created element or existing elements.

The marks should be more modifiable e.g. size should be chosen and maybe a letter indicating which location has been positioned. Some interactivity might also be implemented at the same time.

Close this ticket when a move in this direction has been done.

The admin has to be able to choose which map from the map-layers service to use for the questionnaire.

The drag ad drop might be easier to use and might give extra value for the questionnaire. Although the interaction design might become too complex.

Test this feature.

Automatic inclusion of popup forms should be enabled. The problem with adding elements is just to remember which popup forms needs to be added at the same time,

The color and the geometry type should be obvious by just looking at the button.

There should be a way to mark a question as required. Which would mean that the user could not move forward to the next page if the question has not been answered.

This can be fixed with a help message like a tooltip that follows the cursor. The tooltip can have the help text of what the user should o next.

There should be support for any existing language.

Make sure this works with the information in the database etc..

If a popup name changes that is used by drawbuttons the drawbuttons will break as the data-popup in button html will not change.

A solution to this could be a fallback if a certain popup cannot be found. Or a Foreignkey to a popup.

The mobile version of tooltip does not work properly as it takes a lot of space and the text is not accurate.

Mobile popup. After positioning something the popup is not very convenient, rather open up a new page that looks a bit different as a 'popup'.

Geolocation should be added to the mobile application,

There should be a more secure way to create content in a way that the creator becomes the owner of the content. The owner can be changed only by the administrator. The content should also be easier to copy as then the copier would become the owner of the new copied content.

The data saving should be more obvious to the user. Now the user is confused wether the data was actually saved or not.

Now the color format is mixed and in some places the color does not have the hash in front #

The lottery function should be optional but easily defined. Also the information from the lottery should not be connected to the answers of the user and saved separately.

The feedback can be given using a fade in fade out thank you message or similar.

The buttons should be element wide if not specified to be half element wide..

The solution could be to make the buttons either element wide or half:
span2 - full width of the form
span1 - as half the form width

This feature should enable CSV download of the questionnaire data from the admin interface.

When creating a questionnaire it would be easier to just link same questions to different pages if they were grouped by e.g. page.

This button is required if the user is e.g. trying out the questionnaire, the questionnaire is short and want's to empty it because the answers does not feel good etc..

There should be a way to restrict the amount of answers for a drawbutton. e.g. a user can only have one home.

The required question can be implemented with html 5 required attribute and some javascript logic to make it work..

Now if the same element appears twice in the same questionnaire it will probably override each others values..

This needs to be checked and tested.

To indicate activated draw functionality the cursor should change when activated and a message on what to do next should appear next to the cursor.

When there are multiple entries in gnt.geo.get_properties response data qnt.questionnaire.property_id is always set to undefined. This causes a POST call on next property change and this will create new property_id. As a side effect all other values are removed from the non place based property data.

Also if last entry is a feature's properties all non place based properties appear empty to the user.

The problem is in questionnaire.api.js lines 595 - 602

The page does not include any information about the questionnaire. The information should be included on top of the page and the user should be able to hide or show the information..

Try this one out..

The forms and questionnaires should be built with the help of ready made elements. The form pages seems to change very often and so does the questionnaires. Only elements seems to be consistent from one questionnaire to the other.

This is a new feature but it is technically easy to do as long as the design works. The idea is that the urban planner created also non place based questionnaires with other software and it is a bit too much to ask them to use two software for this reason.

There are some generic names like improvements which will be named and shown under the same name to the user even if the contents are different.

This is why the identifier unique value of the form cannot be the same as the name of the form.

Icons on either the right or the left side of the button text needs to be enabled.

This is for usability of recognizing if the button will draw a route, point or area.

The blurb is cut and invisible if it does not fit into the left hand side of the page.

This can be fixed with restricting the blurb or giving it the ability to wrap. The wrap solution seems more popular at the moment.

The application needs to be validated HTML and jslint javascritp and tested on IE browsers down to the version 7.

Now the map is hardcoded to use 'questionnaire-map.js'. This should in someway be made so that the admin can choose which map to use.

Change the styles to fix this problem.

Especially new users who do not know which field do what can see it directly from the changes done if there exists a visual preview of the element.

One possibility would be to use html 5 editable for editing forms..