EDMR XML Load User’s Reference
eDMR XML Load User’s Reference
The XML Load feature in the eDMR web-application provides permitted wastewater facilities with the ability to load DMR test results using an XML file. This allows facilities with existing systems that capture DMR data to extract that data from their existing system and electronically upload it into eDMR. This electronic upload eliminates duplicate entry of DMR data and should minimize data entry synchronization errors between the two systems. An XML file is for a single permitted facility and the corresponding permit number must match the permit number to which the user is logged in. Each XML file can include multiple reporting periods, outfalls, toxicity tests, and daily test results.
The purpose of this document is to explain the process and requirements for facilities using the XML Load feature in eDMR. The primary audiences for this manual are eDMR Test Data Entry users and technical personnel responsible for generating XML files for upload of DMR test results into the eDMR application.
Process
The current process for entering DMR test data into eDMR is:
1. Log into eDMR as a Data Entry User or Data Entry Proxy user.
2. Select the facility for which DMR test data is to be entered.
3. Select the Test Data Entry menu selection.
4. Enter DMR test data for each outfall for the report period on the Test Data Entry screens.
5. Save the DMR test data results. Data is validated and errors are displayed on the screen.
6. Correct any errors using the Test Data Entry screens.
7. Repeat steps 5-6 until all errors have been corrected.
8. Submit the DMR test data results to the Data Reviewer.
The above documented process will change to the following for facilities using the XML Load feature in eDMR:
1. Log into eDMR as a Data Entry User or Data Entry Proxy user.
2. Select the facility for which DMR test data results are to be loaded.
3. Select the Load XML menu selection, as shown on the following screen shot:
[pic]
4. Enter the name of the XML file containing the DMR test data and select the Load XML Data button to initiate the load.
.[pic]
5. After uploading the XML file, the eDMR application will validate it against the eDMR XML schema. Schema validation verifies the structure of the XML file, data types, and field lengths. In addition to the XML schema validation, the DMR test data is validated in context with the permitted values and limits. If errors are found during the validation then errors will be displayed on the screen. The XML file must be corrected and resubmitted.
6. If no validation errors are found in the XML test data from step 5 above, the user is asked for confirmation to save the DMR test data results. If the user responses affirmatively then the DMR test data results are saved, otherwise the XML test data is discarded. If the DMR test data results are saved the data are subjected to the same validation that is performed when the user manually enters DMR test data and selects the Save button on the Test Data Entry screen. Validation at this level includes comparison against permitted limits and precision requirements.
7. When the load is complete, the user queries each DMR for the reporting periods submitted in the XML file.
Error and warning messages from the “Save” validation in step 6 are displayed as each DMR is queried. DMR test results can be corrected using the DMR Test Data Entry screen, or the data in the XML file can be corrected and resubmitted, provided the DMR is in its initial state.
A DMR is in its initial state following the load. If any data is manually entered or changed for a DMR through the Test Data Entry screen following the load, the DMR is no longer in its initial state, and the XML file cannot be resubmitted.
When the DMR is error-free, it can be submitted to the reviewer by selecting the Submit to Test Data Reviewer on the Test Data Entry screen.
Note: Whenever a DMR is submitted through an XML file for a reporting period/outfall for which DMR results already exist, all of the DMR results in eDMR for that reporting period/outfall are first deleted, then replaced with results in the XML file. For daily results, only the tests for those days in the XML file are deleted and replaced.
eDMR XML Schema
This section presents the eDMR XML schema for generating DMR test data results. Tags in bold are required if its parent tag is included. The root tag is required to enclose the data.
Each DMR report in the XML file is identified with a tag (“Parent” tag). This tag identifies the beginning of a DMR report and must include the Permit Identifier (Permit Number), Outfall, and Monitoring Reporting End Date. Beneath the tag there may be tags and/or tags to specify the test data results for each of the parameters on that DMR report. An outfall with no discharges for the reporting period will only have a tag with a tag included, and no or child tags. Below each there may be tags to report the toxicity test results for that parameter.
Tags with no data may be omitted from the file.
Following the schema layout is a description of each tag.
characters from the test value, if applicable. |
|Invalid Monitoring Location Code | | must represent a valid monitoring location (sample point) code. |
| | | |
|Invalid No Discharge Code | |This message indicates that the code submitted to report no discharge at the DMR level or the |
| | |parameter level is not valid. The code should not include the leading “N” that is normally |
| |or |used when entering data on the Test Data Entry screen. If the error is at the parameter level,|
| | |the parameter code and monitoring location in the message identify the that |
| | |has the error. |
|Invalid No Discharge Code for Daily Report | |This message indicates that the code submitted to report no discharge on the daily report is |
| | |not valid. The code should not include the leading “N” that is normally used when entering |
| | |data on the Test Data Entry screen. The parameter code and monitoring location in the message |
| | |identify the that has the error. |
|Invalid Sample Frequency Code | |The code submitted is not a valid sampling frequency code. |
| | | |
|Invalid Sample Type Code | |The code submitted is not a valid sample type. |
| | | |
| |or | |
| | | |
| | | |
|Invalid test value | |The report value submitted must be numeric. The tag and value that caused the error (such as |
| |See comment |) are appended to the message. Use the qualifier tags to represent “less |
| | |than” or “greater than” and omit the < or > characters from the test value. |
|Monitoring Location is required | | cannot be blank or omitted |
| | | |
|MonitoringLocation is required for Daily Test | |The tag for a daily test was blank or omitted. |
| | | |
|No Discharge cannot include reported values | |If the tag for a is submitted with a value, the |
| | |reported value tags must be blank or omitted |
| | | |
| | | |
| | | |
| | | |
| | | |
|No Discharge cannot include reported values for| |If the tag is not blank (indicating no discharge on the test date), the |
|Daily Report | | must be blank or omitted. |
|No Discharge Report cannot include daily | |A that has no discharge for at the DMR level |
|parameters | |( value is not blank) cannot include child tags. |
|No Discharge Report cannot include parameters | |A that has no discharge for at the DMR level |
| | |( value is not blank) cannot include child tags. |
| | | |
|Outfall is required | |The Outfall Identifier is blank |
| | | |
|Outfall not found | |The Outfall Identifier is not a valid outfall for the permit |
| | | |
|Parameter is required | | cannot be blank |
| | | |
|Parameter not found | |The Parameter Code is not valid for the DMR reporting period and monitoring location. |
| | | |
| | | |
|Parameter not found for daily report | |The Parameter Code is not valid for the daily report |
| | | |
| | | |
|Parameter Code is required for Daily Test | |The tag for a daily test was blank or omitted. |
| | | |
|Permit number mismatch | |The permit identifier does not match the permit identifier selected when the user logged in, or|
| | |the permit identifier is blank. Log in and select the correct permit, or correct the XML file |
| | |to match the permit identifier for the logged in user. |
|Test Date for Daily Tests must fall within | |The test date for daily tests must fall within the same month as the DMR reporting period. |
|monitoring period | | |
|Toxicity test date cannot be greater than | |The toxicity must be prior to the |
|report end date | | |
|Toxicity tests not allowed | |Toxicity tests may only be included for parameters requiring the for the reporting period. |
| | |Omit tags from the XML file for parameters that do no require toxicity tests. |
|Valid entries for PASSFAIL tests are PASS and | |Valid entries for are PASS and FAIL only. An invalid value was submitted. |
|FAIL | | |
|Valid entries for PASSFAIL toxicity tests are | |Valid entries for are PASS and FAIL only. An invalid value was submitted. |
|PASS and FAIL | | |
|Valid toxicity test type ….. is ….. | |The valid test types are LINEAR, LOGISTIC, and PASSFAIL. The error message specifies the test |
| | |type that is valid for the submitted parameter. |
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.