How do we do this? @tonyshenyy has tried some things...

Note that different fields may be relevant to different "user stories"

From Tuan:

After much thought, I realized the only fields to, ideally, map to each other/combine are under reading level, where we have different entries to translate, see:

https://www.readinga-z.com/learninga-z-levels/level-correlation-chart/

This will solve the problem with gunicorn (but I think you don't need gunicorn to do manage.py runserver).

Dav pointed out in the meeting that we should hide some sensitive information such as the database info in settings.py on our end. I can filter-branch it, but then everyone who currently has a local copy need to do re-cloning or rebasing. Is that fine for everyone?

Have a look at discussion here: #9 and add more stuff below!

I could only assign one person, but @tonyshenyy you should both have a look. We now have a functional app, done in the way @tonyshenyy had initially set things up. Sorry my django is so rusty!

Ideally, @yadelab could start working on improving the templates, but my guess is more explanation will be needed. I think a default of a list view with a search bar makes a lot of sense.

This should be done after #7. We can start with something simple using Django QuerySets:

https://docs.djangoproject.com/en/1.8/ref/models/querysets/#icontains

You probably want to have an approach where you can access postgres (or alternatively sqlite) on your local machine, and also use a database on mercury.

You can ask me to set up a database on mercury for you, and I'll give you access to that database.

cc: @yadelab

Probably also include default image, as @yadelab has introduced in the current search results page.

We may need to sign an agreement first.

Assume you'll either get a list of Books, or a Book object, and populate relevant locations with actual attributes.

Unfortunately, virtualenv doesn't work with anaconda (you get link errors because of libssl). I'm trying to figure out if pyvenv can be made to work, or maybe otherwise using homebrew.

Also write down the steps to set up the database (e.g., what to name it, how to set up permissions).

Let me know if you aren't able to do this. I thought you told me you already figured it out!

See #9 for background.

Get an installer from here:

http://conda.pydata.org/miniconda.html

For now, the most sensible thing is probably Affero GPL, which is a "viral" license that forces folks to share even if only made available as a web service. Currently, we are using an ISC license (a very permissive license).

A good template is here.

This is a fork that came from an older version of the book Two Scoops of Django.

cc: @tonyshenyy

unable to push codes to repo because the organization name changed