Additional file 1: Table S1. of Comparison, alignment, and synchronization of cell line information between CLO and EFO

EFO cell lines drawn from external sources. In the initial step of the EFO-CLO comparison and alignment process, there are 428 and 20 EFO cell lines which were imported from Cell Line Ontology and 20 in BRENDA Tissue and Enzyme Source Ontology respectively. These 448 EFO cell lines were excluded from the entire mapping process. File is stored in Microsoft Excel spreadsheet (xlsx) format. (XLSX 47 kb

Additional file 2: Table S2. of Comparison, alignment, and synchronization of cell line information between CLO and EFO

Final EFO-CLO alignment result. The 874 EFO-CLO mapped cell lines aligned and merged into CLO (Tab. 1 in the excel file) and 344 EFO unique immortalized permanent cell lines added to CLO (Tab. 2 in the excel file). File is stored in Microsoft Excel spreadsheet (xlsx) format. (XLSX 54 kb

Additional file 1 of Developing a web-based SKOS editor

Tutorial. (DOCX 2109 KB

Additional file 2: of Linking rare and common disease: mapping clinical disease-phenotypes to ontologies in therapeutic target validation

The list of journals mined for disease-phenotype assocations. (PDF 13 kb

Additional file 1: of Linking rare and common disease: mapping clinical disease-phenotypes to ontologies in therapeutic target validation

URLs to the supplementary downloadable result files for text mining results (IBD, Autoimmunity, Skeletal disorders, and Metabolism disorders). (PDF 18 kb

Eagle-i record-level citation widget.

<p>Eagle-i record-level citation widget.</p

Contributions and roles related to content as they correspond to identifier creation versus identifier reuse.

<p>The decision about whether to create a new identifier or reuse an existing one depends on the role you play in the creation, editing, and republishing of content; for certain roles (and when several roles apply) that decision is a judgement call. Asterisks convey cases in which the best course of action is often to correct/improve the original record in collaboration with the original source; the guidance about identifier creation versus reuse is meant to apply only when such collaboration is not practicable (and an alternate record is created). It is common that a given actor may have multiple roles along this spectrum; for instance, a given record in monarchinitiative.org may reflect a combination of (a) corrections Monarch staff made in collaboration with the original data source, (b) post-ingest curation by Monarch staff, (c) expanded content integrated from multiple sources.</p

A summary of the 10 recommendations and their direct or indirect impact on different kinds of identifier roles.

<p>A summary of the 10 recommendations and their direct or indirect impact on different kinds of identifier roles.</p

Anatomy of a web-based identifier.

<p>An example of an exemplary unique resource identifier (URI) is below; it is comprised of American Standard Code for Information Interchange (ASCII) characters and follows a pattern that starts with a fixed set of characters (URI pattern). That URI pattern is followed by a local identifier (local ID)—an identifier which, by itself, is only guaranteed to be locally unique within the database or source. A local ID is sometimes referred to as an “accession.” Note this figure illustrates the simplest representation; nuances regarding versioning are covered in Lesson 6 and <a href="http://www.plosbiology.org/article/info:doi/10.1371/journal.pbio.2001414#pbio.2001414.g005" target="_blank">Fig 5</a>.</p

Desirable characteristics for database identifiers in the life sciences.

<p>Desirable characteristics for database identifiers in the life sciences.</p