Difference between revisions of "Data Repository and Data Services"

From phenoscape
(Term info)
(Replacing page with ' Category:Informatics')
 
(73 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Data loader==
 
A data loader application to refresh the data in the Phenoscape database on a daily basis is under development. The application is being developed as a Perl module which:
 
# Downloads curated NeXML files from the Phenoscape SVN repositories
 
# Drops and recreates the database
 
# Loads the requisite ontologies into the database
 
# Loads the data from the curated NeXML files into the database, and
 
# Invokes the OBD reasoner to elicit implicit information from the data and adds them to the database
 
  
==Web services==
 
Each service may support multiple media types.  The desired media type can be specified by appending <code>?media=json</code> or similar to the request URL.
 
===Term info===
 
'''URI'''
 
  
../info/{termID}
+
[[Category:Informatics]]
 
 
'''Returns'''
 
 
 
JSON:
 
<javascript>
 
{
 
    "id" : "TAO:0001700",
 
    "name" : "caudal-fin stay",
 
    "definition" : "Bone that is located anterior to the caudal procurrent rays. Caudal fin stays are unpaired bone."
 
    "parents" :
 
    [
 
        {
 
            "relation" : "OBO_REL:is_a",
 
            "id" : "TAO:0001514",
 
            "name" : "bone"
 
        },
 
        {
 
            "relation" : "OBO_REL:part_of",
 
            "id" : "TAO:0000862",
 
            "name" : "caudal fin skeleton"
 
        }
 
    ],
 
    "children" : [] // if there are children, this content should be in the same format as the parents list
 
}
 
// how should xrefs, etc. be represented, property_value definitions?
 
</javascript>
 
 
 
OWL-RDF:
 
 
 
TBD...
 
 
 
If there is no term with the given ID, the service should return "404 Not Found".
 
 
 
===Autocomplete===
 

Latest revision as of 00:44, 9 January 2009