-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathDataEnricher.html
1021 lines (535 loc) · 34 KB
/
DataEnricher.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
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE HTML>
<html lang="" >
<head>
<title>Data Enricher · 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="Faq.html" />
<link rel="prev" href="DataDistributionBestPractices.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 " 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>
<li class="chapter " data-level="1.4.1.5" data-path="FeatureTABFormat.html">
<a href="FeatureTABFormat.html">
FeatureTAB
</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 active" 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="." >Data Enricher</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">
<h2 id="purpose">Purpose</h2>
<p>One of the aim of this guideline is to provide the community with a tool that could help adding useful information to an existing MITAB 2.7 dataset (but because MITAB 2.7 is backward compatible with MITAB 2.5 and 2.6, the enricher can be used in MITAB 2.5 and 2.6 but will add less information than in MITAB 2.7). A tool, (referred later on as “Enricher”) could consume MITAB data, add extra information about molecules, controlled vocabularies, publication and return enriched MITAB content which follows the <a href="DataDistributionBestPractices.html">Data best practices</a>. Below are a few data items that could be enriched automatically:</p>
<ul>
<li>molecule identifiers, aliases, xrefs and checksum</li>
<li>Controlled vocabulary terms could have their names added provided an ontology identifier is present, eg:<ul>
<li>interaction detection method (column #7),</li>
<li>interaction type (column #12),</li>
<li>source database (column #13);</li>
<li>complex expansion (column #16);</li>
<li>biological roles (columns #17 and #18),</li>
<li>experimental roles (columns #19 and #20),</li>
<li>interactor types (columns #21 and #22),</li>
<li>participant identification methods (columns #41 and #42)</li>
</ul>
</li>
<li>publication information such as author name (column #8) could be added provided there is a publication identifier (i.e. PMID);</li>
<li>organism name (columns #10 & 11) could be added if a taxid is provided.</li>
</ul>
<h2 id="data-enricher">Data Enricher</h2>
<p>The Enricher could use the following resources to retrieve data:</p>
<ul>
<li><a href="https://www.ebi.ac.uk/ols4/" target="_blank">Ontology Lookup Service</a> (aka. OLS) to access the psi-mi ontology;</li>
<li><a href="http://www.ebi.ac.uk/citexplore/" target="_blank">CiteExplore</a> to access publication details;</li>
<li><a href="http://www.uniprot.org/" target="_blank">UniProtKB</a> to access protein information, the sequence information could then be used to compute ROGID and CROGID;</li>
<li><a href="http://www.uniprot.org/taxonomy/" target="_blank">UniProt Taxonomy</a> to access species information;</li>
<li><a href="http://www.ebi.ac.uk/Tools/picr/" target="_blank">PICR</a> to perform computational mapping of protein identifier;</li>
<li><a href="http://www.ebi.ac.uk/chebi/" target="_blank">ChEBI</a> to access small molecule information,</li>
</ul>
<h3 id="molecule-enrichment">Molecule enrichment</h3>
<p>The Data enricher would use the identifiers in columns 1 and 2 (unique identifier) to collect information in PICR, UniProtKB and ChEBI. Here is a recommendation for various molecule types:</p>
<h4 id="1-proteins">1. Proteins</h4>
<p>For higher organisms, the curator may have several isoforms of a protein to select from. In most cases, the experimental evidence will not be sufficient to make an unambiguous mapping. In such a case, most protein interaction databases will make a mapping to the canonical UniProtKB sequence e.g. P51123 to indicate that the interaction could be with some or all of the potential isoforms. Where a mapping to a specific isoform e.g. P51123-3 can be made, it will be. Gene-centric databases will map to the gene identifier in all cases. Whenever the curator has chosen a specific splice variant, its identifier should appear under the unique identifier column. Some examples of annotated proteins:</p>
<table>
<thead>
<tr>
<th style="text-align:left"></th>
<th style="text-align:left"></th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left">ensembl:ENSG00000136869</td>
<td style="text-align:left">innatedb:IDBG-82738</td>
</tr>
<tr>
<td style="text-align:left">uniprotkb:O00206</td>
<td style="text-align:left">uniprotkb:TLR4_HUMAN</td>
</tr>
<tr>
<td style="text-align:left">refseq:NM_138554</td>
<td style="text-align:left">refseq:NP_612564</td>
</tr>
<tr>
<td style="text-align:left">refseq:NR_024169</td>
<td style="text-align:left">refseq:NR_024168</td>
</tr>
</tbody>
</table>
<p><strong>How to pick the canonical sequence for a given protein ?</strong></p>
<p>The sequence defined at the top level of a UniProtKB entry is considered a canonical sequence i.e. P51123. All isoforms linked to this entries (having their own potential sequence variation) would link to this top level sequence which is the canonical sequence for the entry (note, it will be an exact match to one of the isoforms). For example: should your molecule be P51123-3, the canonical sequence would be P51123.
Should the protein be described using a gene identifier (as seen in a minority of PSICQUIC services), it is recommended to map this identifier to the corresponding UniProt/Swiss-Prot canonical sequence, given a specific species, there should be only one corresponding UniProt/Swiss-Prot entry. If the entry is only in UniProtKB/TrEMBL, selecting the longest ORF for that gene is the conventional method for performing a 1:1 mapping.</p>
<p><strong>How to map UniProtKB proteins to RefSeq ?</strong></p>
<p>Some proteins may have related isoforms resulting from different splice isoforms of the mRNA or from alternative promoter usage. UniProtKB does give different identifiers to these entities and it is possible to map them to RefSeq by using the <a href="http://www.ebi.ac.uk/Tools/picr" target="_blank">PICR Identifier mapping</a> service. In case of isoforms, PICR would be able to map it to the corresponding RefSeq identifier.</p>
<p><strong>How would it work in practice ?</strong></p>
<p>For proteins, the Data Enricher can:</p>
<ul>
<li>remap identifiers from any databases listed in <a href="http://www.ebi.ac.uk/Tools/picr/" target="_blank">PICR</a> to a single UniProtKB identifier when possible. For that, it is important to give unambiguous identifiers in columns 1 and 2 and to give the organism of the protein in columns 10 and 11. The organism is very important to be able to remap to a single uniprot accession. The Data Enricher will always remap to the master uniprot entry (canonical sequence) even if an identifier can match a single uniprot splice variant identifier. When the remapping is successful, the Enricher will not delete the original identifier but just move it to 'alternative identifiers' in columns 3 and 4 and add the remapped uniprot accession in columns 1 and 2 for 'unique identifier'. In several cases, the remapping is too ambiguous and the enricher would not enrich the line but just log a warning:<ul>
<li>Several Swissprot entries can match</li>
<li>Several Trembl entries can match and have the same sequence length (but different sequences)</li>
<li>Identifier cannot be remapped to a UniProtKb accession</li>
</ul>
</li>
<li>add Refseq identifiers using PICR. The Data Enricher will add all the possible Refseq identifiers in the columns 3 and 4 'Alternatice identifiers'.</li>
<li>enrich several columns :<ul>
<li>In columns 5 and 6 for aliases, it will add gene name, gene synonym, protein recommended name, ORF and locus name. It will follow the Data best practices and add display_short and display_long aliases.</li>
<li>In columns 3 and 4 for alternative identifiers, it will add uniprotKb secondary accession when not ambiguous</li>
<li>In columns 23 and 24 for Interactor xrefs, it could add GO and interpro xrefs...</li>
<li>In columns 33 and 34 for Interactor checksums, it would add rogid and crogid</li>
</ul>
</li>
</ul>
<table>
<thead>
<tr>
<th style="text-align:left"><strong>Protein accession</strong></th>
<th style="text-align:left"><strong>ROGID</strong></th>
<th style="text-align:left"><strong>CROGID</strong></th>
<th style="text-align:left"><strong>RefSeq</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left"><code>P51123</code></td>
<td style="text-align:left"><code>rogid:DxUDrj8iljY131pQOBswejQxoxI7227</code></td>
<td style="text-align:left"><code>rogid:DxUDrj8iljY131pQOBswejQxoxI7227</code></td>
<td style="text-align:left"><code>NP_996160</code></td>
</tr>
<tr>
<td style="text-align:left"><code>P51123-2</code></td>
<td style="text-align:left"><code>rogid:nqWqHc3mUUZtYVGzCr3UZq60DRU7227</code></td>
<td style="text-align:left"><code>rogid:DxUDrj8iljY131pQOBswejQxoxI7227</code></td>
<td style="text-align:left"><code>NP_476956</code></td>
</tr>
</tbody>
</table>
<p><br></p>
<table>
<thead>
<tr>
<th style="text-align:left">What information</th>
<th style="text-align:left">Target Column</th>
<th style="text-align:left">Data source</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left">gene name, gene name synonym, orf, locus name, recommended name, display_short and display_long</td>
<td style="text-align:left">5 & 6</td>
<td style="text-align:left">UniProtKB</td>
</tr>
<tr>
<td style="text-align:left">Additional database cross references (e.g. primary database identifier such as RefSeq or UniProt), uniprot secondary AC</td>
<td style="text-align:left">3 & 4</td>
<td style="text-align:left">UniProtKB, PICR</td>
</tr>
<tr>
<td style="text-align:left">Organism name (only if no conflicts with uniprot entry)</td>
<td style="text-align:left">10 & 11</td>
<td style="text-align:left">UniProt Taxonomy</td>
</tr>
<tr>
<td style="text-align:left">Model organism database (Flybase, TAIR, SGD...), GO, interpro,...</td>
<td style="text-align:left">23 & 24</td>
<td style="text-align:left">UniProtKB</td>
</tr>
<tr>
<td style="text-align:left">ROGID, CROGID</td>
<td style="text-align:left">33 & 34</td>
<td style="text-align:left">UniProtKB</td>
</tr>
</tbody>
</table>
<h4 id="2-small-molecules">2. Small Molecules</h4>
<p>Should the Standard InCHI Key not describe unambiguously a molecule, the data provider should use an other cross reference and keep the Standard InCHI Key as an alternative identifier.</p>
<h5 id="enrichment-process">Enrichment Process</h5>
<p>For small molecules, the Data Enricher can :</p>
<ul>
<li>remap identifiers from any databases cross referenced by ChEBI (some Drugbank identifiers, Pubchem, etc.) to a single ChEBI identifier when possible. For that, it is important to give unambiguous identifiers or standard Inchi keys in columns 1 and 2 and to give the organism of the small molecule in columns 10 and 11 when relevant. The organism could help to remap to a single ChEBI identifier. When giving the standard inchi key in column 1 and 2 or 3 and 4, it should be represented as 'unknown:xxxxx(standard inchi key)'. The Data Enricher will remap to manually curated compounds when it is possible. When the remapping is successful, the Enricher will not delete the original identifier but just move it to 'alternative identifiers' in columns 3 and 4 and add the remapped ChEBI accession in columns 1 and 2 for 'unique identifier'. If the original identifier is a standard inchi key, it will move it to the checksum columns 33 and 34. In several cases, the remapping is too ambiguous and the enricher would not enrich the line but just log a warning:<ul>
<li>Several compounds can match</li>
<li>Identifier cannot be found in ChEBI</li>
</ul>
</li>
<li>enrich several columns :<ul>
<li>In columns 5 and 6 for aliases, it will add ChEBI name, standard inchi. It will follow the Data best practices and add display_short and display_long aliases.</li>
<li>In columns 3 and 4 for alternative identifiers, it will add ChEBI secondary accessions when not ambiguous</li>
<li>In columns 23 and 24 for Interactor xrefs, it could add PubChem or other xrefs (To be defined)...</li>
<li>In columns 33 and 34 for Interactor checksums, it would add standard inchi key and maybe smiles as well.
The enrichment process here would rely on the existence of a !ChEBI identifier in the unique identifier column. If the given identifier is unambiguously identifying a single small molecule and the taxids match, the enrichment below can take place.</li>
</ul>
</li>
</ul>
<table>
<thead>
<tr>
<th style="text-align:left">What information</th>
<th style="text-align:left">Target Column</th>
<th style="text-align:left">Data source</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left">standard inchi, ChEBI name, display_sort and display_long</td>
<td style="text-align:left">5 & 6</td>
<td style="text-align:left">ChEBI</td>
</tr>
<tr>
<td style="text-align:left">ChEBI secondary acs and Standard InChI</td>
<td style="text-align:left">3 & 4</td>
<td style="text-align:left">ChEBI</td>
</tr>
<tr>
<td style="text-align:left">Organism name (only if no conflicts with ChEBI entry)</td>
<td style="text-align:left">10 & 11</td>
<td style="text-align:left">ChEBI and uniprot taxonomy</td>
</tr>
<tr>
<td style="text-align:left">other xrefs which could be useful (to be defined)</td>
<td style="text-align:left">23 & 24</td>
<td style="text-align:left">ChEBI</td>
</tr>
<tr>
<td style="text-align:left">standard inchi key, smile</td>
<td style="text-align:left">33 & 34</td>
<td style="text-align:left">ChEBI</td>
</tr>
</tbody>
</table>
<h4 id="3-nucleic-acids-and-genes">3. Nucleic Acids and genes</h4>
<p>It was agreed during the PSI meeting 2012 that the Data Enricher will not enrich genes and nucleic acids. It will be up to the data provider to follow the data best practices and provide:</p>
<ul>
<li>unique embl/ddbj/genbank identifier for small nucleic acids in columns 1 and 2. It is recommended to move the other identifiers to alternative identifiers and Interactor xrefs.</li>
<li>unique ensembl genome, ensembl or gene id/locus link identifier for genes in columns 1 and 2. It is recommended to move the other identifiers to alternative identifiers and Interactor xrefs.</li>
<li>gene names should be provided for genes in aliases columns as well as display_short and display_long.</li>
<li>organisms will be enriched using uniprot taxonomy but it will not check if there is a conflict with the identifiers</li>
</ul>
<h3 id="organism-enrichment">Organism enrichment</h3>
<p>To be able to enrich the organism, it is important to give the taxid of the organism represented as 'taxid:taxon(text)'.</p>
<p>In case of proteins and small molecules, the organism enrichment will depend on the consistency between organism and the molecule identifiers.</p>
<h5 id="enrichment-process">Enrichment Process</h5>
<p>For organisms (interactor organisms in columns 10 and 11 and host organism in column 29), the Data Enricher can:</p>
<ul>
<li>add the missing organism for proteins and small molecules (and genes as well?) when possible (columns 10 and 11 only)</li>
<li>add the common name and scientific name as defined in the data best practices (columns 10, 11 and 29)</li>
</ul>
<h3 id="publication-enrichment">Publication enrichment</h3>
<p>To be able to enrich the publication, a pubmed id (or IMEx id) is necessary in column 9 (identifier of the publication).</p>
<h5 id="enrichment-process">Enrichment Process</h5>
<p>For publications, the Data Enricher can:</p>
<ul>
<li>For each pubmed id, it will add the first author name and publication date as defined in the data best practices</li>
</ul>
<h3 id="controlled-vocabulary-enrichment">Controlled vocabulary enrichment</h3>
<p>The Data Enricher will only enrich psi-mi ontology terms in columns 7, 13, 12, 16, 17, 18, 19, 20, 21, 22, 41 and 42 (cross references to psi-mi terms should be represented with 'psi-mi:"MI:xxxx"(term name)').</p>
<p>The Enricher will only add the term name in parenthesis if it is missing or not exact.</p>
<p>For other ontology terms such as GO that could be present in columns 23,24 and 25 (interactor and interaction xrefs), the enricher could also add the name in parenthesis.</p>
</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="DataDistributionBestPractices.html" class="navigation navigation-prev " aria-label="Previous page: Data Distribution Best Practices">
<i class="fa fa-angle-left"></i>
</a>
<a href="Faq.html" class="navigation navigation-next " aria-label="Next page: FAQ">
<i class="fa fa-angle-right"></i>
</a>
</div>
<script>
var gitbook = gitbook || [];
gitbook.push(function() {
gitbook.page.hasChanged({"page":{"title":"Data Enricher","level":"2.1.4","depth":2,"next":{"title":"FAQ","level":"2.1.5","depth":2,"path":"Faq.md","ref":"Faq.md","articles":[]},"previous":{"title":"Data Distribution Best Practices","level":"2.1.3","depth":2,"path":"DataDistributionBestPractices.md","ref":"DataDistributionBestPractices.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":{"pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css","website":"styles/website.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":{"pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css","website":"styles/website.css"}},"file":{"path":"DataEnricher.md","mtime":"2024-10-28T11:47:30.501Z","type":"markdown"},"gitbook":{"version":"3.1.1","time":"2025-01-21T16:19:00.566Z"},"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>