Search results

Create the page "Data" on this wiki! See also the search results found.

• Queries and Query Execution Plans
  ...s the queries that have been (or are to be) implemented for the Phenoscape data services, in addition to the execution details of each queries on the Postg ...onal, but their execution was very slow in terms of time. As a result, the data retrieval strategy used in the SICB prototype is being examined for bottlen
  3 KB (429 words) - 20:30, 21 January 2009
• Logic and Reasoning Challenges
  ...a, adding top-down inferencing may cause widespread inconsistencies in the data if unchecked. ...between taxa and phenotypes, would cause incorrect inferencing and loss of data integrity. The easiest way to address this issue is to use different relati
  18 KB (2,610 words) - 17:18, 22 February 2010
• Phenoscape data loader
  ...ation server at NESCent and can be found at /usr/local/projects/phenoscape-data-loader ==The Phenoscape data loader - A step by step review==
  3 KB (515 words) - 16:05, 29 October 2009
• Data Services
  {{StatusBox|This page documents data services for version 1 of the Phenoscape KB, available as a legacy resource This page details the data services that query the Phenoscape OBD database and transfer the retrieved
  46 KB (4,930 words) - 19:11, 29 June 2016
• Queries
  ...ection describes the queries that have been implemented for the Phenoscape data services, in addition to the execution details of each queries on the Postg ...d and an execution plan is drawn up by the PostgreSQL DBMS to retrieve the data as efficiently as possible in terms of time and memory utilization. In the
  3 KB (409 words) - 18:07, 21 August 2009
• ORB term request prototype
  The vision of this project is to develop an application that will allow data curators to use new ontology terms without creating a workflow bottleneck. ...provenance and community discussion, enable temporary terms to be used in data annotation, and update temporary terms once a request has been resolved.
  30 KB (4,747 words) - 13:13, 3 October 2010
• Queries for Phenoscape UI demo'ed at SICB, Boston in Jan 2009
  This page documents the queries implemented to retrieve data for the Anatomy Web Services module of the Phenoscape project, which was de ...eries Q2 and Q3 are avoided. Coupled with connection, query execution, and data transfer times, this leads to significant time savings.
  3 KB (531 words) - 20:12, 28 January 2009
• Synchronization Tool
  ====Conflicting Data====
  3 KB (526 words) - 22:05, 23 January 2009
• OBD Java API
  This page contains documentation of the data services module of the Phenoscape project, and supplements the [[http://www
  274 bytes (41 words) - 23:20, 31 July 2009
• OpenURL
  ...adata about publications, however to describe access requests, it contains data for:
  2 KB (385 words) - 23:39, 18 February 2009
• Neglected items
  ...gy (such as "millimeters"). These values are not imported into OBD by the data loader. Data matrices sometimes use the NEXUS format for specifying polymorphic states.
  3 KB (488 words) - 13:37, 30 April 2009
• Query strategy performance
  ...e the execution times. This page discusses the requirements of the various data access modules of the Phenoscape application to be demonstrated at the ASIH = Phenotype data summaries and details services =
  28 KB (4,482 words) - 16:37, 24 April 2009
• Creating Tree Files
  ...tml Mesquite]. You might begin with an existing nexus file containing the data matrix for the publication, or create a new nexus file containing a list of # Open the nexus file in Mesquite. You should see the data matrix with the taxon list in the left-hand column.
  2 KB (316 words) - 21:19, 26 November 2012
• Current queries
  This page documents the queries implemented to retrieve data for the Anatomy Web Services module of the Phenoscape project, which was de ...the client side, which is a very expensive process in terms of time. Some data structures like lookup tables for Attributes and Values have been implement
  4 KB (540 words) - 19:52, 20 January 2009
• Query execution speed-up: The investigation
  ...ractShard and the OBDSQLShard contain method definitions that can retrieve data from the repositories by executing SQL or more XML based query formats. For The Phenoscape data is stored in a database that is managed through the PostgreSQL RDBMS (Versi
  2 KB (375 words) - 15:02, 21 August 2009
• SummerTraining2009
  ...ata. Opportunities are available to work as part of the Phenoscape team on data curation or open source software/database development. Participants would
  2 KB (323 words) - 02:51, 2 February 2009
• Student Instructions
  ...sed in a shared [http://www.dropbox.com DropBox] folder (named 'Phenoscape-data'). Please contact Wasila or Paula for access. <nowiki>https://webdav.nescent.org/phenoscape-data</nowiki>
  2 KB (253 words) - 20:06, 29 November 2012
• Entities with taxonomic context
  ...effect on data curators - the interface would be the same in Phenex. The data would be modeled in this way on its way into OBD. So, there would be no ne
  4 KB (552 words) - 14:26, 30 March 2009
• Phenoscape data repository
  ...ma of this data repository and outlines the methods to load and query this data repository. == Data Repository ==
  18 KB (2,662 words) - 21:46, 14 December 2009
• ASIH09 workshop
  ...es of how these ontologies are being used to provide new ways of exploring data within morphological and phenotypic databases. Talks in the morning will be As biology has become increasingly data-rich, the reliance on databases and
  14 KB (1,979 words) - 14:02, 13 August 2009

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)