A series of on-demand metric reports were added to the reports menu in AGIIS for Directory Administrator use only. These reports will help aid the Directory Administrator in gathering metrics information for presentations, billing and directory maintenance. The following four reports were added:
General Metrics Report – Provides overall counts and totals such as #entities, #products, #licenses, #active subscribers
Product Metrics Report – Provides totals of companies with products in AGIIS broken down by product type (Chemical, Fertilizer, Seed, Feed)
Product Extract Report – Provides list of users and their active product extracts
Subscriber Metrics Report – Provides subscriber specific metrics around AGIIS usage
On Saturday, 2 May, 2020 AGIIS was updated to enhance the Product Import Notification email that product owners receive when a product import file is loaded into AGIIS. Now, along with receiving import errors within the body of the confirmation email as before, the errors are also included in an attached Excel file. This will allow users to use Excel functionality to filter, sort and search to help aid in error reconciliation. This change was suggested by a subscriber that loads product into the AGIIS Directory.
A sample file that users will receive is provided below. The file contains the original File Name, Line Number, Product Number, GTIN, Error Code and Error Message.
On Saturday, March 14, 2020, AGIIS was enhanced to include Representational State Transfer (REST) API to support Entity Update functionality.
Subscribers wishing to utilize the REST services should contact Member Services to obtain user login credentials.
Swagger documentation has been added to the Links menu in AGIIS underneath the Tech Tools sub-menu, by clicking on the Rest Web Services link. Swagger is a set of rules or specifications for a format describing REST APIs. The format is both machine-readable and human-readable, therefore can be used to share documentation among product managers, testers and developers, but can also be used by various tools to automate API-related processes.
The following Swagger resource guide will help users who want to test basic REST functionality.
Swagger Resource Guide
For more detailed testing and implementation, users can also use Postman. Download Postman HERE. Below is a helpful resource guide to help users implement this testing resource.
Postman Resource Guide
If you have any questions about the REST Web Services enhancement, or would like to obtain user credentials, please contact Member Services by phone or email, both of which are listed above.
AGIIS uses address standardization software to return potential match candidates in an Add or Update request. The software selects potential candidates for a match, and if there is more than one, a prioritization process is used to determine the best match. The prioritization match criteria follow:
An AGIIS subscriber pointed out that the match returned was sometimes that of an inactive entity, yet the return file provided an active, replacement GLN to the inactive entity. To eliminate manual research, the subscriber requested that AGIIS simply return the active entity GLN in the return file.
With this enhancement, the “Active” status of an entity was incorporated into the existing prioritization criteria. Now, if multiple records are identified as a match, AGIIS will place a higher priority on an Active entity over that of an inactive entity.
On Saturday, November 23, 2019, AGIIS was enhanced to include Representational State Transfer (REST) API to support both Entity and Product Lookup functionality.
This enhancement is a recommendation of the 2018 Post Deduplication Analysis. Each year the AGIIS Member Services team performs an analysis of the Annual De-duplication process and looks for improvements in the process. This year the team identified a legacy business rule (The Master EBID Rule) that was no longer applicable to the De-duplication process. The rule was harboring potential duplicate sets in the AGIIS system.
The EBID Mater Rule was created to prevent EBID's from being replaced by an entity that does not have an EBID in the Annual Deduplication process. This rule only applied during the Annual Deduplication process. The legacy rule was established when EBID identifiers were being populated with Duns Plus Four Numbers and GLN's were based on a GS1 Prefix (like they are today). At that time the rule was more pertinent because there would be situations where an entity with an EBID and GLN were going to be replaced by an entity with only a GLN. If that entity with an EBID was replaced it was not an absolute that the Duns number value would stay the same without confirming with D&B so that is why the decision was made to exempt these entities from the Annual Dedupe process.
Over the past several years the system and process has evolved to meet Subscribers needs and the benefits of the Master EBID Rule has declined and, in many cases, causing a negative impact to AGIIS by harboring duplicates. One of the major changes is the value of the identifier's has changed to be the same value (EBID's and GLN's are both based on the GS1 Prefix and are always the same value). It is also important to point out that over the last 5 years the Directory Oversight Committee has made many improvements to the Annual Dedupe process and the system in general to prevent duplicates from entering the system, but the Master EBID Rule is preventing entities from even being considered to be evaluated during the Annual Dedupe.
This Enhancement will be in place for the 2019 Annual Deduplication process and the impact of improvement will be measured in the 2019 Post Deduplication Analysis.
On Saturday, June 29, 2019, AGIIS was enhanced to incorporate several web interface features and modifications. These changes were suggested by subscribers as part of the AGIIS modernization initiative.
Several physical changes were made to the AGIIS search page. First, the Identifier Search field has been moved from the bottom of the page to the top. Additionally, the "Identifier Value" search field has been simplified by modifying the search logic to consider all identifiers (GLN and EBID) and removing the associated identifier drop down box.
By default, the search includes both EBID's and GLN's as shown below in the, "Include Entities having" section. To modify this criterion, simply check or un-check these boxes to fit your search criteria.
This "Identifier Value(s)" field now also allows for multiple identifiers to be searched by separating each with a comma.
Results containing just one entity will be presented on the Entity View page. Multiple results will appear on the Entity List page as shown below.
Another new search feature is the ability to use a wild card when performing a Prop Code search. In the example below, a search is being performed to return all entities that are cross-referenced to the subscriber beginning with the value, "724940".
Because there are multiple returns, the results appear on the Entity List page. A single return would appear on the Entity View page. In the image below, AGIIS returned all entities that are cross-referenced to the subscriber that begin with the value, "724940".
Another new feature is the addition of Google search help. Two new Google icons, map search and web search, have been added to the Entity Search and Entity Add/Update/Activation pages. Because not all addresses are deliverable or are able to be standardized by the United States Postal Service, this feature has been incorporated to help validate an address.
The Google Maps icon will locate the address within Google Maps based on the address, city, state and postal code entered, as shown in the images below.
With a name and address entered, pressing the Google Search button will perform a web search using both name and address as shown in the two images below.
Lastly, search logic is being updated to perform a search on both address lines 1 and 2, of both physical and mailing addresses. Today, the search is performed using address line 1. This will better help locate entities that may have an "In care of" name in address line 1 and the street address in line 2.
If you have any questions regarding the upcoming release, please contact Member Services at Member.Services@AgGateway.org, or call (866) 251-8618.
Product Search, Inactivation/Deletion Enhancement - PCR #219
The Product Search, Inactivation/Deletion Enhancement provides product manufacturers the ability to search AGIIS for products by primary category, variety/hybrid or product ID to perform a mass deactivation or deletion. Based on the input criteria, a list of products is displayed for review. This list allows users to remove one or more products from consideration prior to performing a mass deactivation or deletion. The following images outline the steps to utilize this new functionality. In this example we are performing a mass deletion.
From the Company View page, click ”Update Information“.
The Company Update page below is displayed. Click on, "Mass Deactivation/Delete".
The Mass Deactivation/Delete Page below is displayed. This page allows you to review a product subset based on your input criteria and allows you to remove one or more products from consideration prior to performing the mass deletion.
You must choose to either Deactivate or Delete using the "Operation" radio buttons. Deleting a product will take it out of AGIIS altogether, while deactivating a product will keep the product in AGIIS, but in an "Inactive" status.
Choose either "Last Verified" or "Last Modified" to delete products last verified or last modified prior to the date entered.
Choose to see all products or those under a primary category by clicking one of the Primary Category radio buttons.
A product identifier can be entered into the Product Identifier field to review products under a specific product ID. Likewise, a Variety/Hybrid can be entered to mass deactivate or delete products matching the variety/hybrid entered. In this example, we are leaving these fields blank.
Once all information is entered, click on the "Search" button.
The page below shows all of the products that matched the input criteria. Notice there are several products highlighted in yellow. These products are in another subscriber's product subset and can't be deleted until the subscriber removes these products from their subset. When performing a Deactivation, this rule does not apply.
Clicking on the hyperlink in the "Subscriber Subsets" column will display a page similar to the one below. The subscriber(s), along with the email address of their company contact, and the Product GTIN is displayed. This information is provided so that you can contact the subscriber and request they remove the product from their subset.
To remove one or more products from being deleted, check the appropriate box the "Remove" column and click on the, "Remove Selected Items from Results" button. It is not necessary to remove those products highlighted in yellow as they are exempted from being deleted.
Once the product grid contains only those products you wish to delete, click on the "Delete" button. In this example, there are two remaining products eligible for deletion.
Finally, a confirmation page displays providing the number of products deleted.
CSV EBID/GLN Entity Subset Extract Creation Enhancement - PCR #220
The CSV EBID/GLN Entity Subset Extract Creation enhancement provides AGIIS subscribers the ability to generate a full entity subset extract in a CSV file format. Other format options are XML and fixed length text.
To schedule an EBID or GLN subset extract in the new CSV file format, hover over the "Files" menu in AGIIS and click on, "Schedule Extracts". The following page appears. Click on the, "Request Entity Subset Extract" button.
On the following page, choose either EBID or GLN Subset from the Subset Type drop down menu. Choose, "CSV" from the Extract Format drop down menu. Click, "Submit". You will be notified via email once the extract is complete.
Below is a link to the CSV Entity subset extract file layout.
CSV Entity Subset Extract File Layout
A complete set of release notes for both enhancements will be sent out on Monday, April 22, 2019. If you have any questions, please contact Member Services at Member.Services@AgGateway.org, or call (866) 251-8618.
GLN Bulk Process Name Standardization Enhancement
The GLN Bulk Process Name Standardization Enhancement, takes the name standardization enhancement that was implemented on the website and web services in September 2017, and later to the 2017 annual de-duplication maintenance, and applies it to the GLN bulk process.
The name standardization functionality will provide more robust name standardization when trying to determine a match in the bulk process. This functionality will improve name matching for abbreviations, support individual name vs business name matching scenario’s and provide flexibility to assist in decreasing false positive matching.
Below are two examples of improvement in decreasing false positive matching. Prior to the enhancement, AGIIS likely would have matched the two entities together based on the similarity in the name and having identical addresses. Since the enhancement, AGIIS recognizes their differences and will not match the two together.
Example 1
John Doe, 123 Main St, Anytown, USA and John Doe Farms, 123 Main St, Anytown, USA
Example 2
Jane Doe, 828 Sycamore, Anytown, USA and Jane & John Doe, 828 Sycamore, Anytown USA
The second enhancement, AGIIS Sponsorship Recognition Banner, displays the company logos of those subscribers that have historically provided significant financial support above the published AGIIS subscription rates. With these companies’ permission, they are being recognized by having their company logo scroll across the AGIIS login and home pages. Companies that have authorized the use of their logo are BASF, Bayer, Dow Agrosciences, Dupont/Pioneer, FMC Corporation, Syngenta, Tessenderlo Kerley, and Valent. The image below provides an example of this.
GTIN Logic Modification Enhancement
On Saturday, May 12, 2018, AGIIS was enhanced to accommodate a variable length, GS1 company prefix in the formulation of the 14‐digit Global Trade Item Number (GTIN). The GTIN uniquely identifies a product in AGIIS at its lowest saleable unit. A GS1 Company Prefix is a unique identification number that GS1 issues companies using bar coding and product code identification, such as the GTIN. The 14‐digit GTIN utilized in AGIIS is created by combining four components, a Package Level Indicator, GS1 Company Prefix, Package Size ID and Check Digit.
Historically, company prefixes were assigned by GS1 that were 7‐digits in length. This meant that the Package Size ID was always 5 digits in length, as both the Package Level Indicator and Check Digit, are each 1‐digit.
Now, GS1 is assigning company prefixes that vary in length. As AGIIS was originally programmed to require a 7‐digit Company Prefix and 5‐digit Package Size ID, updates were made to accommodate a GS1 Company Prefix between 1 and 11‐digits. The Package Size ID may now contain between 1 and 11 numeric digits but, the combination of the GS1 Company Prefix and the Package Size ID must equal 12‐ digits.
New requirements for the construction of the 14‐digit GTIN is provided below.
Updates have been made to the AGIIS Product file layouts Product 3‐Level (CSV) and GTIN Level 1 (CSV) to reflect these changes. These file formats, along with the XML product update document, can be found in the Product section in AGIIS under the Links menu. If you have any questions about this enhancement, please contact Member Services at Member.Services@AgGateway.org, or call us at (866) 251‐8618.
Verification Date Enhancement
AGIIS was enhanced on Saturday, January 20, 2018 allowing the AGIIS Directory Administrator to update the "Last Verification Date" on an entity even if the requested update is declined.
Before, if a subscriber requested Member Services verification (phone or web verification) on updated entity demographics, and the update was declined after performing verification, the "Last Verification Date" did not update. With this enhancement, the "Last Verification Date" will update regardless if the demographic update is accepted or declined. In the example below, phone verification was requested on an update to the mailing address. In the side by side comparison of the history, you can see that no update to the entity demographics were made, yet the "Last Verified" field was changed from "None" to "Member Services Level: Tier 2- Phone/Email + Web Verification on 01/22/2018." Member Services verification determined that the existing address on the entity was correct. The update was declined, but because a phone verification was performed confirming the address, the "Last Verified" field is updated with the date and type of verification performed.
If you want to access the 2017 AGIIS Enhancements page, click here.
Release Notes
[PDF] 2020
[PDF] 2019
[PDF] 2018
[PDF] 2017
[PDF] 2016
[PDF] 2015
[PDF] 2104
[PDF] 2013
[PDF] 2012
[PDF] 2011
[PDF] 2010
[PDF] 2009
[PDF] 2008