From: Eric D. <ede...@sy...> - 2015-07-01 21:32:02
|
Hi everyone, another intended feature that is not in the current specification that Pierre-Alain mentions is the ability to define custom key-value pairs. Maybe Pierre-Alain can flesh this out, but from what I gather, the documentation should go something like the below. Please consider this and let’s discuss at the call tomorrow. In order to use a custom key-value pair (i.e. the key is not in the CV) in the sequence header blocks, it MUST be predefined in the file header. The definition MUST be of the form: # SpecificKey=KEYNAME:”KEYDEFINITION”:VALUEREGEXP For example, to define a SecondaryStructure term: # SpecificKey=SecondaryStructure:"Secondary structure element and position":\([0-9]+\|[0-9]+\|[\w:]*\|\S+?\) And then use: \SecondaryStructure=(617|673|ncithesaurus:C47937|Helix) Pierre-Alain, did I capture this correctly? The regexp part will be tricky.. Thanks, Eric |