ApplicationAssignment should be destroy-dependent on Person to avoid stale rows if a Person should ever be deleted.
Avoid redundant RmPerson.find(). Use .includes() in Person.find() to eager-load ApplicationAssignments as they are always needed.
Set favorite, bookmark booleans to default to false in ApplicationAssignment
Use named scope to simplify ApplicationAssignment#index logic and transfer sorting work to database
Merge pull request #2 from cthielen/master

Database optimizations, bug fixes