First load the site (in English). Then click the “menu” circle in the upper right. Then, in the menu, switch language to Filipino. Now click “back” in the upper right. For some reason it doesn’t work, and you have to click it again. (I double checked that without switching languages, it takes only 1 click.) The same problem occurs if you load it in Filipino and copy the process above, but switch to English

Much of views.py appears to use tabs, rather than the four spaces recommended by PEP 8. All existing (and future) code should transition to the use of spaces for indentation.

This would ensure the dataset is clean and that users are guaranteed to be presented with an actual comment.

PCA/Scoring/Prioritization

For example, right now it says run sudo pip install requirements.txt whereas the wiki has the right thing which is sudo pip install -r requirements.txt

This one is sort of big. Here’s the link to the screenshot: https://drive.google.com/open?id=0B9O5aF-I424xVkhNVGZPd05Xdms. I accessed the page at http://opinion.berkeley.edu/pcari-test/comparison/5/ and then I randomly switched between pages by modifying the page number in the link and using the provided buttons. Will notify the team once ableFor example, when you are on the landing page, click begin, backspace / hotkey for “back”, and then begin again from the landing page, there is a CSRF verification error. to replicate. In the meantime, I have provided the error message so we can get started on addressing this one right away. The problem is that lines 332 - 350 in views.py assumes all ratings are in the database and fetched in order.

pcari/views.py , all state information should be stored in cookies.

Write unit tests for all of the views. This means generating post requests with data and testing to see if the data is stored properly.

Translation functionality is built into Django. We would want to focus on translating at the template level, since most of our translations are static.

Error message occurs when AnonymousUser accesses the site: https://drive.google.com/a/berkeley.edu/file/d/0B9O5aF-I424xdlFjMlVaN1RTRFU/view?usp=sharing. (discussed at length in the email thread). Problem occurs in the version of django run on the pcari server. Should be able to fix with “if request.user.is_authenticated”

The current implementation of generating histograms of quantitative question ratings is copy-and-pasted. That is, a for-loop in Django's templating language creates multiple script tags, each corresponding to one histogram. The histogram data is passed into the template.

We should only have one script with reusable components (that is, functions), and pull histogram data dynamically using AJAX calls to endpoints.

Edit: see comments below.

For comments with no ratings, the mean score is undefined, which causes an exception to be thrown.

Use the logging module to facilitate debugging.

The browser back button is not optimal in that it doesn't handle language switches.

Users want to change answer in one of the questions (upon seeing it in the review page), presses back until desired question number, then answers, but is frustrated that he/she has to answer all of the other questions again

We can use validators to sanity check model data on assignment (e.g. preventing negative numbers when storing an age).

Store it in the database and dynamically pull it.

When user submits, the app crashes:

We need to implement proper error handling.

I've seen this done in some places- we can put all the package dependencies into a file and end-users can run pip install requirements.txt
Makes it easier if we end up juggling multiple dependencies and want specific versions for each.

https://pip.pypa.io/en/stable/user_guide/#requirements-files

Minify resources and pages (i.e. eliminate syntactically unimportant whitespace) to reduce file sizes.

Currently, pylint fails badly with the code (e.g. -12.60/10 for views.py). However, once the code base is cleaned up, we will want to enforce good style.

Migrate all form submission to AJAX

E.g "urlpatterns = [
url(r'^v21/', include('pcari.urls')),
url(r'^admin/', admin.site.urls),
url(r'^pcari/', include('pcari.urls')),
]"

Remove these patterns and always reference the root.

Putting dependencies on Docker containers allows easier integration between our machines, and makes setup for new users easier as well.

Migrate the database to mysql

make sure that Facebook sharing works

This enables easier scaling for translations--if we want to add more languages, or add more questions.

From the google doc:

• First load the site (in English). Then click the “menu” circle in the upper right. Then, in the menu, switch language to Filipino. Now click “back” in the upper right. For some reason it doesn’t work, and you have to click it again. (I double checked that without switching languages, it takes only 1 click.) The same problem occurs if you load it in Filipino and copy the process above, but switch to English.

• When you are writing your own idea in the text box, there are a few issues with switching languages. It was loaded in Filipino, and I clicked “menu”. It took 2 clicks to switch languages to English, and it took 3 for “back” to work. Once I did get back to the page with the text box, the language reset back to Filipino. (Notably, when I clicked “menu” again, that page was still in English). Then, switching to English on the main page also makes the menu switch back to Filipino...

Currently, most templates share the same frontmatter (for instance, the head tag). To cut down on redundant boilerplate and make creating new templates easier, templates should inherit from a base template.

This would be especially helpful if a user wanted to revisit a page (without having to refill their responses).

Now that we have agreed to not commit SQLite files, we should remove the data in malasakit-django (to avoid noisy commits when SQLite files are updated).

For example, when you are on the landing page, click begin, backspace / hotkey for “back”, and then begin again from the landing page, there is a CSRF verification error.

This would help with version numbering.

Strip trailing whitespace to comply with PEP 8. Most editors have a setting to perform this automatically.

Add a 404 page or 404 redirect for invalid GET requests

All analytics functionality should go here.

Once a record is written to the database (especially concerning user data), it should never be able to be deleted. We should have flags that indicate whether a record is active or not.

Rating from 0-9 seems sort of arbitrary without any frame of reference. For example in question 1, instead of “select a number”, there could be a statement by each number, or for every few numbers. For example, “0: I have not suffered due to a flood, and know no one who has suffered due to a flood.” All the way up to “9: I have lost a home or loved one to a flood.”

From Django documentation:

Running Django with a known SECRET_KEY defeats many of Django’s security protections, and can lead to privilege escalation and remote code execution vulnerabilities.

We will need to set the SECRET_KEY as an environmental variable and reference it through os.environment.get() on the production server.

While writing text on the last part of the survey (http://opinion.berkeley.edu/pcari-test/comment/), switching languages also deletes all user input from the text box.