This is an open question. Is there a general naming convention for the names of the classes/collections in Weaviate that I should follow? For example, I have news embeddings, which I want to store in Weaviate. I want to name NewsHeadline as the collection/class but what if I want to test with a different embedding model of the same News? should I then name the class/collection NewsHeadline-<Name-of-Model>? so I can store the embeddings in different classes and test them?
From my side, I’d go with the approach you mentioned for simplicity.
Example: NewsHeadline_ModelA, NewsHeadline_ModelB, etc.
This keeps things clear and easy to distinguish. You might also include a version number in the class name, e.g., NewsHeadline_ModelA_v1, NewsHeadline_ModelA_v2.
Aside from the above, here’s a GUI tool I built that might help you visualize your cluster and collections more easily including configs: