Share

MIAMExpress

File Release Notes and Changelog

Release Name: MIAMExpress1.01

Notes:
Full version of MIAMExpress.

Changes: Main new features are new in R1.01: ----------------------------------- 1- Sample treatment protocol is a standard protocol that could be referenced once it has been created. 2- Growth condition protocol is a standard protocol that could be referenced once it has been created. 3- Feature mapping for GenePix data files for submissions which are based on ADF submitted array designs. 4- Pooling functionality; one can create an extract pooled from multiple sample. Other Changes and Bug Fix: -------------------------- 1- Unlike the previous version it generates email to the mailing list when a submitter sends a new array design. 2- The array design MAGE-ML creation program to write down the MAGE-ML file in the specified directory. 3- MAGE-ML creation program now creates external data files with the same name that submitter has submitted. 4- MAGE-ML creation program which creates MAGE-ML from ADF, now counts identifiers from 1 not 0. 5- Not creating two different compounds identifier for the same compound. 6- Growth condition duration: if submitter doesn't specify the time we shouldn't parse out the time unit. 7- Adding the not applicable to Time point drop down list. 8- Parse out the address in MAGE-ML file as organization's address. 9- Including Reporter Group in ADF parsed mage-ml file. 10-Take the Array design info from TARDESIN table and incorporate their values in the produced MAGE-ML file. 11-Add another OntologyEntry object and associated it as PolymerType in ADF->MAGE-ML creation. 12-MAGExpress doesnt create Database and DatabaseEntry objects when the values are NULL,anymore. 13-Having Submitter Role to the Person Object when ADF-> MAGE-ML. 14-Having Hardware and Software not as parameters of protocols but as hardware and software in MAGE-ML file. 15-US spelling in MAGE-ML file. 16-Include Unapproved CV associated to the "Other" entry in MAGE-ML file, everywhere in MAGExpress. 17-Having another column in ADF; "Fail Type" which we need a OntologyEntry object for that associated with Reporter, according to the MAGE-OM. 18-In the produced mage-ml files get rid of spaces in the file name. (Replace it with UNDERLINE) 19-Fixing upload screens so that it doesn't remove the file on the server, when updating.