eLandings Data Import Approval:
- Notification of intent to import data into the eLandings system.
- Understanding that the use of the tLandings application requires that the entity required to report first purchase, as outlined in 5AAC 39.130, import the landings data into the eLandings system, using the Processor Tender Interface, within the timeframe prescribed by the ADFG.
- Understanding that 5AAC 39.130 requires true and accurate information, necessitating that all corrections to catch species, delivery condition or poundage information be updated within the eLandings system.
- Understanding of and program structure to assure unique numbering of all landing and production reports and fish tickets.
- Understanding of and validation of all code tables associated with the eLandings system.
- Understanding of and use of all eLandings Product Recovery Rates for rounding to whole pounds.
- The ability to identify and report all overages using the established eLandings codes.
- Responsibility for user support for all front end data entry applications that generate XML code that is imported into the eLandings system.
How do I get my software approved?
Specifications: the elandings project provide technical specifications for software here (and we would link to our interface documented). Interested parties may also contact us by email at elandings.alaska.gov
The software must meet the following standards:
- The software must have all the fields for data entry and be designed to ensure that an operator can comply with the NMFS record keeping and reporting requirements as described in ยง 679.5(e) and ADFG reporting requirements as described in .... ?? Gail can you add link ??
- The software must produce pdf formats of reports that can be printed and have time and date stamp and clearly identify whether the report has been submitted. If any changes are made to the data in the software, subsequent printed copies must clearly be identified as revised. The software must be designed to prevent the operator from overriding this feature.
- The software must export data in xml schema as specified here.... link to xml documentation.
- The software must include sufficient data validation capability to prevent a submitter from accidentally transmitting a data file or printing PDF report that is incomplete or contains clearly erroneous data.
A vendor or developer wishing to have software approved must submit:
- A fully operational test copy of the software
- An application for software-approval giving the following information:
- Company, contact person, address, telephone number, and fax number for the company developing the software. Including the printed name and signature of individual submitting the software for approval
- Name and type of software.
- Copies of all manuals and documentation for the software.