ClaM - A Classification Manager
Generating modified sub-classes
You have the choice to automatically generate all elegible extension classes from the defined modifiers, or to do this locally from the place where a modifier has been defined at a specific class. These two options are described below. Before you can do any of the two, you have to create and assign the modifiers.
Local generation of extended classes
The local generator screen serves two purposes:
- Define and Store settings
- Generate new subclasses
Usually the codes of modifiers are concatenated to the existing code. If there is more than one modifier specified at the selected class level, you must apply the modifiers in the appropriate order, so the codes are generated at the desired position.
The Code box under Settings allows the user to define the position within the class-code where the new extension will be placed. NOTE: bear in mind that here the position does include the decimal point in the code. So where in daily use one uses terms like fourth digit, it is the fifth position if a decimal point is included.
Alternatively if the classification does not allow for a modifier at a fixed position, you just set the Replace digit at to 0, and the extension code is appended to whatever level leaf node.
You can conditionally concatenate the subcode with a maximum of two characters. Be aware that depending on the number of characters inserted you have to adapt the position setting.
The Rubric box offers a few options on how to compose the term that goes with the new code. You have the option to a) only use the preferred term of the modifier rubric, b) combine the preferred term of the parent class with that of the modifier class, an finally c) to replace a specific subset of the parent class preferred term, with that of the modifier rubric preferred.
The Preview window at the bottom gives an impression how the new classes look with the options choosen. That view shows what will happen at the first found leaf node as an example. This view adapts instantly on changes of settings.
Finally you can indicate with a checkbox that the subclasses should be automatically created with the Auto generator (see below). The Store settings buttons save the setting in a Meta tag as bescribed at the end of this section. The meaning of the four are self explanatory. Please note that the "Remove.." button deletes all subclasses that have been generated from this specific point downwards. Subclasses generated from a parents or children are not affected by this command.
This function can be reached via the Class menu, or via the pop-up if you right click in the hierarchy pane of ClaM.
Auto-generator of extended classes
With this function you can generate all subclasses at all leafnodes under the classes where a modifier has been specified as auto generate
This function can be reached via the Modifiers menu.
Because ClaML does not provide descriptors for how and when modifiers are generated, ClaM stores these data in a META-tag. You should not edit that tag. The contents of the tag are changed from the local generator screen.
The "Commands" in the meta tag are concatenated with their parameter values, and separated with semi-colons. The meanings are given below:
AUTOGEN => auto-generate sub-classes ALWAYS<sep> => concatenate with <sep> OPTIONAL<sep> => if <sep> not already present, then concatenate with <sep> REPLACE<digit> => replace digit at <digit> CKIND<ckind> => class kind for new sub-classes MODRUBRIC => use rubric of modifier for new sub-class CONCATRUBRIC<sep> => concatenate rubric of modifier using <sep> REPLRUBRIC<word> => replaces <word> in rubric with modifier rubric