Reorganize the API

[reynoldtan]

Tripal API conventions:

• name/combine API functions based on what they return
• names should be of the format [module abbreviation]_[verb]_[subject]
• functions retrieving records should use an $identifiers array as the first parameter to support different select criteria (e.g. name, cvterm_id, term_string for ap_get_cvterm)

Task

For all current API functions with the switch($property) approach, create new functions for each $property following the Tripal API Conventions. Where it makes sense, these new functions could be grouped in a separate file to keep the functions together.

[reynoldtan]

Updated GENUS API:

Test function calls:

// Fetch project genus by project name. $m = ap_get_projectgenus( array('project_name' => 'AGILE: Application of Genomic Innovation in the Lentil Economy') );

dpm($m);

// Fetch project genus by project id. $m = ap_get_projectgenus( array('project_id' => 63) );

dpm($m);

// Set project genus with replace option on. $project_id = 63; // Change to a different project with genus. ap_set_projectgenus( array('project_id' => $project_id, 'genus' => 'Cicer'), array('replace' => TRUE) );

$m = ap_get_projectgenus( array('project_id' => $project_id) );

dpm($m);

[laceysanderson]

Current Review Status

• [x] Project API
• [x] System Variables API
• [x] Genus API
• [x] CV Term API
• [ ] Column Headers API
• [ ] Database API
• [ ] Data File API
• [ ] Unit & Data Type API
• [ ] Materialized Views API
• [ ] Ontology API
• [ ] Tripal Job API
• [ ] Form Fields API
• [ ] Integration of the API throughout the module.

My Approach: review a file at a time since that roughly corresponds to an API above :-)