Determine fields we need to deal with in database / interface(s)

[davclark]

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/

[yadelab]

Hi Dav,

1. Can we please get a sample data on mercury to so that we can explore postgresql more.
2. Also how do you think we can best implement a database search functionality using Django. As a very basic starting point, we would like to have search by author or title working.

[davclark]

Sorry - I'm a bit overwhelmed with beginning-of-semester activities... so I'll be slow.

For (2) - do you understand this stuff? This is the core logic:

https://docs.djangoproject.com/en/1.8/topics/db/queries/

You'll use a form to generate the query, and a template to display the results list - each element can link to a view of an individual book.

For (1) I think this is the sample data from Tuan: https://drive.google.com/open?id=0B2JP4TBQGyuXcXlTNDVfZ1BzT2QxOC1CRWQ2STF3NjJFZGlB

[davclark]

The model should be updated to have all the columns as fields.

[davclark]

I'm pretty sure this is done, but it is a good opportunity for Code Review!

@yadelab can you have a look at the model code that @tonyshenyy wrote and verify that it matches the book fields and generally think about whether the fields are well-specified? You can provide feedback to @tonyshenyy either here, or via the GitHub code commenting interface (ask me how to use that if you'd like).