byu-osl / city-issue-tracker

An issue tracker for cities
GNU General Public License v2.0
2 stars 3 forks source link

Discussion about Backend #1

Open kamn opened 10 years ago

kamn commented 10 years ago

I am just going to kick off the discussion for the Backend team(David, Mike and me) so everyone else can ignore this thread. I just wanted to mention what I am doing, an ideas and some questions.

First, I am going over a Flask tutorial which mentions some modules that might be useful. Once I am done I will give a quick overview.

Second, I think that we should try to get some simple open-source 311 api server running for the front-end team. To give them something to work with early. Like I have mentioned I think this might work but I am not sure. I will try to get that up and working after the Flask tutorial(or after reading the Open311 specs)

Third, the backend is going to be at least partially an API but is it only going to be an API? For example, are we going to allow a simple interface for viewing databases or managing issues(like closing them or reassigning them)? Or is that the front end's job? If we are going to be adding some interactive features, which? I feel like parts of this were discussed but I would like to see something in writing.

Fourth, I have not gotten to the Open311 spec yet but probably will by the end of the weekend but has anything stood out(important to note) to either of you guys?

kamn commented 10 years ago

Ok, so I have a basic toCitDict working in the app/models/citmodel.py. It should work in the same way as the toDict method. Also I added two new methods toCitJSON and composeCitJSONList which should work probably. I am not going to add a toCitXML since we know we will only deal with JSON.

Mike, for the session management I guess maybe the easy( but not exactly what we want) solution is Flask-Login.