When a person shares their data set (makes it public) allow them to assign a license to it. Give them a few options to pick from.

During signup it would be great to learn more about the user.

If we could capture these during signup and in user settings (post signup). That would be great. This means we'll need to add a user settings page too eventually.

• Name (optional)
• Organization (optional)
• Country

This is down the road feature but it would be really nice to configure in "advanced settings" the ability to post any received xform to a particular URL.

That way we can use deploy as a passthrough to other systems that also support xforms.

https://github.com/modilabs/deploy/blob/master/odk_viewer/views/csv_export.py#L149

the one on the site now is the default bootstrap one which is not very cool... i think we should just make one that is the dark grey with the white f in the formhub font, though we don't want it to be too much like facebook or something... idk, anything is better than a blue b... other ideas?

Need to check with Andrew to see if this has been done already.

It would be good to have:
name
organization
city
country

Like this: http://www.christopherjonassen.com/8369/98686/gallery/devour

When an anonymous user tries to download a form, it causes a 500 error.

http://formhub.org/odk_viewer/export_spreadsheet/tutorial_1.csv

The error:

File "/project_env/lib/python2.6/site-packages/django/db/models/fields/init.py", line 292, in get_prep_lookup
return self.get_prep_value(value)

File "/project_env/lib/python2.6/site-packages/django/db/models/fields/init.py", line 479, in get_prep_value
return int(value)

TypeError: int() argument must be a string or a number, not 'AnonymousUser'

To show multiple questions in a group on the same screen, I wanted to use the appearance="field-list". In my xls I added a column appearance and added field-list in the relevant 'begin group' row.

None of this is exported to the XML. Is appearance currently supported by Formhub?

the file http://prabhasp.com/MCH_v1.xls gives an error message

'float' object has no attribute 'split'

that gives very little clue as to what to debug.

Function to return XLS form download, it links to XML now, need to write controller function.

I'll try and retest but the popups appear to be broken.

In the tutorial, the URL for the ODK settings is set to http://blah/tutorial/username rather than http://blah/username.

• Deletion should only hide a survey from the UI.
• This will allow submissions for this survey to continue if a phone still the XForm on it.
• This will prevent the user from creating another survey with this ID. This is actually a good thing so that old versions don’t get mixed in with a newer version with the same ID.

• Store photos in folders by username and survey id.
• Display photos with single survey view.
• Allow users to export zipped photos.
• We need someone in the lab to set up an account for Amazon storage.
• Store photos on S3 http://aws.amazon.com/articles/Amazon-S3/3998

HTTPS

• force the reg form to make usernames lower case
• force login form to be lowercase for user name
• we can correct (manually I can help) user names to be lowercase

Collect optional information about users when they register.
It would be good to have:
name
organization
city
country

Add form name for so users can rename their forms as desired.

It would be nice if you could upload from a URL.

This will be key when form sharing gets working.

Andrew I realize you're working on a better solution for photos. In the interim, could we just link to the photo in the popup? That will allow the people in haiti to start seeing the photos they are seeing.

We need to make sure we block off certain user names so people don't register them.

originally many of the functions of the site were tied to the root url (http://formhub.org/) which we are trying to move away from. this url should be just serving up the homepage with some basic information and a link to sign up or log in. right now, this url is also handling the submission of xls files which should have it's own url (and probably move apps as well)

this migration is failing because it is migrating data with the xform model which is out of sync with the migrations... not sure if this makes sense but, yeah, ask me and i can explain it in more detail

We should add a floating back button on the map. Right now there is no way to get back to your main dashboard besides hitting the back button.

Need to check with Andrew to see if this has been done already.

On the user settings page we might want to add as the first field

username: mberg

This will be read only but it helps orient you a bit.

Looks like this:

{u'French': u'A-0.10 Nom de l\u2019Assistant de Recherche:', u'English': u'A-0.10 Research Assistant\u2019s Full Name:'} Muscadin Junot
{u'French': u'A-1.1 Coordonn\xe9es GPS:', u'English': u'A-1.1 Geocode of facility:'} 18.195236921310425 -74.00600373744965 -3.0 6.0
{u'French': u'A-1.2 Photo:', u'English': u'A-1.2 Location Photo:'} 1324325500388.jpg
{u'French': u'A-2.3 D\xe9partement', u'English': u'A-2.3 District / Division'} Sud
{u'French': u'A-2.4 Commune', u'English': u'A-2.4 Location / Ward / Commune'} coteaux
{u'French': u'A-2.5 S Communaute/Localite', u'English': u'A-2.5 Community / Village'} other

The src on the KML points to

src="/media/attachments/1325594065737.jpg"

Needs to be the full site url.

In the xls export numbers (at least decimals, need to verify ints) are stored as text. This means you can't tally up a row of numbers in excel easily.

So I guess the need is to make it easier for users to iterate on form design. The issue now is that every new survey that is uploaded has to have a unique name/id, and once you upload a survey with a certain name/id, you are forever denied from re-using that.

The reason this is a large issue is that the need for constant renaming really is a pain and will create a billion xls files with slightly different names, and users won't be sure what is draft at what stage, etc.

One solution would be to have a "sandbox" where data integrity is a very sketchy issue (maybe we store sandbox submitted data as couch entries, as the table defintions won't line up one data submission to another?), and users are allowed to view data in very limited ways (ie, a per-submission view, but no larger xls view, cuz it just won't make sense?). BUT, they are allowed to replace a survey with any other, no problem.

For iterating until you get a decent form to deploy, this would be a perfect thing.

[We can build this much later, but Andrew, would appreciate your thoughts on this if you have any..]