eLandings has already been successfully integrated with third-party applications in several ways. To list a few, some third-party applications:
- Pull data from eLandings
- Push data to eLandings
- Pull and push data to eLandings depending on the situation
For example, some third-party developers wanted the ability to include eLandings Individual Fisheries Quota or IFQ data in their system. However, federal regulation requires that IFQ data be created originally in eLandings. Furthermore, the business and mathematic rules associated with IFQ situations can be very complex. A third-party developer would find it very challenging and frustrating to match eLandings rounding rules on numbers exactly. As a result, one third-party developer decided to pull landing reports from eLandings and never push them to eLandings in IFQ situations. The result is that any ticket that is created or edited by a processor using their third-party application was required to do the work first in eLandings and then pull it into their system.
In non-IFQ situations, this same third-party developer wanted to use custom data entry structures, and electronic data feeds (i.e. directly from electronic scales) to make data entry faster and easier for their users. In this case, they were able to create and/or modify the reports in their own system and push the resulting data into the eLandings database.
The simpliest configuration is to have all data flow from eLandings to the third-party application. We recommend this as the first major milestone in third-party development. This alleviates third-party developers from having to match report validation rules found in eLandings. Such a set-up might look like: 