How to organize and document large number of database views

Hi.

​

In our upcoming data analysis project, we'll be creating a bunch of database views, many of which will likely be reused in different parts of our software. Many of the views will be queried by other database views as well.

As the project grows, we need to have a strict (naming) policy so that we don't end with a total mess of views that's hard to reuse and hard to figure out which business problem it solves.

Likely, we'll maintain some soft of SQL script in our application source code, which will (re-)create the views as needed. In this script file we can add comments as needed.

What's the community's suggestions on how to structure a large number of views like this, both in sense of naming the views but also documentation?