Search results

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

• Data Jamboree 2/Notes
  * ability to prune species with no data (values) for export * Summarizing data per publication
  19 KB (2,935 words) - 15:05, 14 October 2008
• Data Jamboree 2/Annotation Experiment
  ...to five curators on the third day of the [[Data_Jamboree_2/Agenda | second data jamboree]]. The goals of the experiment were to assess curation consistency Only one of the five curators had experience using Phenex prior to the data roundup. Training for all curators consisted of:
  7 KB (996 words) - 14:46, 8 October 2008
• Phenoscape web UI planning
  * Could use OLS, but makes more sense to retrieve exact data we're working off of in the database ...summary counts be returned in? These are then used to navigate to further data services.
  2 KB (301 words) - 03:11, 23 October 2008
• Roadmap for first iteration
  * '''[Ongoing]''' Investigate and begin documenting additional data service needs required by interface * '''[Ongoing]''' Document data retrieval web service specifications
  5 KB (764 words) - 19:27, 11 October 2011
• Front end user interface tools
  ...e still under development, Phenex is ready for use and enables our ongoing data curation activities. ===Data services built on OBD===
  2 KB (256 words) - 23:48, 10 January 2009
• Phenoscape web UI
  ** Mockup interface using dummy data within web application - request group feedback ** Possible live demo depending on data service performance progress
  6 KB (783 words) - 22:51, 9 January 2014
• Database Roadmap
  * Implement improved query methods to speed up execution of anatomy data services * Automate data loader module
  2 KB (274 words) - 19:25, 11 October 2011
• OBD API Documentation
  ...inally reasons with (as in infers implicit knowledge from) the downloaded data. ==OBD Data Model Entities==
  11 KB (1,531 words) - 16:06, 8 January 2009
• Problem Log Format
  ...is an excerpt from such a Problem Log created during the execution of the Data Loader. The problematic, incomplete records are grouped under the name of t
  3 KB (365 words) - 23:59, 10 January 2009
• Web UI mockups
  Mockup drawings created at the Phenoscape Data Roundup in September 2008. These are intended to stimulate discussion and [[Category:Data Jamboree 2]]
  1 KB (185 words) - 19:58, 19 January 2010
• 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

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