title: How to approach Django project starting with database schema?
body: <p>Every Django tutorial/book I've seen approaches Django projects from what I am going to characterize as an ad-hoc database design method.  A project ends-up being a bunch of little apps, each with it's own models, view, etc.</p>
  
  <p>I am trying to locate a resource that covers how to structure a Django project when you do, in fact, start with a traditional DB design process.  </p>
  
  <p>For example, let's say that this is the starting point:</p>
  
  <p><img src="https://i.stack.imgur.com/azB8m.jpg" alt="enter image description here"></p>
  
  <p>And a document describing it:</p>
  
  <p><a href="http://geneontology.org/page/lead-database-guide" rel="nofollow noreferrer">LEAD Database Guide</a></p>
  
  <p>How does one approach this so that the various Django apps access a single "global" (bad word) db model that covers the entire schema rather than a bunch of models spread across a bunch of apps?</p>
  
  <p>Are there any resources (books, pdf's, tutorials) that cover this approach rather than the piece-meal approach most commonly seen?</p>
  
  <p>A corollary to this question might be:  Is there a, perhaps automated, way to go from an SQL (or MySQL Workbench) schema definition to the equivalent Django ORM?</p>