README iRefIndex expanded MITAB proposal

This is a proposed expansion of the MITAB format for use in future releases of iRefIndex and does not
correspond to any released product.  

See http://irefindex.uio.no for links to the latest release and relevant README documentation.

This proposal is based on the experimental form of the iRefIndex MITAB format found at 
http://irefindex.uio.no/wiki/README_iRefIndex_experiment_MITAB_6.0

Look for xxx for things that need to be changed to create a version specific form of theis README.
Look for CHANGE for items that differ significantly from the current MITAB format.

This format is based on recent changes agreed upon by the PSI-MI working group in Turku, Finland.
See http://code.google.com/p/psimi/issues/detail?id=2 and http://code.google.com/p/psimi/wiki/PsimiTabFormat

Last edited: xxx

Applies to iRefIndex release: xxx

Release date: xxx

Download location: xxx

Authors: Ian Donaldson, Sabry Razick, Paul Boddie

Database: iRefIndex (http://irefindex.uio.no)

Organization: Biotechnology Centre of Oslo, University of Oslo (http://www.biotek.uio.no/)

Note: this distribution includes only those data that may be freely distributed under the copyright license of the source database. See Description below. xxx

Description

This file describes the contents of the

xxx

directory and the format of the tab-delimited text files contained within. Each index file follows the PSI-MITAB2.5 format with additional columns for annotating edges and nodes. Each line in PSI-MITAB2.5 format represents a single interaction record from an experiment . Assignment of source interaction records to these redundant groups is described at http://irefindex.uio.no. The PSI-MI2.5 format plus additional columns are described at the end of the file.

Details on the build process are available from the publication PMID 18823568.

There are two sets of data free and proprietary. Free version includes only those data that may be freely distributed under the copyright license of the source database. This includes data from BIND, BioGRID, IntAct, MINT, MPPI and OPHID.

iRefIndex also integrates data from CORUM, DIP, HPRD and MPact. These data are not distributed publicly. These data may be made available to academic users under a collaborative agreement.

Contact ian.donaldson at biotek.uio.no if you are interested in using the iRefIndex database or would like your database included in the public release of the index.

Sources	http://irefindex.uio.no/wiki/Sources_iRefIndex_xxx
Statistics	http://irefindex.uio.no/wiki/Statistics_iRefIndex_xxx
Download location	ftp://ftp.no.embnet.org/irefindex/data/archive/xxx

Directory contents

README	pointer to this file at http://irefindex.uio.no/wiki/README_iRefIndex_MITAB_xxx
Sources	pointer to data files for this release at http://irefindex.uio.no/wiki/Sources_iRefIndex_xxx
Statistics	pointer to statisitics for this release at http://irefindex.uio.no/wiki/Statistics_iRefIndex_xxx
xxxx.mitab.mmddyyyy.txt.zip	individual indices in PSI-MITAB2.5 format

iRefIndex data is distributed as a set of tab-delimited text files with names of the form xxxx.mitab.mmddyyyy.txt.zip where mmddyyyy represents the file's creation date.

The complete index is available as All.mitab.mmddyyyy.txt.zip .

Taxon specific data sets are also available for:

	Taxon Id
Homo sapiens	9606 (human)
Mus musculus	10090 (mouse)
Rattus norvegicus	10116 (brown rat)
Caenorhabditis elegans	6239 (nematode)
Drosophila melanogaster	7227 (fruit fly)
Saccharomyces cerevisiae	4932 (baker's yeast)
Escherichia coli.	562 (E. Coli)
Other	other
All	all

Taxon specific subsets of the data are named xxxx.mitab.mmddyyyy.txt.zip where xxxx is the taxonomy identifier of at least one of the interactors according to either the source interaction database or the sequence database record. Each zip compressed file contains a single text file with the corresponding name xxxx.mitab.mmddyyyy.txt.

In some cases, other objects may belong to other taxons if a virus-host interaction is being represented or if a protein from another organism has been used to model a protein in the specified organism.

Taxonomy identifiers are provided in the data sets allowing these exceptions to be identified. The taxonomy identifiers listed are derived from the source protein sequence record. In some cases, this taxonomy identifier will be a child of the taxon listed in the file's title; for example, Escherichia coli K12 (taxonomy identifier 83333) will appear in the Escherichia coli (taxonomy identifier 562) file.

A description of the NCBI taxon identifiers is available at the following location:

http://www.ncbi.nlm.nih.gov/sites/entrez?db=taxonomy

The above data taxon division scheme leads to duplications; for instance, an interaction present in the mouse index could also appear in the human index if the interaction record lists protein sequence records from both human and mouse. The All.mitab.mmddyyyy file is a complete and non-redundant listing.

The data format and divisions provided in this initial release were chosen in the hopes that they would be immediately useful to the largest possible set of users. Other formats and divisions are possible and we welcome your input on future releases.

Changes from last version

xxx

Known Issues

xxx

Understanding the iRefIndex MITAB format

iRefIndex is distributed in PSI-MITAB format. This format was originally described in a recent PSI-MI paper (PMID 17925023).

Since this PSI-MITAB format allows for only two interactors to be described on each line, it is best suited for describing binary interaction data (the original experiment, say yeast two hybrid, gives a binary readout). However, other source PSI-MI XML source records will describe interactions involving only one interactor type (dimers or multimers) or they will contain associative or (a.k.a "n-ary") interaction data (say from immunoprecipitation experiments where the exact interactions between any pair of interactors are unknown. These cases are problematic for the PSI-MITAB format. This README describes exactly how we use the MITAB format to describe these alternate (non-binary) interaction types.

CHANGE

Each row in the MITAB file represents a **single** interaction records from one primary data source. Previously, each line represented a **collection** of interaction records where each member of this collection describes an interaction involving the exact same set of proteins (as defined by their primary sequence and taxon ids). We have moved to representing a single interaction on each line since this allows us to convey additional information about each of the original source records. Users can still "collapse" or find all lines that describe an interaction between the same set of proteins by using the "RIG" (column xxx). Rows with identical rigids (redundant interaction group identifiers) all describe interactions between the same set of proteins.

The natural keys for each interaction record in this group (i.e. the record identifiers from the source database) are listed under interactionIdentifier (column xxx). For example:

intact:EBI-761694

CHANGE

Our surrogate (primary) key for this group of redundant interaction records (RIG) is no longer listed in column xxx. Only, the source database record is listed in this column. The source db name and record id in are separated by a colon.

The RIG identifier is a 27 character key that is derived from the ROGIDs of the interactors involved in the interaction record (see columns xxx and xxx). The RIG identifier is listed (by itself) in column xxx for convenience. The ROGID is a SHA-1 digest of the protein interactor's primary amino acid sequence concatenated with the NCBI taxon id (see the paper for details).

Sometimes source interaction records in PSI-MI format only list one interactor. These are cases where either 1) an intramolecular interaction is being represented or 2) a multimer (3 or more) of some protein is being represented. These records are difficult to represent in the PSI-MITAB format because PSI-MITAB requires that each row (interaction) list two interactors. The way we handle this is to list the ROG identifier for the single interactor twice (once in each of columns xxx and xxx) of the MITAB. The RIG identifier for these interactions will be the SHA-1 digest of the interactor’s ROG id (see column xxx). These interactions are marked by a Y in column xxx (see the README).

Note that column xxx may also contain a C. This indicates that the MITAB entry describes membership of a protein in some complex. These entries correspond to PSI-MI records where more than two interactors are listed (associative interaction data; a.k.a. n-ary data cf. binary data). In these cases, the first column holds the ROG identifier of the complex and the second column contains the ROG id of the protein. We refer to this method of representation as a bi-partite model since there are two kinds of nodes corresponding to complexes and proteins.

As an example, let’s say that a source interaction record contained interactors A, B and C found by affinity purification and mass-spec where a tagged version of protein A was used as the bait protein to perform the immunoprecipitation.

Then we would represent the complex in the MITAB file using three lines: X-A, X-B, and X-C. All three entries would have the same string in column 1 (the RIG id for the complex). All three entries would have the same string in column 21 (again, the RIG id for the complex) All three entries would have a C in column xxx.

xxx

Other databases take an interaction record with multiple interactors (n-ary data) and make a list of binary interactions (based on the spoke or matrix model) and then list these binary interactions in the MITAB. For the example above, using a spoke model to transform the data into a set of binary interactions, these data would be represented using two lines in the MITAB file: A-B and A-C. Here A is chosen as the "hub" of the spoke model since it was the "bait" protein. For experimental systems that do not have "baits" and "preys" (e.g. x-ray crystallography), an arbitrary protein might be chosen as the bait.

Alternatively, a matrix model might be used to transform the n-ary data into a list of binary interactions. Here all pairwise combinations of interactors in the original n-ary data are represented as binary interactions. So, in the above example, the immunoprecipitated complex would be represented using three lines of the MITAB file: A-B, B-C, and A-C.

All three methods for representing n-ary data in a MITAB file (bi-partite, spoke, and matrix) are different representations of the same data.

We have chosen to use the bi-partite method of representation so that it is impossible to mistake spoke or matrix binary entries for true binary entries; the identifiers used for complexes will, of course, not appear in a protein database and any programme that tries to treat complex identifiers as though they were protein identifiers will fail. The method allows you to reconstruct the members of the original interaction record that describes a complex of proteins (say from an affinity purification experiment). From there, you can choose to make a spoke or matrix model by yourself if you want.

xxx Users are advised that other databases will use spoke and matrix model representations of complexes. In these cases, column xxx will indicate this fact. The pairs of proteins found in these entries do not necessarily represent observations of real binary interactions: they merely represent membership in some larger list of proteins observed to be somehow associated.

For binary interaction data, column xxx will contain an X. Two protein interactor ROGIDs will be listed in columns 1 and 2.

License

Data released on this public ftp site are released under the Creative Commons Attribution License http://creativecommons.org/licenses/by/2.5/. This means that you are free to use, modify and redistribute these data for personal or commercial use so long as you provide appropriate credit. See next section.

iRefIndex data distributed on the FTP site includes only those data that may be freely distributed under the copyright license of the source database. This includes data from BIND, BioGRID, IntAct, MINT, MPPI and OPHID.

iRefIndex also integrates data from CORUM, DIP, HPRD and MPact. These data are not distributed publicly. These data may be made available to academic users under a collaborative agreement.

Contact ian.donaldson at biotek.uio.no if you are interested in using the iRefIndex database or would like your database included in the public release of the index.

Copyright © 2008-2010 Ian Donaldson

Citation

Credit should include citing the iRefIndex paper (PMID 18823568) and any of the source databases upon which this resource is based. See http://irefindex.uio.no for appropriate citations.

Disclaimer

Data is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Description of PSI-MITAB2.5 file

Each line in this file represents either

1. an interaction between two proteins (binary interaction) or
2. the membership of a protein in some complex (complex membership) or
3. an interaction that involves only one protein type (multimer or self-interaction).

See column xxx for more details.

Column number: 1 (uidA)

Column name:	uidA
Column type:	String
Description:	Unique identifier for interactor A
Example:	irefindex:hhZYhMtr5JC1lGIKtR1wxHAd3JY83333

Notes This column contains a universal key for the interactor. It corresponds to the ROGID (redundant object group identifier) described in the original iRefIndex paper. PMID 18823568.

If this line (entry) describes a binary interaction between two proteins, then the protein with the 'ascibetically' (ASCII value sort order) larger ROGID is listed first as uidA. If this entry describes the membership of a protein in a complex, then the ROGID of the complex is always listed first as uidA and the protein's ROGID is listed as uidB (column 2). If this entry describes a an interaction involving only one protein type, then the ROGID of that protein is listed both as uidA and uidB.

The ROGID (redundant object group identifier) for proteins, consists of the SEGUID for the protein concatenated with the taxon identifier for the protein. For complex nodes, the ROGID is calculated as the SHA-1 digest of the ROGID's of all the protein participants (after first ordering them by ASCII-based lexicographical sorting in ascending order and concatenating them) See the iRefIndex paper for details. The SEGUID is always 27 characters long. So the ROGID will be composed of 27 characters concatenated with a taxon identifier for proteins.

These first two columns in the iRefIndex MITAB file facilitate integration of a third party's protein interaction data into this dataset using the universal method described in PMID 18823568.

CHANGE Note that the iRefIndex procedure maps all protein interactors to their canonical forms. See http://irefindex.uio.no/wiki/Canonicalization for a description. Protein references from the original interaction record (and a description of how they were mapped to the canonical form) can be found in the corresponding iRefWeb record. See column xxx and search for this interaction record at http://wodaklab.org/iRefWeb/.

Column number: 2 (uidB)

Column name:	uidB
Column type:	String
Description:	Unique identifier for interactor B
Example:	irefindex:ImnYkXur2U4xVdz5PVvprq8Zgd483333

Notes

See notes for column 1.

Column number: 3 (altA)

Column name:	altA
Column type:	a|b: pipe-delimited set of strings
Description:	Alternative identifiers for interactor A
Example:	uniprotkb:P23367|refseq:NP_418591|entrezgene/locuslink:948691

Notes

Each pipe-delimited entry is a database_name:accession pair delimited by a colon. Database names are taken from the MI controlled vocabulary at http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI Database references listed in this column may include the following:

uniprotkb

The accessions this protein is known by in UniProt(http://www.uniprot.org/). More information regarding this protein can be retrieved using this accession from UniProt. See the AC line in the flat file. http://au.expasy.org/sprot/userman.html#AC_line. Uniprot accessions are mapped to nodes using an exact match to the ROGID. If the node's ROGID maps to a specific isoform of the protein, then the Uniprot accession for the isoform is given.

refseq

If a protein accession exists in the RefSeq data base (http://www.ncbi.nlm.nih.gov/RefSeq/) that reference is indicated here. More information about this protein can be obtained from RefSeq using this accession. Refseq accessions are mapped to nodes using an exact match between the node's ROGID and the ROGID for the most recent version of the RefSeq accession.

entrezgene/locuslink

NCBI gene Identifiers for the gene encoding this protein. See ftp://ftp.ncbi.nlm.nih.gov/gene/DATA/gene2refseq column GeneID given protein's accession.version

other

If none of the three identifier types are available then other databasename:accession pairs will be listed. These database names may not follow the MI controlled vocabulary.

Example:

emb:CAA44868.1|gb:AAA23715.1|gb:AAB02995.1|emb:CAA56736.1|uniprot:P24991

irefindex

If the node represents a complex, then the rogid for the complex will be listed here, such as the following:

irefindex:xBr9cTXgzPLNxsaKiYyHcoEm/DM

Note that this column value may contain duplicate identifiers.

Column number: 4 (altB)

Column name:	altB
Column type:	a|b: pipe-delimited set of strings
Description:	Alternative identifiers for interactor B
Example:	uniprotkb:P06722|refseq:NP_417308|entrezgene/locuslink:947299

Notes

See notes for column 3.

Column number: 5 (aliasA)

Column name:	aliasA
Column type:	a|b: pipe-delimited set of strings
Description:	Aliases for interactor A
Example:	uniprotkb:MUTL_ECOLI|entrezgene/locuslink:mutL

Notes

Each pipe-delimited entry is a databasename:alias pair delimited by a colon. Database names are taken from the PSI-MI controlled vocabulary at http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI

Database names and sources listed in this column may include the following:

uniprotkb:entry name

the entry name given by UniProt. See Entry name in the ID line of the flat file. http://au.expasy.org/sprot/userman.html#ID_line

entrezgene/locuslink:symbol

the NCBI gene symbol for the gene encoding this protein. See ftp://ftp.ncbi.nlm.nih.gov/gene/DATA/gene_info column Symbol given GeneID

irefindex:complex

If the node is a complex then irefindex:complex will be listed here.

NA

NA may be listed here if aliases are Not Available

Column number: 6 (aliasB)

Column name:	aliasB
Column type:	a|b: pipe-delimited set of strings
Description:	Aliases for interactor B
Example:	uniprotkb:MUTH_ECOLI|entrezgene/locuslink:mutH

Notes

See notes for column 5.

Column number: 7 (Method)

Column name:	Method
Column type:	a|b: pipe-delimited set of strings
Description:	Interaction detection method
Example:	MI:0039(2h fragment pooling)

Notes

CHANGE

Only a single method will appear in this column. Previously, multiple methods appeared. Both the controlled vocabulary term identifier for the method (e.g. MI:0399) and the controlled vocabulary term short label in brackets (e.g. 2h fragment pooling) will appear in this column. See http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI to look up controlled vocabulary term identifiers.

The interaction detection method is from the orginal record. Path for PSI-MI 2.5:

entrySet/entry/experimentList/experimentDescription/interactionDetectionMethod/names/shortLabel/

CHANGE

If a controlled vocabulary term identifier was not provided by the source database then an attempt was made to use the supplied short label to find the correct term identifier. If a term identifier could not be found, then MI:0000 will appear before the shortLabels.

xxx Sabry check above

NA or -1 may appear in place of a recognised shortLabel.

For example:

MI:0000(-1)
MI:0000(NA)

Column number: 8 (author)

Column name:	author
Column type:	a|b: pipe-delimited set of strings
Description:
Example:	hall-1999-1|hall-1999-2|mansour-2001-1|mansour-2001-2|hall-1999

Notes

According to MITAB2.5 format this column should contain a pipe-delimited list of author surnames in which the interaction has been shown.

CHANGE

This column will usually include only one author name reference.

xxx Sabry Check this

Column number: 9 (pmids)

Column name:	pmids
Column type:	a|b: pipe-delimited set of strings
Description:	PubMed Identifiers
Example:	pubmed:9880500|pubmed:11585365

Notes

This is a non-redundant list of PubMed identifiers pointing to literature that supports the interaction. According to MITAB2.5 format, this column should contain a pipe delimited set of databaseName:identifier pairs such as pubmed:12345. The source database name is always pubmed.

CHANGE

This column will usually include only one pubmed reference.

xxx Sabry Check this

The special value - may appear in place of the identifiers.

Column number: 10 (taxa)

Column name:	taxa
Column type:	string
Description:	Taxonomy identifier for interactor A
Example:	taxid:83333

Notes

The NCBI taxonomy identifier listed here is that of the sequence record for the interactor and may be different than what is listed in the interaction record. See the methods section for more details. See the NCBI taxonomy database at http://www.ncbi.nlm.nih.gov/sites/entrez?db=taxonomy . According to MITAB2.5 format, this column should contain a pipe delimited set of databaseName:identifier pairs such as taxid:12345. The source database name has been listed as taxid since it is always NCBI's taxonomy database. The value in this column will be NA if the interactor is a complex.

Column number: 11 (taxb)

Column name:	taxb
Column type:	string
Description:	Taxonomy identifier for interactor B
Example:	taxid:83333

Notes

See notes for column 10.

Column number: 12 (interactionType)

Column name:	interactionType
Column type:	a|b: pipe-delimited set of strings
Description:	Interaction Type from controlled vocabulary or short label
Example:	MI:0218(physical interaction)

Notes

Taken from the PSI-MI controlled vocabulary and represented as...

database:identifier(interaction type)

...(when available in the interaction record) or Path for PSI-MI 2.5:

entrySet/entry/interactionList/interaction/interactionType/names/shortLabel

See http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI to lookup controlled vocabulary term identifiers for interaction types.

CHANGE

If the MI controlled vocabulary identifier was not provided by the source database, but a text description was provided, then an attempt was made to map the text to the correct controlled vocabulary term identifier. If this was not possible then MI:0000 is listed.

xxx Sabry discuss

NA may be listed here if the interaction type is not available (meaning that we could not find the interaction type in the record provided by the source database).

Column number: 13 (sourcedb)

Column name:	sourcedb
Column type:	String
Description:	Source databases containing this interaction
Example:	MI:0469(intact)

Notes

Taken from the PSI-MI controlled vocabulary and represented as...

database:identifier(sourceName)

See http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI to lookup controlled vocabulary term identifiers for database sources.

CHANGE Only one source database will be listed in each row.

Column number: 14 (interactionIdentifiers)

Column name:	interactionIdentifiers
Column type:	String
Description:	source interaction database and accession
Example:	intact:EBI-761694

Notes

Each reference is presented as a databaseName:identifier pair.

CHANGE

Only one source database reference will be listed in each row. The RIGID (from iRefIndex) is no longer listed in this column. See column xxx instead.

The source databaseNames that appear in this column are taken from the PSI-MI controlled vocabulary at http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI where possible

Interaction record identifiers are not available for mppi and ophid so these entries will appear as mppi:found and ophid:found

Sometimes, FOUND will appear as in:

intact:EBI-861910|intact:FOUND:1

xxx Sabry discuss this

Column number: 15 (confidence)

Column name:	confidence
Column type:	a|b: pipe-delimited set of strings
Description:	Confidence scores
Example:	lpr:1|hpr:12|np:1

Notes

Each reference is presented as a scoreName:score pair. Three confidence scores are provided: lpr, hpr and np.

PubMed Identifiers (PMIDs) point to literature references that support an interaction. A PMID may be used to support more than one interaction.

The lpr score (lowest pmid re-use) is the lowest number of distinct interactions (RIGIDs: see column 14) that any one PMID (supporting the interaction in this row) is used to support. A value of one indicates that at least one of the PMIDs supporting this interaction has never been used to support any other interaction. This likely indicates that only one interaction was described by that reference and that the present interaction is not derived from high throughput methods.

The hpr score (highest pmid re-use) is the highest number of interactions (RIGIDs: see column 14) that any one PMID (supporting the interaction in this row) is used to support. A high value (e.g. greater than 50) indicates that one PMID describes at least 50 other interactions and it is more likely that high-throughput methods were used.

The np score (number pmids) is the total number of unique PMIDs used to support the interaction described in this row.

- may appear in the score field, indicating the absence of a score value.

---

CHANGE

NEW

COLUMNS PAST THIS POINT (16 - 31) ARE PART OF THE NEW PSI-MITAB 2.6 FORMAT

Column number: 16 (expansion)

Column name:	expansion
Column type:	String
Description:	Model used to convert n-ary data into binary data for purpose of export in MITAB file
Example:	bipartite

Notes For iRefIndex, this column will always contain either bipartite or a dash ( - ).

Other databases may use either "spoke" or "matrix" in this column.

See Understanding_the_iRefIndex_MITAB_format at the top of this file for an explanation.

Column number: 17 (biological role A)

Column name:	biological role A
Column type:	String
Description:	Biological role of interactor A
Example:	-

Notes This column is not supported by iRefIndex at the moment and will always contain a dash ( - ). Other databases may include entries such as "MI:0501(enzyme)", MI:0502(enzyme target), MI:0580(electron acceptor), or MI:0499(unspecified role). See http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI to browse possible values for biological role.

Column number: 18 (biological role B)

Column name:	biological role B
Column type:	String
Description:	Biological role of interactor B
Example:	-

Notes See notes for column 17.

Column number: 19 (experimental role A)

Column name:	experimental role A
Column type:	String
Description:	Indicates the experimental role of the interactor (such as bait or prey).
Example:	MI:0496(bait)
Example:	MI:0498(prey)

Notes

This column indicates the experimental role (if any) that was played by interactor A (column 1).

iRefIndex will always use a dash ( - ) if the interactor does not fall into either the bait or prey category.

See http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI to see definitions of bait and prey. as well as browse other possible values of experimental role that may appear in this column for other databases.

Column number: 20 (experimental role B)

Column name:	experimental role B
Column type:	String
Description:	Indicates the experimental role of the interactor (such as bait or prey).
Example:	MI:0496(bait)
Example:	MI:0498(prey)

Notes

This column indicates the experimental role (if any) that was played by interactor B (column 2).

See notes above for column 19.

Column number: 21 (interactor type A)

Column name:	interactor type A
Column type:	string
Description:	describes the type of molecule that A is
Example:	MI:0326(protein)

Notes

For iRefIndex, this will always be one of...

MI:0326(protein)
MI:0315(protein complex)

Column number: 22 (interactor type B)

Column name:	interactor type B
Column type:	string
Description:	describes the type of molecule that B is
Example:	MI:0326(protein)

Notes

See column 21.

Column number: 23 (xrefs A)

Column name:	xrefs A
Column type:	string
Description:	xrefs for molecule A
Example:	-

Notes

This is not used by iRefIndex. A dash ( - ) will always appear in this column.

xxx

Discuss with Bruno. What is this meant for? MINT lists uniprotkb:YKR042W(UTH1)here for interactor uniprotkb:P36135.

Column number: 24 (xrefs A)

Column name:	xrefs A
Column type:	string
Description:	xrefs for molecule A
Example:	-

Notes

This is not used by iRefIndex. A dash ( - ) will always appear in this column.

xxx

Discuss with Bruno. What is this meant for? MINT lists uniprotkb:YKR042W(UTH1)here for interactor uniprotkb:P36135.

Column number: 25 (xrefs Interaction)

Column name:	xrefs Interaction
Column type:	string
Description:	xrefs for the interaction
Example:	-

Notes

This is not used by iRefIndex. A dash ( - ) will always appear in this column.

xxx

Discuss with Bruno. What is this meant for? MINT lists GO cellular components (place) here for 479 entries. Example, go:"GO:0048786"(presynaptic active zone) for MINT-7233649.

Column number: 26 (Annotations A)

Column name:	Annotations A
Column type:	string
Description:	Annotations for molecule A
Example:	-

Notes

This is not used by iRefIndex. A dash ( - ) will always appear in this column.

xxx

Discuss with Bruno. What is this meant for? MINT does not appear to use this column.

Column number: 27 (Annotations B)

Column name:	Annotations B
Column type:	string
Description:	Annotations for molecule B
Example:	-

Notes

This is not used by iRefIndex. A dash ( - ) will always appear in this column.

xxx

Discuss with Bruno. What is this meant for? MINT does not appear to use this column.

Column number: 28 (Host organism taxid)

Column name:	Host organism taxid
Column type:	string
Description:	Host organism taxid where the interaction was experimentally demonstrated
Example:	-

Notes

This is not used by iRefIndex. A dash ( - ) will always appear in this column.

xxx

Discuss with Bruno. Confirm that this was for the experimental organism. MINT uses this column. Example entries are

-

taxid:-1(in vitro)

taxid:-4(in vivo)

taxid:10090(Mus musculus)

Also, I notice that MINT has inserted a column before this (not is the standard) called "Interaction Annotations" where they list figure legend references (presumably where the interaction is described). Do you know anything about this? Is it part of MITAB2.6 .Example entries are

figure-legend:F1A|figure-legend:F1B

prediction score:432|comment:prediction based on phage display consensus

author-confidence:8 85|figure-legend:ST2

comment:AD-ORFeome library used in the experiment. Interaction of the NON_CORE set.|number of hits:1

pbs signal:-8.966|pbs category:B|figure-legend:NFA

using the tandem affinity purification technology (TAP). The prey proteins were identified in parallel experiments by MALDI-TOF/MS and LC-MS/MS analysis. A core dataset of binary interaction was generated by a machine learning procedure assigning a confidence score to each interactions. All the interactions belonging to the core dataset display a confidence score higher than 0.273. In MINT are collected only the interactions belonging to the core dataset. For each interaction the confidence score is reported. For each protein identified by MALDI-TOF/MS the numbers of peptides detected are reported the Z-score provides confidence measure for the identification of the protein. For each protein identified by LC-MS/MS numbers of peptides detected are reported the probability value provides confidence measure for the identification of the protein. All the original datasets provided by the authors are available at the following URL : ftp://mint.bio.uniroma2.it/pub/data/krogan-2006

url:AS251102_218_12_DTASelect_COMBINED.html|probability:99|number of peptides:7|reliability

cumulative hits:1|independent hits:1|comment:(high throughput data)|figure-legend:ST3

This column is not documented. README for MINT MITAB is out of date and does not reflect changes in 2.6

Column number: 29 (parameters Interaction)

Column name:	parameters Interaction
Column type:	string
Description:	Host organism taxid where the interaction was experimentally demonstrated
Example:	-

Notes

This is not used by iRefIndex. A dash ( - ) will always appear in this column.

Discuss with Bruno. What is this column for?

MINT does not seem to use this column

Column number: 30 (dataset)

Column name:	dataset
Column type:	b (pipe-delimited set of strings
Description:	datasets to which this entry belongs to
Example:	-

Notes

This is not used by iRefIndex. A dash ( - ) will always appear in this column.

xxx

Discuss with Bruno. What is this column for?

MINT uses this column for entries like

dataset:Mammalia|dataset:Viruses|dataset:mint|dataset:virusmint|dataset:ADENOVIRUS|dataset:virhostome

Is this agreed on?

Column number: 31 (Caution Interaction)

Column name:	Caution Interaction
Column type:	string
Description:	notes regarding curation of the record?
Example:	-

Notes

This is not used by iRefIndex. A dash ( - ) will always appear in this column.

Discuss with Bruno. What is this column for?

MINT uses this column for:

caution:only a selection of interactions described in this publication have been curated

curation-level:light-curation

curation-level:MIMIx

curation-level:MIMIx|caution:only a selection of interactions described in this publication have been curated

negative:the interactions are not observed under these experimental conditions

Column number: 16 (entrezGeneA)

Column name:	entrezGeneA
Column type:	pipe delimited list of integers or a string
Description:	EntrezGene identifier(possibly a pipe-delimited list) for interactor A
Example:	947299

Notes

If an EntrezGene identifier is not found for the interactor, then a ROGID will appear in this column (see notes to column 1).

If the interactor is a node representing a complex, then the ROGID for the complex will appear here.

Column number: 17 (entrezGeneB)

Column name:	entrezGeneB
Column type:	Integer
Description:	EntrezGene identifier for interactor B
Example:	948691

Notes

See notes for column 16.

Column number: 18 (atype)

Column name:	atype
Column type:	string
Description:	Is interactor A a protein or a complex?
Example:	MI:0326(protein)

Notes

This will always be one of...

MI:0326(protein)
MI:0315(protein complex)

Column number: 19 (btype)

Column name:	btype
Column type:	string
Description:	Is interactor B a protein or a complex?
Example:	MI:0326(protein)

Notes

See column 18.

Column number: 20 (rigid)

Column name:	rigid
Column type:	string
Description:	Redundant interaction group identifier
Example:	3ERiFkUFsm7ZUHIRJTx8ZlHILRA

Notes

The RIGID (for redundant interaction group identifier) consists of the ROG identifiers for each of the protein participants (see notes above) ordered by ASCII-based lexicographic sorting in ascending order, concatenated and then digested with the SHA-1 algorithm. See the iRefIndex paper for details. This identifier points to a set of redundant protein-protein interactions that involve the same set of proteins with the exact same primary sequences.

Column number: 21 (edgetype)

Column name:	edgetype
Column type:	Character
Description:	Does the edge represent a binary interaction (X), complex membership (C), or a multimer (Y)?
Example:	X

Notes

Edges can be labelled as either X, C or Y:

X

a binary interaction with two protein participants

C

denotes that a protein is part of some complex of proteins. One of the nodes is a protein. The other node represents a complex of proteins (see columns 18-19). The edge represents the idea that the protein is a member of the complex.

Y

for dimers and polymers. In case of dimers and polymers when the number of subunits is not described in the original interaction record, the edge is labelled by a Y. Interactor A (column 1) will be identical to the Interactor B (column 2). The graphical representation of this will appear as a single node connected to itself (loop). The actual number of self-interacting subunits may be 2 (dimer) or more (say 5 for a pentamer). Refer to the original interaction record for more details and see column 22.

Column 1, Column 21 and Column 2 are all concatenated into a single space-delimited identifier to create the interaction identifier when this file is imported into Cytoscape; for example:

qE03bpSsQiJouJbn6ISt8DnD/pA9606 (X) E4tMCoGbaqAfjU8QXbQzbAb8fGQ9606

Column number: 24 (numParticipants)

Column name:	numParticipants
Column type:	Integer
Description:	Number of participants in the interaction
Example:	2

Notes

• For edges labelled X (see column 21) this value will be two.
• For edges labelled C, this value will be equivalent to the number of protein subunits included in the complex(represented by the complex node).
• For interactions labelled Y, this value will either be the number of self-interacting subunits (if present in the original interaction record) or 1 where the exact number of subunits is unknown or unspecified.

Column number: 25 (ROGA)

Column name:	ROGA
Column type:	Integer
Description:	Integer representation of uidA
Example:	617653

Column number: 26 (ROGB)

Column name:	ROGB
Column type:	Integer
Description:	Integer representation of uidB
Example:	4052696

Column number: 27 (interaction_name)

Column name:	interaction_name
Column type:	String
Description:	The name of the interaction,
Example:	MTA1-HDAC core complex

Notes

• A name was selected from the original interaction data provided when available.
• When no interaction name available a name was constructed using the names of the interactors (e.g.Interaction involving HCK_HUMAN and RASA1_HUMAN).

COLUMNS PAST THIS POINT (32 -) ARE NOT DEFINED BY THE PSI-MITAB2.6 STANDARD. THESE COLUMNS ARE SPECIFIC TO THIS IREFINDEX RELEASE AND MAY CHANGE FROM ONE RELEASE TO ANOTHER

old columns

Column number: 14 (interactionIdentifiers)

Column name:	interactionIdentifiers
Column type:	String
Description:	source interaction database and accession
Example:	intact:EBI-761694

Notes

Each reference is presented as a databaseName:identifier pair.

CHANGE

Only one source database reference will be listed in each row. The RIGID (from iRefIndex) is no longer listed in this column.

The identifier given for irefindex is the RIGID. The RIGID (for redundant interaction group identifier) consists of the two node identifiers (see columns 1 and 2) concatenated and then digested with the SHA-1 algorithm. The two node identifiers are ordered in columns one and two according to ASCII-based lexicographical sorting in ascending order. See the iRefIndex paper for details. The RIGID points to a set of redundant protein-protein interactions that involve the same set of proteins with the exact same primary sequences. The source databaseNames that appear in this column are taken from the PSI-MI controlled vocabulary at http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI where possible

Interaction record identifiers are not available for mppi and ophid so these entries will appear as mppi:found and ophid:found

Sometimes, FOUND will appear as in:

intact:EBI-861910|intact:FOUND:1