Creating Instance Data
Using RITE, users can quickly create instance data corresponding to the ontology currently present in the running RACK instance.
Note: This tutorial assumes that the RACK Project directory has already been set (see here).
Step 1. Bring up the Ontology Info tab and expand a namespace to see the classes in that namespace.
Step 2. Right-click on a class of your choice and click on Create Instance Data.
Step 3. Step 2 will bring up a new tab with two sections.
The first section shows the properties associated with the class, which users have the choice to select or deselect. Selecting a property implies that the user wishes to associate entities to the instances being created, using the property.
The second section contains a table where each row represents a new instance of the class and the columns represent each of the selected properties in the template.
Step 4. Fill in the table as desired to create instances of the class, and then right click on the filled row. This will bring up a context menu that will have options for deleting the row, ingesting it into RACK, saving as a CSV file, or autopopulating the next 10 rows.
Step 5. If the users choose to save the data as CSV, then a CSV file corresponding to the class is created in the location set as RACK Project. A corresponding .yaml file is also automatically created that can be later added to the manifest.
Step 6. If the users choose to autopopulate the next 10 rows, then 10 rows at the end of the CSV table are autopopulated by using values from the selected row. Empty cells are copied as is. Non-empty cells have a random number attached as a suffix starting from the first row that is appended to the end of the CSV table. The same random number is incremented by 1 and added as suffix to the next row's non-empty cells and the process repeats up to 10 rows.
Go back to Wiki Home
Copyright (c) 2021-2023 General Electric Company, Galois, Inc.
All Rights Reserved
This material is based upon work supported by the Defense Advanced Research Projects Agency (DARPA) under Contract No. FA8750-20-C-0203.
Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the Defense Advanced Research Projects Agency (DARPA).
Distribution Statement "A" (Approved for Public Release, Distribution Unlimited)