kprasch / opendispatch Goto Github PK

to do:
create a milestone or label for this file.
wrap most of the logic in this file in a class.
when the class is called the init method connects to gmail.
somewhere another method closes the connection to gmail.
extract_gmail_incidents needs to be rewritten using generators.
urls.py needs to not use extract_gmail_incedents as a view.
test stuff.

Generate and display a report of incidents for any given data range, type of incident, ect.

including page navigation.

Need google auth done through the API for message downloading. Log in is currently from termanal raw input.

Make the date indicators that overflow onto the page hide when the dateSlider has been inactive.

Use the DRF API correctly and use views.APIView

Using extracted location data, pinpoint the dispatched location on a map, and display it to the user on any incident page.

I would like to research in Psych, Behavioral Psych, Disaster Psychology etc. scholarly article databases the effects of this information on behavior. We would like it do have a positive effect.

https://github.com/KPrasch/Dispatch.py/blob/master/dispatch/__init__.pyc

in dispatch_gmail.views messages are selectred by sender via the imap library. This should be docoupled and placed into a settings file, along with the valid keys list. Mabye this belongs in a custom settings file, or just settings.py

Need a landing page - main.html

Will become a call taker dashboard.

Using models from the db, populate a table of retrieved gmai lincidents.

I like this layout a lot better, what's your goal?

dispatch_gmail.views.extract_gmail_incidents

Needs to take a request and return an HttpResponse object

Users should be able to log in, and then redirected to thier Dashboard.

Google API auth for incident downloads, and Django Auth should be implemented.

Leave a comment below to let me know you've got it.

I feel like this may be a better way to stage new features and also allow for less wait and change debugging. Thoughts?

User should be able to generate incident reports based upon input. Some graphing shoud be done automaticaly, however. Graphic could be done with a python library, or with a javascript interface, for real time. Amount of processing needed should be considered. One obstacle will be cleaning the data fields in the db that have random strings attached to thier values from bad parsing. A url and template structure needs to be imagined for this as well.

Each incident will have an incident web page with location data and details.

The options are pretty expansive but I feel like Mithril.js (still in BETA) is a good place to start because of our relatively simple needs, no point in adding the extra abstraction of a less lightweight framework. This could clean up and organize the current JS implementation and also allow for less jQuery/$.ajax ambiguity.

Also possible use of LoDash on the client side to filter JSON that will get piped to the interface in a more performant and concise way. (AKA less server calls for filters and map points.)

Mithril.js
LoDash