Conflict resolution tools in SEED

This was written by SvetaG, March, 2005.

In order for a protein/gene (PEG) in SEED to be connected to a Subsystem (SS) it's annotation must exactly match the name of a corresponding functional role as it appears in the table of Functional Roles in a SS. Therefore, for a PEG to be connected to multiple SSs, their authors should agree on the name of the corresponding functional role. The general philosophy in SEED (especially Annotators' SEED) is to build Pythagorean/Kepler's Harmony of the Spheres - Subsystems that is, meaning that each Subsystem has to be encoded such as not to crash into any other (and ideally - to nicely cover metabolic space leaving minimal holes between them). To do so, a number of naming conflict prevention and conflict resolution tools have been implemented:

1. for use during initial SS encoding
2. for use during uploading//installation of SSs developed elsewhere

1. Tools for conflict prevention during construction of a new SS
1. During the ground stage of SS development - putting the list of functional roles together - make sure you consult the tool: Locate PEGs in Subsystems - found at the very bottom of the main FIG search page. This great tool is the front line of defense against potential naming conflicts (in additions to it's many other uses).


The easiest way to find out if a particular functional role has been already named and used in other SSs, type the corresponding EC number into the Search box. In the absence of EC number, search can be performed using a COMPLETE role name as a query. However, PEGs with annotations deviating even slightly from the query text (e.g. by capitalization or a space) will not be identified.
Alternatively, naming conflict prevention can be done one step further into SS development, after the initial limited set of PEGs in a handful of genomes have been connected to a Spreadsheet. Using PEG ID as a query, it's homologs (in a specified genome) connected to other SSs can be identified. Note, that a genome must be denoted by it's SEED ID number, not it's name. If search results are negative you are free to name the functional role as you like (however, see SEED naming conventions here) . If it has been used in at least one other SSs, you must either use the exact role name or negotiate its name change with the author via E-mail. An author's name appears at the top of each SS page. For SEED annotators' contact info write to: Sveta.

2. While projecting PEG annotations via homology using Similarities page, please note the "In Sub" column. It shows the number of other SSs that each homolog is already connected to, warning you not to rename such PEGs lightly. This tool doesn't tell you, which SS the homolog occurs in. Please open the corresponding PEG page to see the list of "Subsystems in which this peg is present". If in conflict - negotiate the PEG(s) name change with the SS author via E-mail.
3. Before renaming any functional roles in your existing SS, please check if any of them have been adopted by other SEED users. To do so, to open your SS using the "old code":


It will take longer to open, but when it finely comes up - you'll see by each role name a list of other SSs that use the same name. Please, notify//negotiate with the authors possibility of a name change.

4. Finally, every "master" should shepherd his/her flock of SSs on Annotator's SEED carefully, checking periodically their integrity. There is a great tool for that. It can be activated from each SS page (located right above the NOTES section). Please, use it with some regularity.


When activated, this tool creates two lists of PEGs:



1. PEGs in Subsystem with MISMATCHING Functions are PEGs that still appear connected to this SS, but which have been renamed recently by someone. Note that "Role name" and "Function name" columns do not match any more - hence these PEGs will be lost if you do "refill from scratch". To prevent this, you can reannotate them inside this tool - using Assign Roles to Selected PEGs button. As always, before doing this negotiate the change with other SEED "masters".
2. PEGs NOT in Subsystem with MATCHING Functions. Those PEGs will automatically associate with this SS when the corresponding genomes will be added to it. For PEGs in the genomes already connected to SS use "refill from scratch" function on a SS page (you'll need to exit Check Subsystem window to use it).

2. Conflict resolution during SS uploading and installation

Often Subsystems created on different SEED servers by different curators can contain identical functional roles (and PEG assigned with these roles) named slightly differently. When a SS from a remote server is uploaded into your version of SEED recklessly, these 'shared' PEGs are automatically renamed in your SEED, and therefore are disconnected from resident SS(s.) To prevent or resolve these naming conflicts, every incoming SS should pass through a series of checks. To activate them, do the following:

1. On the SEED Peer to Peer Updates page mark the check-box near the SS you need to upload. Scroll all the way to the bottom of this page, make sure that the Enqueue Subsystems check-box is marked, and press the Install Checked Subsystems button. Then follow the link called subsystem update queue located in the middle of the same page:

2. There you'll see many SSs in queue - wait until yours (the bottom one) is processed - then click on Show analysis - and you'll see in minute detail all the terrible harm to resident SSs you were about to cause by uploading the new one:

3. If it looks benign - press Install subsystem button, then delete SS from queue.
4. If it looks horrible - it is your responsibility to contact the author ("master") of each SS, which the incoming SS is trespassing into - and to resolve naming conflicts with them by E-mail. To find out the authorship of affected SSs - click on each Local Subsystem name to open it - the author's name appears at the top of each SS page. For the authors' contact info write to: Sveta.
5. In the meantime:
1. register all the conflicts and planned changes in Word or any other format
2. check skip PEG boxes for all the PEGs that require attention of other SEED annotators
3. press Install subsystem button. Do not delete SS from queue if there are unresolved naming conflicts left.
6. Generate E-mails to the authors of all affected SSs.
7. Depending on their responses you will need either:
1. to change the names of affected roles in the newly installed SS to match the resident ones, or
2. to rename all the affected resident PEGs to match the role in the new SS (if all the authors of affected SSs have found the role names in the newly installed SS superior)
8. To change the naming of functional role(s), open the newly installed SS, delete the old name and type in the new. Now check refill from scratch check-box (located under the spreadsheet) and press update spreadsheet button.
9. To rename affected resident PEGs in batch, use Generate Assignments via Translation tool. It can be activated from the SEED main FIG search page (located mid-page):

10. To use this tool:
1. type in your user name in the Section: Exporting Assignments in the box Save as user
2. to the From box paste "Branched-chain amino acid aminotransferase (EC 2.6.1.42)" from an example above
3. to the To box paste "D-alanine aminotransferase (EC 2.6.1.21)"
4. click on the Generate Assignments via Translation button
5. when the job is done, go to Process Saved Assignments Sets section down the same FIG search page:

6. type in your user name WITH master:____ and click on 'Process Assignments Sets button
7. examine, accept (if OK) and delete (!!!) the set.

Please also see the Conflict Resolution help page.

A new tool to straighten out conflicts in peg assignments. If you use the URL:

where XXXXXX is your user name, you should get a summary of your conflicts.

For example,

would produce a short report for RobE.