headerof the generated PRIDE XML file is not totally achieved (contact info, experiment & sample details, protocol steps, etc.). The user will have to use PRIDE Converter to build another PRIDE XML file, from which he will only copy the meta-infos and paste them into the hEIDI generated PRIDE XML file.
headerfrom the second PRIDE XML file and paste it into the first PRIDE XML file (see below)
runDescriptor.propertiesfile exists in your hEIDI project (see next section)
MS Identifications > Context > Export > PRIDE XML
Noto stop the PRIDE XML Export process (Ask the INFO Team to populate the MSIdb with missing spectra)
runDescriptor.properties file you provide meta information about your experiment (title, description, contact info), your sample(s), the instrument, the protocol steps, etc.
The PRIDE XML Export fonctionnality will then parse properties from the
runDescriptor.properties file and create the appropriate header in the resulting XML file.
runDescriptor.propertiesfile, click here for more details about filling in this file)
When you create a new hEIDI project, a default
runDescriptor.properties file is created.
If you use an old hEIDI project (created with hEIDI version lower than v1.10.1), check:
runDescriptor.propertiesfile exists under
<HEIDI_PROJECT_DIR>\heidi.project\. If it doesn't exist, simply create an empty text file, named
Filestab (or select in the main menu bar
runDescriptor.propertiesfile to open it in the hEIDI editor view (you can also right-click on the
Open, it will display the contents of this file in a tabular way)
File→Savein the main menu bar
See here to create a PRIDE XML file from a MASCOT DAT file.
The purpose is to replace meta-information from the first PRIDE XML file (generated by hEIDI) with the more detailled meta-information of the second PRIDE XML file (generated by PRIDE Converter)