Landing and production reports can be generated by seafood processors' business systems and imported into eLandings, to reduce data entry effort. The eLandings system provides both web pages and fully automated web service methods to allow the import of reports. Report XML documents must be produced in accordance with the eLandings XML schema. The data elements required for landing reports are documented on Landing Report Data and those required for production reports are documented on Production Report Data.
The eLandings system provides two means of importing reports. The eLandings web application has a Report Import page that allows import of both landing and production reports. It can be reached by clicking on the "Import Report" menu link on the main Report Menu page. The eLandings system also provides web service methods that allow seafood processors' business systems to automatically import reports to eLandings. The web service methods are documented on Public+Web+Service+Documentation.
Attributes
When preparing an XML document for import, no attributes should be specified. Only data elements are read when the report is imported into eLandings. The attributes contain additional data that is associated with the element values in the eLandings database. The eLandings system populates the attributes with the associated data when it creates documents for users, but does not need to read attribute data when receiving reports.
Considerations for Using the Report Import Page
The Report Import page allows users to import landing and production reports, one at a time. Reports are imported in the unsubmitted status. Once the report has been successfully imported, users must review it and submit it. Imported landing reports must be initially submitted, and finally submitted, just like reports created directly in eLandings. Production reports do not have a distinction between initial submit and final submit, they just need to be submitted after they are imported. As a consequence, the XML document for reports does not have to specify the status element. If the status element is specified, it must have the unsubmitted status value.
The Report Import page has some flexibility in the use and assignment of report identifiers. Both landing reports and production reports have a report ID, which uniquely identifies the report. Landing reports also have fish ticket numbers, which identify what parts of the harvest documented on the landing report are assigned to which CFEC permits. The report ID can be handled in one of two ways.
- The report ID can be omitted from the report. In that case, eLandings will generate a new report ID that is guaranteed to be unique. Once the report is imported the report ID is visible on the web pages, and will be present in the report XML document if it is exported from eLandings.
- The report ID can be specified in the XML document when it is constructed. It then becomes part of the import. In this case, the report ID must be obtained from the eLandings system prior to constructing the XML document.
Fish ticket numbers can be retrieved as importable numbers from Operation page, get importable numbers button.
When importing a landing or production report to eLandings, the XML document need not have every data item populated. Attributes should not be provided since they are populated by eLandings based on element data. For example, the species code element only needs its numeric code, such as "200". The name attribute should not be provided, eLandings knows that "200" is "Halibut". If attributes are entered they will be ignored. Therefore if you provide the species code as "200", and give the species_code name attribute as "Pollock" eLandings will identify the species as 200 Halibut. The species_code name will be ignored, and you will not get an error message that 200 does not equal Pollock.
...