2009
DOI: 10.5808/gi.2009.7.4.208
|View full text |Cite
|
Sign up to set email alerts
|

IdMapper: A Java Application for ID Mapping across Multiple Cross-referencing Providers

Abstract: We developed an identifier mapping application for bioinformatics research in Java programming language. It is easy to use and provides many usability functionalities that are expected as essentials for a professional application. It supports three widely used mapping services and can convert many ids from one source database into many target databases at once. Id mapping across service providers is possible by remapping the resultant ids. Because it adheres to the NetBeans platform architecture, it can be inc… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2015
2015
2015
2015

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(1 citation statement)
references
References 13 publications
0
1
0
Order By: Relevance
“…These warehouses often materialize relationships among objects represented using such IDs, which are either gathered from other databases or computed using ID mapping tools such as DAVID [3], OntoTranslate [4], Synergizer [5], GeneID Converter [6], IdBean [7], IDMapper [8], g:Profiler [9] and MatchMiner [10]. The materialized views must then be maintained by monitoring possible ID changes, migration, and relationship changes among the objects, occurring in databases they do not control, or risk producing inconsistent and obsolete results, perhaps even facing loss of functionality [11].…”
Section: Introductionmentioning
confidence: 99%
“…These warehouses often materialize relationships among objects represented using such IDs, which are either gathered from other databases or computed using ID mapping tools such as DAVID [3], OntoTranslate [4], Synergizer [5], GeneID Converter [6], IdBean [7], IDMapper [8], g:Profiler [9] and MatchMiner [10]. The materialized views must then be maintained by monitoring possible ID changes, migration, and relationship changes among the objects, occurring in databases they do not control, or risk producing inconsistent and obsolete results, perhaps even facing loss of functionality [11].…”
Section: Introductionmentioning
confidence: 99%