Submitter comment about the content of whole submission. this node added by us when we get the package and identify source of package (for our tracking) Organization(s) involved into the submission. One organization is the owner of submission data. If the data are to be deposited in a protected database and not made public under any circumstances, this element should be set to "controlled-access", otherwise to "public" Date are to be deposited to a public database. Date are to be deposited to a protected database. This is set of references to already created object. E.g. - to the projects (bioproject, SRA study, dbgap study etc) , samples , previous submission id, etc, Name in the ccontext of the object in db, Action is what to do - either process new submission (ProcessFile) or change status (ChangeStatus) of the existing one. All action and commands to target archive are contained in this file Adding a group of files to the content of particular target archive in given context File label the use of which is specific to target database. For example, for dbGaP genotype files, it can represent anonymized ids of dbGaP samples Adding a group of data objects, inlined into the submission Data label the use of which is specific to target database. Same as for AddFiles, but this is inlined data. If the action is ChangeStatus, the target is identified by id tag. Immediate release NCBI identifier of the related submission. For corrections of previously submitted (invalid) data and for backward compatibility with existing SRA submission XML. Common attributes for group of metafiles, data files and inline data. Target database for the data, e.g. dbGaP, SRA, GEO, etc... Target database context (if known) for the data, e.g. phs123 for dbGaP study, SRX123 for SRA experiment, etc Internal tracking information. DataType is what we can process: submitter-xml,project-core-xml,biosample-xml,genbank-FF,genbank-seqsubmit, sra-experiment.xml,sra-run.xml, etc full list must be specified in submission database. Branded with the version. XML is autodected by top-level element and XML schema reference This is a data file, the type of which will be determined by destination archive Phenotype table Street address: 123 Main St. Suite 104 City: New York Subdivision of Country(state, province, etc.): New York Country: USA Full middle name or initials Contact information if known Logon name eRA,pda,NIH,ncbi/ftp-private,..... Organization for the submission Full Name Name abbreviation Contact(s) with organization when known Organization type : center, institute(a lab) or consortium. Role of the ogranization in submission - owner of the data or just a participant. It is expected that there is one owner of the submission data. In case we want to exchange organization list Organization URL Db defines the scope of IdTag, which will become local to submission when Db is missing Internal tracking information filled up by submission system and needed for internal use by the archives This is inline data to be embedded into the submission Internal tracking information filled up by submission system and needed for internal use by the archives Either XML or base64/plain text data) XML node - we do not care what is inside- it should be just a well-formed XML Optional name of the data object Data model of the data object Content type - what is it - XML, text, binary, etc How data is encoded (or how to decode it) E.g. - plain or base64 Plain text Base64-encoded binary