Open nerdstein opened 6 years ago
Or, the product should be articulated as an Open Data Dashboard. This name is likely weak, because we don't have a direct right to "Open Data" (it's too generic) and "Dash" is closely tied to Dashboard. As such, this might be harder to trademark based on these loose affiliations to broader things.
A safer bet would be a fanciful or arbitrary name for the product itself that doesn't really have any association or descriptive association to the product.
@marctjones offered to do a trademark search if we come up with a set of names. Let the contest begin.
Please note - we should also likely consider renaming the repo and the product name
The best names are fanciful, arbitrary, or suggestive. The more fanciful the better. We should avoid names that are descriptive or generic names.
You can combine fanciful elements with descriptive or generic names though. See https://en.wikipedia.org/wiki/Trademark_distinctiveness
Not so sure about that @marctjones -- meaningless branding names are not particularly helpful for UX and present a learning hump. You can preface the function name with DKAN, which checks the fanciful, arbitrary box. Here are a couple suggestions: -DKAN Visualization manager -DKAN Chart Center -DKAN Chart Hub -DKAN Visualization Hub
In general, I really dislike long titles and -ization words, but it may fit here.
Oh I like 'VisHub' but we already have confusion around the Visualization Entity repo and Dashboards (and recline previews for that matter) so using any variation of visualization is going to compound that problem.
Maybe in keeping with nautical terms (e.g. Surfing uncharted seas of data) and getting more specific with actual visualization objects: Chart House? Chart Room? Chart Library?
^^ Agreed with @bobschmitt-civicactions .
Would like to avoid the full word "Visualization" in the name - mostly because it doesn't roll off the tongue easily when speaking quickly, i.e. when giving an in-person DKAN training. (Try saying "data visualization" 10 times fast.) See also what @janette said about the Visualization Entity being a separate module.
I can't think of anything super catchy, but here's what I've come up with:
I like Infographics, VizHub, DataViz, DasDataVizard (German translation ;-)
Side note: DataViz is a registered brand name, but Data Viz isn't :)
@stefaniefgray I think we have aspirations to use it beyond just DKAN. I'd like to avoid using DKAN in the name
There are a couple of reasons for this.
React has trademark rights to React. This rides off of Facebook's trademark, which is awkward for us. We would potentially need to change the name of this product.
I don't think we need to be beholden to using the React framework. What if we want to use Elm or Vue in a future version? The current name would then be off based.
Our vision of React Dash is to use this as a dashboard technology for any Open Data system. A better name might be something closer tied to the purpose, like "Open Data Dash". This would be better contextually, and not tied to a technological framework.