What names to use for enterprise geodatabases? and authoring users?
When looking at feature classes and tables stored in a GDB the name of the DB and user is a prefix. Consequently these characters are looked at and typed a lot. As much as possible within the allowed framework, what naming conventions do you use that balance conveying something meaningful and being useful without getting unwieldy?
The first is nice in daily use for it's brevity but without an interpretive document somewhere is just confusing, especially when the RDBMS has multiple DB. The last is descriptive, but invokes too much typing and consumes so much screen real estate you often can't see the feature class name, which is the most important part.
In your organization what principles and/or conventions have you settled on?