Frequently Asked Questions: MIP Workflow – MetaData Upload

The metadata has been run through MetaMan successfully, is named correctly, and is in the correct folder on the submittal drive (see first screen shot), and the submittal has otherwise passed Validate Content for Jasper Co, IA (Case number 06-07-B080S). However, this is stuck at Store Content with an error message.

Your metadata file is failing to ingest into Content Manager because at least one of the data values in a metadata entity is not valid for the fields in the database. Please submit a ticket to MIPHELP

Note: Failing to ingest metadata into Content Manager only happens at the Store Content tasks. If the metadata was validated with MetaMan, the user should never receive this type of error;

When you upload your draft DFIRM database deliverable submissions at the Develop DFIRM Database task, the data/metadata submission is automatically sent to FAFS for the independent QA/QC. The passing notification from FAFS QA/QC is not required until the associated Validate Content Submission task.

Additionally, at the Validate Content Submission task, the metadata file must be in .xml format for it to be recognized by the MIP. Use MetaMan to validate and convert the metadata file. Since the screen does not currently have a Load Data Artifacts portlet (this will change in a future Service Pack), you can either copy the .xml metadata file to the correct folder via Citrix's Windows Explorer (if you have write permissions to the folder) or send the metadata file to MIPHELP and let us know to where you need the file copied.

Note: Please ensure the xml file does not contain any embedded comments.

Return to FAQ Page