Lars is responsible for the creation of the many ontologies for his company in order to keep their artifacts organized for future use. Lars worked with the architects in the company to come up with an artifact ontology strategy. Their strategy included a region ontology and a platform ontology. He then needed to translate this into the S-RAMP system. Lars creates a new ontology for the region, and adds all of the regions they agreed to classify by. Some of the regions have a hierarchy, such as “Southwest” includes “Albuquerque”, “Phoenix”, and “Denver” for their three offices there. Lars creates a second ontology with the platform classifications.
System Path 1 -
Upload a file containing the ontology. Upon upload, the user sees a preview of the ontology and commits it to the system. Once saved, he can easily see the ontology with no artifacts assigned to it. From there he can move to assigning artifacts to this ontology if there are existing artifacts that need to be classified. By default, the ontology will be in "draft" format, which means that it is not released for everyone to use or to be classified against yet. When Lars is ready for the ontology to be publically available, he can "activate" it in the system.
System Path 2 -
Lars goes to the user interface to create the ontology. He provides a name and description of the ontology, and then creates a hierarchy of the classifiers he wants as part of the ontology. During this creation, he can add, remove, and move classifiers within the list. Lars can save his work along the way and the ontology will be in "Draft" format. When he is ready, Lars activates the ontology in the system and easily begins to add existing and new artifacts to it.
When creating or uploading an ontology, we might want to make it easy for users to add existing artifacts into the right places of the ontology.
We might want to allow the user to define the ontology as "public" or "private", or maybe even define user groups that are enabled to see certain ontologies.