About Dataset Naming Conventions

Use the following conventions when creating datasets:

• For all datasets that you create for a specific scenario, begin the name with an abbreviated ver- sion of the scenario name that the scenario or pattern catalog ID represents (for example, BC- ShortOptionRisk-dRBPC for Short Option Risk).
• If the scenario uses multiple datasets, start each dataset with the same prefix and provide an extension that specifies the purpose of each dataset. Make the extensions as meaningful as pos- sible; avoid extensions like _1 and _2 because they may not be recognizable to another scenario developer. Use the _p prefix and the pattern code if the dataset is pattern specific.
• If you no longer need a particular dataset, rename it with the prefix zzz_ (for example, zzz_OPT- N_ASGMT_RISK). This causes the dataset to sort to the bottom of the dataset list.
• If using a dataset across multiple scenarios, do not give it a name that is specific to one scenario. Instead, give it a name that describes the purpose of the dataset. These cases should be rare. Remember that when datasets are transferred between environments they are made parts of scenarios, so treat the multi-scenario datasets with care.