Django project models.py versus app models.py
Django models can only reside in applications, not in project itself. By default manage.py inspectdb outputs content of the models.py file and it's up to you to put it in the right place.
In your case it would be easier to put whole thing in one app and later split it in the places where it would make sense.
I'm not sure what's the state with the current version, but before presence of models module in package was indication that this is django application and can be put in INSTALLED_APPS list.
I am learning Django and I am trying to understand the use of models.py in the project versus the application.  It seems from the tutorial examples that I include a model definition in the app, but when I went to apply that knowledge to my own existing database I got stuck.
I took a database that I use (a copy of course) and generated the conceptual schema as a django model using inspectdb.  I did this at the project level, and presumed then I could write apps using subschemas in the applications for that project.
But generalizing the tutorial, they define the model in the application's model.py.  If I did that, I would be repeating the model (or part of it) that's already at the project level, which seems like a mistake and a maintenance issue.
So how, in Django style, do I use the project schema (or parts of it) without redefining it in the application's models.py?
Thanks in advance.