-
Notifications
You must be signed in to change notification settings - Fork 1
/
MITAB27Format.html
852 lines (375 loc) · 41.3 KB
/
MITAB27Format.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
<!DOCTYPE HTML>
<html lang="" >
<head>
<title>MITAB 2.7 · GitBook</title>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<meta name="description" content="">
<meta name="generator" content="GitBook 3.1.1">
<link rel="stylesheet" href="gitbook/style.css">
<link rel="stylesheet" href="gitbook/gitbook-plugin-highlight/website.css">
<link rel="stylesheet" href="gitbook/gitbook-plugin-search/search.css">
<link rel="stylesheet" href="gitbook/gitbook-plugin-fontsettings/website.css">
<meta name="HandheldFriendly" content="true"/>
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black">
<link rel="apple-touch-icon-precomposed" sizes="152x152" href="gitbook/images/apple-touch-icon-precomposed-152.png">
<link rel="shortcut icon" href="gitbook/images/favicon.ico" type="image/x-icon">
<link rel="next" href="MITAB28Format.html" />
<link rel="prev" href="MITAB26Format.html" />
</head>
<body>
<div class="book">
<div class="book-summary">
<div id="book-search-input" role="search">
<input type="text" placeholder="Type to search" />
</div>
<nav role="navigation">
<ul class="summary">
<li class="chapter " data-level="1.1" data-path="./">
<a href="./">
Introduction
</a>
<ul class="articles">
<li class="chapter " data-level="1.1.1" data-path="PsicquicSpecification.html">
<a href="PsicquicSpecification.html">
Specification
</a>
<ul class="articles">
<li class="chapter " data-level="1.1.1.1" data-path="PsicquicSpec_1_4_Soap.html">
<a href="PsicquicSpec_1_4_Soap.html">
SOAP
</a>
</li>
<li class="chapter " data-level="1.1.1.2" data-path="PsicquicSpec_1_4_Rest.html">
<a href="PsicquicSpec_1_4_Rest.html">
REST
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.1.2" data-path="Registry.html">
<a href="Registry.html">
Registry
</a>
<ul class="articles">
<li class="chapter " data-level="1.1.2.1" data-path="PsicquicServiceTags.html">
<a href="PsicquicServiceTags.html">
Registry Service Tags
</a>
</li>
<li class="chapter " data-level="1.1.2.2" data-path="RegistryJavaClient.html">
<a href="RegistryJavaClient.html">
Java client
</a>
</li>
</ul>
</li>
</ul>
</li>
<li class="chapter " data-level="1.2" data-path="MiqlDefinition.html">
<a href="MiqlDefinition.html">
Usage MIQL
</a>
<ul class="articles">
<li class="chapter " data-level="1.2.1" data-path="MiqlReference.html">
<a href="MiqlReference.html">
MIQL Reference 2.5
</a>
</li>
<li class="chapter " data-level="1.2.2" data-path="MiqlReference27.html">
<a href="MiqlReference27.html">
MIQL Extension 2.7
</a>
</li>
<li class="chapter " data-level="1.2.3" data-path="MiqlReference28.html">
<a href="MiqlReference28.html">
MIQL Extension 2.8
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.3" data-path="Clients.html">
<a href="Clients.html">
Clients
</a>
<ul class="articles">
<li class="chapter " data-level="1.3.1" >
<a target="_blank" href="http://www.bioconductor.org/packages/release/bioc/html/PSICQUIC.html">
R Bioconductor package
</a>
</li>
<li class="chapter " data-level="1.3.2" data-path="JavaClient.html">
<a href="JavaClient.html">
Java
</a>
</li>
<li class="chapter " data-level="1.3.3" data-path="PerlCodeSamples.html">
<a href="PerlCodeSamples.html">
Perl
</a>
</li>
<li class="chapter " data-level="1.3.4" data-path="PythonCodeSamples.html">
<a href="PythonCodeSamples.html">
Python
</a>
</li>
<li class="chapter " data-level="1.3.5" data-path="CytoscapeClient.html">
<a href="CytoscapeClient.html">
Cytoscape
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.4" data-path="formats.html">
<a href="formats.html">
Formats
</a>
<ul class="articles">
<li class="chapter " data-level="1.4.1" data-path="PSIMITAB.html">
<a href="PSIMITAB.html">
PSI-MI TAB
</a>
<ul class="articles">
<li class="chapter " data-level="1.4.1.1" data-path="MITAB25Format.html">
<a href="MITAB25Format.html">
MITAB 2.5
</a>
</li>
<li class="chapter " data-level="1.4.1.2" data-path="MITAB26Format.html">
<a href="MITAB26Format.html">
MITAB 2.6
</a>
</li>
<li class="chapter active" data-level="1.4.1.3" data-path="MITAB27Format.html">
<a href="MITAB27Format.html">
MITAB 2.7
</a>
</li>
<li class="chapter " data-level="1.4.1.4" data-path="MITAB28Format.html">
<a href="MITAB28Format.html">
MITAB 2.8
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.4.2" data-path="PSIMIXML.html">
<a href="PSIMIXML.html">
PSI-MI XML
</a>
<ul class="articles">
<li class="chapter " data-level="1.4.2.1" data-path="MIXML25Format.html">
<a href="MIXML25Format.html">
PSI-MI XML 2.5
</a>
</li>
<li class="chapter " data-level="1.4.2.2" data-path="MIXML30Format.html">
<a href="MIXML30Format.html">
PSI-MI XML 3.0
</a>
</li>
<li class="chapter " data-level="1.4.2.3" >
<a target="_blank" href="https://github.com/MICommunity/psi-jami/tree/master/jami-xml">
Java Examples
</a>
</li>
</ul>
</li>
</ul>
</li>
<li class="divider"></li>
<li class="chapter " data-level="2.1" data-path="PsicquicServiceProviders.html">
<a href="PsicquicServiceProviders.html">
Service providers
</a>
<ul class="articles">
<li class="chapter " data-level="2.1.1" data-path="HowToInstallPsicquicSolr.html">
<a href="HowToInstallPsicquicSolr.html">
How to install PSICQUIC Solr (recommened)
</a>
<ul class="articles">
<li class="chapter " data-level="2.1.1.1" data-path="HowToInstallPsicquicAndSolrJetty.html">
<a href="HowToInstallPsicquicAndSolrJetty.html">
Single jetty server
</a>
</li>
<li class="chapter " data-level="2.1.1.2" data-path="HowToInstallPsicquicSolrDifferentServers.html">
<a href="HowToInstallPsicquicSolrDifferentServers.html">
Using a solr server independent from the PSICQUIC server
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="2.1.2" data-path="HowToInstallPsicquicLucene.html">
<a href="HowToInstallPsicquicLucene.html">
How to install PSICQUIC using LUCENE
</a>
<ul class="articles">
<li class="chapter " data-level="2.1.2.1" data-path="HowToInstall.html">
<a href="HowToInstall.html">
Using LUCENE
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="2.1.3" data-path="DataDistributionBestPractices.html">
<a href="DataDistributionBestPractices.html">
Data Distribution Best Practices
</a>
</li>
<li class="chapter " data-level="2.1.4" data-path="DataEnricher.html">
<a href="DataEnricher.html">
Data Enricher
</a>
</li>
<li class="chapter " data-level="2.1.5" data-path="Faq.html">
<a href="Faq.html">
FAQ
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="2.2" data-path="WhoUsesPsicquic.html">
<a href="WhoUsesPsicquic.html">
Who uses PSICQUIC?
</a>
</li>
<li class="chapter " data-level="2.3" data-path="PreparingARelease.html">
<a href="PreparingARelease.html">
How to release the project
</a>
</li>
<li class="divider"></li>
<li>
<a href="https://www.gitbook.com" target="blank" class="gitbook-link">
Published with GitBook
</a>
</li>
</ul>
</nav>
</div>
<div class="book-body">
<div class="body-inner">
<div class="book-header" role="navigation">
<!-- Title -->
<h1>
<i class="fa fa-circle-o-notch fa-spin"></i>
<a href="." >MITAB 2.7</a>
</h1>
</div>
<div class="page-wrapper" tabindex="-1" role="main">
<div class="page-inner">
<div id="book-search-results">
<div class="search-noresults">
<section class="normal markdown-section">
<h1 id="psi-mi-tab-27-format">PSI-MI TAB 2.7 Format</h1>
<h2 id="introduction">Introduction</h2>
<p>The MITAB27 format is an extention of the PSI-MI 2.5 (1) and 2.6 standard. It has been derived from the tabular format provided by BioGrid. MITAB27 only describes binary interactions, one pair of interactors per row. Columns are separated by tabulations. Tools allowing to manipulate this data format are available (2).</p>
<p>(1) <a href="http://www.pubmedcentral.nih.gov/articlerender.fcgi?tool=pubmed&pubmedid=17925023" target="_blank">http://www.pubmedcentral.nih.gov/articlerender.fcgi?tool=pubmed&pubmedid=17925023</a></p>
<p>(2) <a href="http://www.psidev.info/groups/molecular-interactions" target="_blank">http://www.psidev.info/groups/molecular-interactions</a> (Tools section)</p>
<h2 id="column-definitions">Column definitions</h2>
<p>The column contents should be as follows:</p>
<ol>
<li><strong>Unique identifier for interactor A</strong>, represented as databaseName:identifier, where databaseName is the name of the corresponding database as defined in the <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI:0444&termName=database%20citation" target="_blank">PSI-MI controlled vocabulary</a>, and identifier is the unique primary identifier of the molecule in the database. Even though identifiers from multiple databases can be separated by "|", it is recommended to give only one identifier in this column. It is recommended that proteins be identified by stable identifiers such as their UniProtKB or RefSeq accession number. Small molecules should have Chebi identifiers, nucleic acids should have embl/ddbj/genbank identifiers and gene should have entrez gene/locuslink, ensembl, or ensemblGenome identifiers. This column should never be empty ('-') except for describing intra-molecular interactions or auto-catalysis. <em>Ex: uniprotkb:P12346</em></li>
<li><strong>Unique identifier for interactor B</strong>.</li>
<li><strong>Alternative identifier for interactor A</strong>, represented as databaseName:ac, where databaseName is the name of the corresponding database as defined in the <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI:0444&termName=database%20citation" target="_blank">PSI-MI controlled vocabulary</a>, and ac is the primary identifier of the molecule in the database. Multiple identifiers separated by "|". It is recommended to only give database identifiers in this column. Other cross references for interactor A such as GO xrefs should be moved to the column 'Interactor xrefs A' and interactor names such as gene names should be moved to the column 'Alias A'. <em>Ex: refseq:NP_001013128|ensembl:ENSRNOP00000012946</em></li>
<li><strong>Alternative identifier for interactor B</strong>.</li>
<li><strong>Aliases for A</strong>, separated by "|". Representation as databaseName:name(alias type), where databaseName is the name of the corresponding database as defined in the <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI:0444&termName=database%20citation" target="_blank">PSI-MI controlled vocabulary</a>, name is the alias name and alias type is the name of the corresponding alias type as defined in the <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A0300&termName=alias%20type" target="_blank">PSI-MI controlled vocabulary</a>. In the absence of databaseName, one can use <code>unknown</code>. Multiple names separated by "|". In parenthesis, 'display_short' and 'display_long' are used to describe what name can be used for network display. <em>Ex: uniprotkb:Tf(gene name)|uniprotkb:Serotransferrin(recommended name)|uniprotkb:Tf(display_short)</em></li>
<li><strong>Aliases for B</strong>.</li>
<li><strong>Interaction detection methods</strong>, taken from the corresponding <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI:0001&termName=interaction%20detection%20method" target="_blank">PSI-MI controlled Vocabulary</a>, and represented as databaseName:identifier(methodName), separated by "|". As the detection methods are taken from the PSI-MI ontology, the database name is 'psi-mi'. Interaction detection method is recommended by MIMIx and can be used for scoring interactions so it is recommended to always give this information. It is also recommended to give one interaction detection method per MITAB line (for clustering purposes). <em>Ex: psi-mi:"MI:0006"(anti bait coimmunoprecipitation)</em></li>
<li><strong>First author</strong> surname(s) of the publication(s) followed by 'et al.' and the publication year in parenthesis, <em>e.g. Ciferri et al.(2005)</em>. Separated by "|".</li>
<li><strong>Identifier of the publication</strong> in which this interaction has been shown. Database name taken from the <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI:0445&termName=literature%20database" target="_blank">PSI-MI controlled vocabulary</a>, represented as databaseName:identifier. Multiple identifiers separated by "|". The publication identifier is used for clustering interactions from different data providers in PSICQUIC and can be used for scoring interactions so it is recommended to always give this information. It is recommended to give one pubmed id per MITAB line and IMEx ids can be added. <em>Ex: pubmed:16980971|imex:IM-1</em></li>
<li><strong>NCBI Taxonomy identifier for interactor A</strong>. represented as taxid:identifier(organism name) where the identifier is the taxon id of the organism and organism name can either be the common name or scientific name. Even though multiple identifiers can be separated by "|", it is recommended to have one organism per interactor per MITAB line. If both scientific name and common name are given, they should be represented with : <em>taxid:id1(common name1)|taxid:id1(scientific name1)</em>. Note: Currently no taxonomy identifiers other than NCBI taxid are anticipated, apart from the use of -2 to indicate "chemical synthesis" and -3 indicates "unknown". It is recommended to always give this information for proteins and genes. For small molecules and nucleic acids, this information should be given when available but can be left empty ('-') if not relevant.</li>
<li><strong>NCBI Taxonomy identifier for interactor B</strong>.</li>
<li><strong>Interaction types</strong>, taken from the corresponding <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI:0190&termName=interaction%20type" target="_blank">PSI-MI controlled vocabulary</a>, and represented as dataBaseName:identifier(interactionType), separated by "|". As the interaction types are taken from the PSI-MI ontology, the database name is 'psi-mi'. Interaction type can be used for scoring interactions so it is recommended to always give this information. It is also recommended to give one interaction type per MITAB line (for clustering purposes). <em>Ex: psi-mi:"MI:0914"(association)</em></li>
<li><strong>Source databases</strong> and identifiers, taken from the corresponding <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI:0444&termName=database%20citation" target="_blank">PSI-MI controlled vocabulary</a>, and represented as databaseName:identifier(sourceName). As the detection methods are taken from the PSI-MI ontology, the database name is 'psi-mi'. Multiple source databases can be separated by "|". When the interaction has been imported and reported by different sources, it is recommended to give the original source plus the source that currently reports the interaction. <em>Ex: psi-mi:"MI:0469"(intact)|psi-mi:"MI:0923"(irefindex)</em></li>
<li><strong>Interaction identifier(s)</strong> in the corresponding source database, represented by databaseName:identifier. It is recommended to always give a unique identifier per interaction (binary and n-ary) so in case of complexes which have been expanded, it would be possible to retrieve and re-build the original complex based on the interaction identifier. IrefIndex IDs go into the interaction checksum field. Other interaction references such as GO references go into the interaction xref field. <em>Ex: intact:EBI-1547321|imex:IM-11865-3</em></li>
<li><strong>Confidence score</strong>. Denoted as scoreType:value where scoreType is taken from the corresponding <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A1064&termName=interaction%20confidence" target="_blank">PSI-MI controlled vocabulary</a>. Multiple scores separated by "|". <em>Ex: author-score:0.60|author-score:high|intact-miscore:0.36784992</em></li>
<li><strong>Complex expansion</strong>. Model used to convert n-ary interactions into binary interactions for purpose of export in MITAB file. It should be represented as databaseName:identifier(expansion name) and taken from the corresponding <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A1059&termName=complex%20expansion" target="_blank">PSI-MI controlled vocabulary</a>. It is recommended to always give this information when n-ary interactions have been expanded. In case of true binary interactions, this column should be empty ('-'). <em>Ex: psi-mi:"MI:1060"(spoke expansion)</em></li>
<li><strong>Biological role A</strong> , taken from the corresponding <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A0500&termName=biological%20role" target="_blank">PSI-MI controlled vocabulary</a>, and represented as dataBaseName:identifier(biological role name), separated by "|". As the biological roles are taken from the PSI-MI ontology, the database name is 'psi-mi'. Biological roles are recommended by MIMIx so it is recommended to always give this information. When the participant A does not have any specific biological roles, the term 'unspecified role' (MI:0499) should be used. <em>Ex: psi-mi:"MI:0684"(ancillary)</em></li>
<li><strong>Biological role B</strong>.</li>
<li><strong>Experimental role A</strong> , taken from the corresponding <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A0495&termName=experimental%20role" target="_blank">PSI-MI controlled vocabulary</a>, and represented as dataBaseName:identifier(experimental role name), separated by "|". As the experimental roles are taken from the PSI-MI ontology, the database name is 'psi-mi'. Experimental roles are recommended by MIMIx so it is recommended to always give this information. When the participant A does not have any specific experimental roles, the term 'unspecified role' (MI:0499) should be used. <em>Ex:psi-mi:"MI:0496"(bait)</em></li>
<li><strong>Experimental role B</strong> .</li>
<li><strong>Interactor type A</strong> , taken from the corresponding <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A0313&termName=interactor%20type" target="_blank">PSI-MI controlled vocabulary</a>, and represented as dataBaseName:identifier(interactor type name), separated by "|". As the interactor types are taken from the PSI-MI ontology, the database name is 'psi-mi'. It is recommended to always give this information as it can be useful for recognizing protein-protein, small molecule-proteins, nucleic acids-proteins and gene-proteins interactions. <em>Ex: psi-mi:"MI:0326"(protein)</em></li>
<li><strong>Interactor type B</strong>.</li>
<li><strong>Xref for interactor A</strong>, represented as databaseName:ac(text), where databaseName is the name of the corresponding database as defined in the <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI:0444&termName=database%20citation" target="_blank">PSI-MI controlled vocabulary</a>, and ac is the primary accession of the molecule in the database. For example the gene ontology cross references associated. The text can be used to describe the qualifier type of the cross reference (see the corresponding <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A0353&termName=cross-reference%20type" target="_blank">PSI-MI controlled vocabulary</a>) or could be used to give the name of the GO term in case of cross references to ontology databases. Multiple cross references separated by "|". This column aims at adding more information to describe the interactor A but cannot be used to identify the interactor A. If some sequence database accessions are ambiguous (Ex : uniprot secondary accessions that are shared between different uniprot entries and so cannot be used as identifiers of interactor A), it is possible to report them in this column. <em>Ex: go:"GO:0003824"(catalytic activity)</em></li>
<li><strong>Xref for interactor B</strong>.</li>
<li><strong>Xref for the interaction</strong>, represented as databaseName:ac(text), where databaseName is the name of the corresponding database as defined in the <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI:0444&termName=database%20citation" target="_blank">PSI-MI controlled vocabulary</a>, and ac is the primary accession in the database. For example the gene ontology cross references associated (components, etc.) or OMIM cross references. Multiple cross references separated by "|". The text can be used to describe the qualifier type of the cross reference (see the corresponding <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A0353&termName=cross-reference%20type" target="_blank">PSI-MI controlled vocabulary</a>) or could be used to give the name of the GO term in case of cross references to ontology databases. Note, that this field is not meant not store interaction accessions or interaction checksums in this field. <em>Ex:go:"GO:0005643"(nuclear pore)</em></li>
<li><strong>Annotations for interactor A</strong>, represented as topic:"text", where topic is the name of the topic as defined in the <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A0590&termName=attribute%20name" target="_blank">PSI-MI controlled vocabulary</a> and text is free text associated with the topic (linebreak and other MITAB reserved characters should be properly escaped, replaced and/or removed). For example comments about this interactor : <em>comment:"sequence not available in uniprotKb"</em>. The text is optional and only a topic could be given, <em>e.g. anti-bacterial</em>. Multiple annotations separated by "|".</li>
<li><strong>Annotations for Interactor B</strong>.</li>
<li><strong>Annotations for the interaction</strong>, represented as topic:"text", where topic is the name of the topic as defined in the <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A0590&termName=attribute%20name" target="_blank">PSI-MI controlled vocabulary</a> and text is free text associated with the topic (linebreak and other MITAB reserved characters should be properly escaped, replaced and/or removed). For example figure legends : <em>figure legend:"Supp Tables 1 and 2"</em>. The text is optional and only a topic could be given. This column would also be used for tagging interactions and in such a case, topics for tags are also defined in the <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A1045&termName=curation%20content" target="_blank">PSI-MI controlled vocabulary</a> except for the complex expansion tags that have their own column. <em>Ex: internally-curated</em> Multiple annotations separated by "|".</li>
<li><strong>NCBI Taxonomy identifier for the host organism</strong>. represented as taxid:identifier(organism name) where the identifier is the taxon id of the organism and organism name can either be the common name or scientific name. Multiple identifiers can be separated by "|". Cells and tissues cannot be described in this column. If both scientific name and common name are given, they should be represented with : <em>taxid:id1(common name1)|taxid:id1(scientific name1)</em>. Note: Currently no taxonomy identifiers other than NCBI taxid are anticipated, apart from the use of -1 to indicate "in vitro", -2 to indicate "chemical synthesis", -3 indicates "unknown", -4 indicates "in vivo" and -5 indicates "in silico".</li>
<li><strong>Parameters of the interaction</strong>, for example kinetics. Representation as type:value(text). The type can be taken from the corresponding <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A0640&termName=parameter%20type" target="_blank">PSI-MI controlled vocabulary</a>. Multiple parameters separated by "|". <em>Ex: kd:"4.0x2^5 ~0.3"</em></li>
<li><strong>Creation date</strong> when the curation of the publication started. Representation as yyyy/mm/dd. This field is equivalent to the release date in the PSI-XML schema. <em>Ex:2010/10/17</em></li>
<li><strong>Update date</strong> when the interaction was updated for the last time. <em>Ex:2011/12/13</em> Representation as yyyy/mm/dd. This field does not have any equivalence in PSI-XML (could be the release date as well) and helps to keep track of changes in curated data.</li>
<li><strong>Checksum for interactor A</strong>, for instance the ROGID of the interactor which takes into consideration both the sequence and the organism of the interactor. Representation as methodName:checksum where methodName is the name of the method used to create the checksum. It is recommended to give the ROGID and CROGID for proteins and the standard Inchi key for small molecules. <em>Ex: rogid:UcdngwpTSS6hG/pvQGgpp40u67I9606|crogid:UcdngwpTSS6hG/pvQGgpp40u67I9606</em></li>
<li><strong>Checksum for interactor B</strong>.</li>
<li><strong>Checksum for interaction</strong>, for instance the RIGID of the interaction. Representation as methodName:checksum where methodName is the name of the method used to create the checksum. <em>Ex: rigid:"+++94o2VtVJcuk6jD3H2JZXaVYc"</em></li>
<li><strong>negative</strong> Boolean value to distinguish positive interactions (false) from negative interactions (true). By default, if the column is empty ('-'), the negative value is considered to be false (positive interaction). <em>Ex: true</em></li>
<li><strong>Feature(s) for interactor A</strong>: describe features for participant A such as binding sites, PTMs, tags, etc. Represented as feature_type:range(text), where feature_type is the feature type as described in the <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A0116&termName=feature%20type" target="_blank">PSI-MI controlled vocabulary</a>. For the PTMs, the MI ontology terms are obsolete and the <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MOD" target="_blank">PSI-MOD ontology</a> should be used instead. The text can be used for feature type names, feature names, interpro cross references, etc. For instance : sufficient to bind:27-195,201-133 (IPR000785). The use of the following characters is allowed to describe a range position : ‘?’ (undetermined position), ‘n’ (n terminal range), ‘c’ (c-terminal range), ‘>x’ (greater than x), ‘<’ (less than x), ‘x1..x1’ (fuzzy range position <em>Ex : 5..5-9..10</em>). The character '-' is used to separate start position(s) from end position(s). Multiple features separated by '|'. Multiple ranges per feature separated by ','. However, It is not possible to represent linked features/ranges. <em>Ex: gst tag:n-n(n-terminal region)|sufficient to bind:23-45. or binding site:23..24-46,33-33</em></li>
<li><strong>Feature(s) for interactor B</strong>.</li>
<li><strong>Stoichiometry for interactor A</strong>: A numerical value describing the count of instance of the molecule participating in the interaction. If no stoichiometry is available for interactor A, the column should be empty ('-'), otherwise a positive Integer value should be given. Several specific cases should be taken into consideration : in case of auto-catalysis, only one interactor is given and the stoichiometry should be 1. In case of homodimers, homotrimers, etc., the stoichiometry of one interactor should be 0 and the stoichiometry of the other should be a valid positive Integer. In case of homo-oligomer, the stoichiometry of both interactors should be 0. Example: for self interactors e.g. a kinase occluding its kinase domain by an internal phospho-tyrosine/SH2 domain interaction, only Interactor A column will show the molecule accession number with the stoichiometry 1. The columns for Interactor B will be empty. <em>Ex: 4</em></li>
<li><strong>Stoichiometry for interactor B</strong>.</li>
<li><strong>Participant identification method for interactor A</strong>: taken from the corresponding <a href="http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=MI&termId=MI%3A0002&termName=participant%20identification%20method" target="_blank">PSI-MI controlled Vocabulary</a>, and represented as databaseName:identifier(methodName), separated by "|". As the identification methods are taken from the PSI-MI ontology, the database name is 'psi-mi'. Participant detection method is recommended by MIMIx so it is recommended to always give this information. <em>Ex: psi-mi:"MI:0102"(sequence tag identification)</em></li>
<li><strong>Participant identification method for interactor B</strong>.</li>
</ol>
<p>Empty columns should be represented with '-' to keep track of the columns.</p>
<h2 id="syntax">Syntax</h2>
<p>Columns are normally formed by fields delimited by "|", with a structure like this one:</p>
<pre><code><XREF>:<VALUE>(<DESCRIPTION>)
</code></pre><p>Due to the unsafe use of reserved characters in the values, we have recently added the possibility to surround <code><XREF></code>, <code><VALUE></code> or <code><DESCRIPTION></code> with quotes if they contain a special symbol.</p>
<p>In MI-TAB, the reserved characters are:</p>
<pre><code>|
(
)
:
\t (tabulation)
</code></pre><p>Whenever this happen in your data, surround the value with double quotes:</p>
<pre><code>"<XREF_WITH_RESERVED_CHARS>":"<VALUE_WITH_RESERVED_CHARS>"("<DESCRIPTION>")
</code></pre><p>Note that the quotes are before and after each part. The escaped data should look like in the following examples:</p>
<pre><code>psi-mi:"MI:0000"(a cv term)
psi-mi:"MI:0000"("I can now use braces ()()() or pipes ||| here and ::colons::")
</code></pre><p>If you want to use a quote within a quote, escape it:</p>
<pre><code>uniprotkb:P12345("a \"nice\" protein")
</code></pre>
</section>
</div>
<div class="search-results">
<div class="has-results">
<h1 class="search-results-title"><span class='search-results-count'></span> results matching "<span class='search-query'></span>"</h1>
<ul class="search-results-list"></ul>
</div>
<div class="no-results">
<h1 class="search-results-title">No results matching "<span class='search-query'></span>"</h1>
</div>
</div>
</div>
</div>
</div>
</div>
<a href="MITAB26Format.html" class="navigation navigation-prev " aria-label="Previous page: MITAB 2.6">
<i class="fa fa-angle-left"></i>
</a>
<a href="MITAB28Format.html" class="navigation navigation-next " aria-label="Next page: MITAB 2.8">
<i class="fa fa-angle-right"></i>
</a>
</div>
<script>
var gitbook = gitbook || [];
gitbook.push(function() {
gitbook.page.hasChanged({"page":{"title":"MITAB 2.7","level":"1.4.1.3","depth":3,"next":{"title":"MITAB 2.8","level":"1.4.1.4","depth":3,"path":"MITAB28Format.md","ref":"MITAB28Format.md","articles":[]},"previous":{"title":"MITAB 2.6","level":"1.4.1.2","depth":3,"path":"MITAB26Format.md","ref":"MITAB26Format.md","articles":[]},"dir":"ltr"},"config":{"gitbook":"3.1.1","theme":"default","variables":{},"plugins":[],"pluginsConfig":{"highlight":{},"search":{},"lunr":{"maxIndexSize":1000000},"sharing":{"facebook":true,"twitter":true,"google":false,"weibo":false,"instapaper":false,"vk":false,"all":["facebook","google","twitter","weibo","instapaper"]},"fontsettings":{"theme":"white","family":"sans","size":2},"theme-default":{"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"showLevel":false}},"structure":{"langs":"LANGS.md","readme":"README.md","glossary":"GLOSSARY.md","summary":"SUMMARY.md"},"pdf":{"pageNumbers":true,"fontSize":12,"fontFamily":"Arial","paperSize":"a4","chapterMark":"pagebreak","pageBreaksBefore":"/","margin":{"right":62,"left":62,"top":56,"bottom":56}},"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"}},"file":{"path":"MITAB27Format.md","mtime":"2022-02-09T13:58:44.500Z","type":"markdown"},"gitbook":{"version":"3.1.1","time":"2022-02-09T15:46:01.286Z"},"basePath":".","book":{"language":""}});
});
</script>
</div>
<script src="gitbook/gitbook.js"></script>
<script src="gitbook/theme.js"></script>
<script src="gitbook/gitbook-plugin-search/search-engine.js"></script>
<script src="gitbook/gitbook-plugin-search/search.js"></script>
<script src="gitbook/gitbook-plugin-lunr/lunr.min.js"></script>
<script src="gitbook/gitbook-plugin-lunr/search-lunr.js"></script>
<script src="gitbook/gitbook-plugin-sharing/buttons.js"></script>
<script src="gitbook/gitbook-plugin-fontsettings/fontsettings.js"></script>
</body>
</html>