What should the project name be for Cybercastor model runs?

[philipbaileynar]

We are currently revising every model in our waterfall. RSC being the first #833. Now is the time to think about what we want the project names to be for all our automated model runs!

• We are currently inconsistent and use the HUC number, HUC name and model type in various combinations.
• Now that we have the Data Exchange we can see the various places that we use these names and some of the associated space constraints that cause truncation and wrapping.

Here's a useful comment by @MattReimer to kick things off:

It might be a good time to ask if the project type should appear in the project name. There are pros and cons but mostly we just want to be consistent/

Pros for short names
It frees up our design and interface choices so that we can choose when to show the project type and when to hide it Maybe we don't show the project type at all, maybe we show an icon, maybe we show the short name, maybe we show the long one.
It makes scanning easier. For example: if we are filtering a view to only Riverscapes context then the fact that every item's title starts with "Riverscapes context for blah blah blah" is redundant and when we shorten the string we may just get every line being:
"Riverscapes Cont..."
"Riverscapes Cont..."
"Riverscapes Cont..."
"Riverscapes Cont..."
This is really hard to make a choice
Seems like a good time to have the discussion...