siwells / daybook Goto Github PK

Need to keep track of how the app is used through logging. This should be a useful trial of an approach for deployment in the main SUPERHUB app.

Add trial city of user document

Daybook needs to support at least the following languages:

• English,
• Spanish,
• Italian
• Catalan
• Finnish

The basic approach will use the interpolation pattern, Jinja2 trans tags, and Babel, and gettext.

Dashboard shows dates until Aug 25, but the newest entries are actually Aug 27. View Diary Entries views the dates correctly.

Usability should be improved, e.g., by computing the possible duration of remaining legs based on overall journey time.

User geocoding to validate addresses & retrieve GPS coordinates,

e.g. Call the google map API:
http://maps.googleapis.com/maps/api/geocode/json?address=wheelock%20street,%20middlewich&sensor=false

Either

• redirect to the diary entries page
• redirect to the new_entry page (same page again) flashing a message to the user
• Redirect to a succesfully added a new entry page, would your like to ... page
• Show a modal indicating success and redirect to same page

Investigate CouchDB replication to get clones for data analysis, e.g. clone live DB to local machine then work with the reports on a safe backup.

Export the journey diary data stored in the CouchDB database as:

• A raw dump
• An analysed report

Enable a user to get a new password sent to them

The time format in View Diary Entries shows 11:2 while it should be 11:20

When a users password is changed they should be notified at their registered email

e.g.

daybook/
   doc/
   etc/
   src/
      daybook/
      db/
   test/

Investigate using the flask-script extension for CLI management of daybook.

Set up a unit testing framework for the flask WSGI app so that we can be confident we haven't broken existing functionality each time we make a change to existing code. This is also useful as a dry-run for how to introduce unittests to the SUPERHUB WSGI app.

• Enable user to set their language in the settings page
• Update user document to store language
• Override browser/platform locale if user has a different locale set in the app

Because the 404's in the logs are fucking annoying

Abstract from travel history towards more general behavioural metrics/tracking/reminders

Add {email|UUID} to log lines to make them a little more useful.

Log lines now output something similar to the following at new user signup:

{"timestamp": "2013-08-20T18:26:43.718945", "type": "New user reqistration", "payload": null, "data": {"email": "[email protected]", "uuid": "319f7435-e5f3-41de-98a9-2f8700aa6309"}}

Users should engage with the journey diary regaularly. Ideally this engagements occurs at exactly the frequency required by the study that DayBook is being deployed for. Therefore, use Celery background tasks to iterate over DB & populate user notifications. This is related to issue #13.

Initialise CouchDB datastore for diary storage

Dashboard Page: More information about reported journeys, e.g. date + time for each entry.

Wiki page listing overview of features is hereDayBook Features

When creating a new account the supplied email should be confirmed by emailing that account with a confirmation link

Enable user to log out

Investigate the HAProxy+Nginx+uWSGI deployment architecture.

Enable users to save templates for regular journeys:

[1] Save all details from a complete plan with a template name, [2] User selects a journey template from drop-down in entry page, [3] for is completed with saved details from template but the date & time are updated to reflect the current time of entry. [4] User makes final adjustments then saves new journey.

Showing links to diary entries & add new entry page with chart showing the number of entries over the duration of the diary

When a user has saved a journey then notices a mistake then they need a method for fixing the errors in the existing stored journeys.

Two possible solutions:

[1] Allow user to toggle edit/view mode in the diary page. In edit mode the user can alter the details of the displayed journey
[2] Allow user to select to edit a given journey when displayed in diary page. This journey is then loaded into the entry form for final adjustment with an update flag set. When button is pressed this entry must be saved in place of the older entry & not as a new entry.

Need to distribute code with a license so people know their rights

Enable users to log in

Enable user to put in just the origin and click a radio button to indicate a round trip.

Saving past addresses would be good to add so that every address does not need to be newly entered.

Enable user to change their password by setting a new one

Work with Paula & Judith to establish what the minimum requirements are for this tool.

Replace the boilerplate in gh-pages with something about what we are trying to build here.

Enable users to create an account

Investigate using Celery for longer-running background/external tasks

Code needs to be under a license

Add join date to user document

Editing past trips does not work. Seems like a technical issue. https://diary.superhub-project.eu/diary gives an error on row 19 (funktion select_journey() ). Does not escape a JSON object correctly, javascript crashes with ".

In View Diary Entries, Select a Journey wraps at 31, making 32 the top value

Based on list of features found in https://github.com/siwells/daybook/wiki/Features

Based on user feedback "This is about definitions. We should add more explicitly on the form what we expect to the location fields (addresses), what is the definition of a journey, what is the minimum travel distance for walking legs."

Initialise CouchDB datastore for user account/authentication storage