Abstraction Schemas

Abstractor stores predicates/attributes in the AbstractionSchema model. Each AbstractionSchema has an object type that determines how the data point will be represented in the user interface:

• list: an autocompleting list of possible values (intended for larger lists).
• number: a HTML 5 number type input.
• boolean: a radio button list of 'True' and 'False'.
• string: a regular HTML text input type.
• radio button list: a radio button list of possible values (intended for small lists).
• date: a datepicker input type.
• dynamic list: an autocompleting list of possible values determined dynamically by delegation to a configured instance method on the subject entity/subject.
• text: a textarea input.

Each entry in AbstractionSchema has a predicate, display name and preferred name.

• predicate: the formal name of the predicate/attribute -- this should not contain spaces, as it will be used to represent the attribute in pivoted SQL statements. Examples: 'has_icd_o_3_histology_diagnosis', 'has_recist_tumor_response_critera', 'has_karnofsky_performance_status'.
• display name: the way the predicate/attribute will be represented in the user interface -- it should be the optimal way to communicate the meaning of the attribute/predicate to a human. Examples: 'Pathology Diagnosis', 'Response Criteria', 'Karnofsky'.
• preferred name: should be the most common way for which the predicate/attributes is mentioned in textual content. Examples: 'Histology', 'Response', 'KPS'.