Package phenote.datamodel

Interface Summary
AnnotationMappingDriver  
CharacterI CharacterIs are the building blocks of phenotypes.
CharacterListI holds a list of Characters - rename phenotype? i dont think so - can have multiple genotypes in it - transfreable allows it to be plopped on the clipboard hmmm isnt this just a List?
PhenotypeCharacterI  
PhenotypeCharacterI.PhenotypeCharacterFactory  
 

Class Summary
AbstractCharacter  
AnnotationCharacter CharacterI for OBOAnnotations
BasicAnnotationMappingDriver Maps ENTITY to subject and QUALITY to object but is this proper? shouldnt genotype be subject?
Character The Character datamodel is a generic hash of CharField-CharFieldValues CharFieldValues are free text or from ontologies This is the straightontabular implementation of CharacterI In the table view a character represents a row
CharacterIFactory Makes instances of CharacterI, according to mode set - OBOAnnotation or Character
CharacterList i made this as a transferable when i didnt get the whole transferable thing and now i dont whether to scrap it or not.
CharField  
CharFieldManager Manages all of the ontologies.
CharFieldValue At the moment char field values can be Strings, OBOClasses, and dates, and possibly more coming.
Comparison for making relations between statements
DefaultMappingDriver  
EnvironmentalSampleAssociationMappingDriver  
OboUtil changing this from static to non-static so can build post comp object from multiple rel-diffs
Ontology Ontology represents at this point the contents of a single obo file (which can be more than one ontology) an ontology wraps an obo edit OBOSession - at this point there is one OBOSession per obo file - that may change in the future
PhenotypeAssociationMappingDriver  
PhenotypeCharacterWrapper Provides a mapping between a character representing a phenotype, such as is required by the PhenoXML adapter, and the standard character with generic fields.
TransferableCharacterList  
ValueCharacterList A CharacterListI implementation which represents the contents of a CharFieldValue as a list of characters which can be edited in a separate character table view.
 

Enum Summary
CharFieldEnum so this class has evolved - this was actually doing the setting of field values at one point - but now that we've gone to a generic datamodel, the datamodel is now determined by the configuration - and not restricted to CharFieldEnums - you can have a field that is not in CharFieldEnum - which leads to the question should we get rid of this class? and the answer at the moment is maybe not - as you can still use this in data adapters to get at predefined strings for definied fields - to make sure data adapters are using the same string for the pub of entity field.
RelationshipEnumeration Created by IntelliJ IDEA.
 

Exception Summary
CharacterEx  
CharFieldException  
OntologyException  
TermNotFoundException unclear to me if we really need both ontology ex and termo not found ex