Changeset 3833
- Timestamp:
- Oct 15, 2007, 9:36:21 AM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/development/ideas.html
r2055 r3833 29 29 list are just ideas. It is not yet decided, if, when and by whom 30 30 any of these items are going to be implemented. Also note that the items 31 are not ordered in a particular way. The only exception is that ontology 32 support and MAGE ML seems to be a major issue and it is likely that 33 this will happen before anything else. 31 are not ordered in a particular way. 34 32 </p> 35 33 … … 74 72 75 73 76 <dt>MEV connection </dt>74 <dt>MEV connection (DONE)</dt> 77 75 <dd> 78 76 Access BASE from MEV. Requires a remote API. … … 84 82 </dd> 85 83 86 <dt>Affymetrix/one-channel plugins </dt>84 <dt>Affymetrix/one-channel plugins (DONE)</dt> 87 85 <dd> 88 86 To be able to analyse affymetrix data, a new set of plugins are needed, … … 102 100 </dd> 103 101 104 <dt>Protocol parameters </dt>102 <dt>Protocol parameters (DONE)</dt> 105 103 <dd> 106 104 Protocols may have parameters, ie. variations in the compounds and quantities used. … … 110 108 </dd> 111 109 112 <dt>Sanity check tool </dt>110 <dt>Sanity check tool (DONE)</dt> 113 111 <dd> 114 112 The core is very loose when it comes to checking the structure of linked items. … … 119 117 120 118 121 <dt>Platform item </dt>119 <dt>Platform item (DONE)</dt> 122 120 <dd> 123 121 Introduce a <code>Platform</code> item in the database. It should be use for
Note: See TracChangeset
for help on using the changeset viewer.