Use rules combinations. In order to use same feature as IRMa, the user should be able to:

• specify a set of rules defining
  • the field on which the rule will be applied : accession or description
  • the test operation which will be executed : starts with / ends with / contains or don't contains
  • the text to search in the given field (Case sensitive)
• specify one or more rules compositions

User will want to select as typical, protein which has

• its description starting with “sp”
• or its description starting with “tr” and its accession ending with “_HUMAN”

To do this the user will have to create 3 rules :

 1. R1: description starts with "sp"
 2. R2: description starts with "tr"
 3. R3: accession ends with "_HUMAN"

and creates the following rule composition: R1 or (R2 and R3).
When running the module, for each PutativeProtein the typical protein will be set to the first one which respects the rule composition constraint.

In this example, the user will preferentially wants to select as typical a protein which has its description starting with “sp”.
If no protein respects that constraint then user will want to select as typical a protein which has its description starting with “tr” and its accession ending with “_HUMAN”.

If we uses the same rules as in example 1 (R1, R2 and R3), the typical protein to choose will be one (the first) which respect R1 and if none is found the new typical protein should respect rules composition (R2 or R3).
To do this, the user will have to create 3 rules :

 1. R1: description starts with "sp"
 2. R2: description starts with "tr"
 3. R3: accession ends with "_HUMAN"

create two rules compositions:

 1. C1 : R1
 2. C2 : R2 or R3

and order rules compositions by priority

• C1 then C2