Update model

[ehmatthes]

This is the most significant issue of the alignment so far. We need to:

• [x] Remove the pathway feature.
• [x] Remove the forking feature.
• [x] Remove migrations, and rebuild the db from scratch. (Look at fixtures as well.)
• [x] Create superuser, create regular user, and make a school.
• [x] Upgrade to Python 3.
• [x] Look for other simplifications before digging into new model.
• [x] Update the existing model to GSP structure/ labeling/ language.
  • [x] Look for opportunities to simplify the code significantly. #52
• [x] Address ordering issue. #55
• [x] Decide whether to include public option right now, or focus on development while logged in only.
  • Leaning towards logged in only, for simplicity. Implement option to make it public once works logged in.
  • This doesn't block the current alignment work, so I'll move this to post-alignment work.
• [x] Decide whether to leave levels in, or remove them for now.
  • If they're not in the way, may leave them in. But could be worth rethinking.
  • Will examine this when cleaning code in #48.

[ehmatthes]

Remove the pathway feature

Started this in #43, continuing here.

• [x] Remove references to pathways in models.py.
• [x] Remove pathway-related forms.
• [x] Remove pathway-related views.
• [x] Remove pathway-related templates.
• [x] Remove pathway-related admin elements.
• [x] Remove pathway-related urls.

[ehmatthes]

After removing most pathway elements listed above, runserver lists a lot fewer issues than when I ran runserver in #43:

$ python manage.py runserver
Performing system checks...

System check identified some issues:

WARNINGS:
competencies.UserProfile.schools: (fields.W340) null has no effect on ManyToManyField.
competencies.UserProfile.subject_areas: (fields.W340) null has no effect on ManyToManyField.

System check identified 2 issues (0 silenced).

You have unapplied migrations; your app may not work properly until they are applied.
Run 'python manage.py migrate' to apply them.

May 15, 2015 - 16:05:58
Django version 1.8.1, using settings 'opencompetencies.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.

[ehmatthes]

Should just grep pathway in the codebase.

Done. Can view entire system for a school. Haven't tried all aspects of the project yet.

[ehmatthes]

Remove the forking feature

I've been mentally debating whether to remove all the forking code while removing the pathways code. It's always hard to remove code you think you might use again, but it's pretty verbose. I'm confident the model can be greatly simplified, which would simplify the approach to forking I tried in the first edition of OC. That's what version control is for, anyway! If I want to use this old code, I can copy it back in.

Remove references to forking in:

• [x] models
• [x] views
• [x] templates
• [x] forms
• [x] urls
• [x] admin
• [x] docs
• [x] grep the remaining codebase for "fork"

[ehmatthes]

Remove migrations, and rebuild the db from scratch. (Look at fixtures as well.)

• [x] Is there any content that's worth saving?
  • No, I saved a copy of the webpage for reference, but it's sample data anyway.
• [x] Is there anything in fixtures that's worth saving?
  • No, it's full of references to pathways and not worth parsing.
• [x] Remove migrations.
  • Deleted entire /migrations directory.
• [x] Rebuild db.
  • [x] Drop db in postgres.
  • [x] Recreate empty db.
  • [x] Rebuild db.

[ehmatthes]

Dropped database, rebuilt empty database.

[ehmatthes]

Rebuild db

$ manage.py makemigrations competencies
$ manage.py migrate competencies

Complains about contenttypes.

$ manage.py migrate

Worked.

[ehmatthes]

Index page complains about school that doesn't exist. Not using the school anymore, so removing the query for sample_school in views.py for the index view.

[ehmatthes]

Stepping away from this for a bit. Next steps: create a superuser, and at least try to make a school.

[ehmatthes]

Create superuser, create regular user, and make a school

Try this before moving on. Not worth testing more, until focusing on the model further.

• Created a superuser, that user could create a school.
• Tried creating a regular user through admin site:
  • User can create a school.
  • Initially complained user didn't have a UserProfile, but I'm not seeing that error working with schools now.

Sort out UserProfile issues when creating process for new account registration.

[ehmatthes]

Upgrade to Python 3

I think I went with 2.7 when I was doing the initial version of OC because I wanted to use reportlab, which required 2.7 when I started this work.

Plan: replace current venv with a Python 3 venv, and see if anything breaks.

Upgrade worked, with minor notes:

• I have multiple versions of Python 3 on my system, so I needed to run sudo apt-get install python3.4-dev
• Rather than installing from requirements.txt, I installed django-toolbelt. This updated the versions of all dependencies, and eliminated some dependencies. I made a new requirements.txt.
• Fixed a single 2.7-style print statement.

[ehmatthes]

Look for other simplifications before digging into new model

In a quick look, I didn't see anything obvious. But I'll keep an eye out for this as I'm working on the model, and maybe record some simplifications here.

Tracking these separately in #52.

[ehmatthes]

Update the existing model to GSP structure/ labeling/ language

Opening a separate issue for this, as this is likely to be more involved than I want to work with in this one issue. #51

[ehmatthes]

Decide whether to include public option right now, or focus on development while logged in only.

This is mostly about whether to give users the option of making elements public at this point.

Easy decision: hold off for post-alignment, it's useful to our school right now.

[ehmatthes]

Done!