usda / data-standards Goto Github PK

The JSON schemas are using development url such as "id": "http://localhost:4000/json-schema/field.json" These need to be replaced with url on github for validation.

1. geospatialSourceDataCreationDate and geospatialShapeProcessDate data type in geospatialMetadata.json should be Datetime with format YYYY-MM-DDTHH:MM:SSZ to match prior standards.
2. originalPlantedDate, finalPlantedDate data type in agriculturalProductionPlan.json should be Date to match prior standards.
3. Producer Share Percent data type in producerShare.json should be Decimal (5,4) to match prior standards.

1. The element titled “middleName” with “title” = “First Name” in customer.json should have the element name changed to “firstName” to match prior standards.
2. The element name “TractNumber” in tract.json should be renamed “tractNumber” to match prior standards.
3. The element name “FieldNumber” in field.json should be renamed “fieldNumber” to match prior standards.
4. The element name “Producer Share Percent” in producerShare.json should be renamed “producerSharePercent” to match prior standards.

With 375+ unique commodity codes (Core Product Code) that will be updated periodically, there is a need to publish these reference codes in parallel of ACRSI project releases.
Requirements:

• Allow third party software providers, producers, AIP (Approved Insurance Providers), County Offices to select and utilize correct set of core product codes while submitting their CART file.
  Advantage: Reduce or eliminate complex communication for exception handling during CART data file submissions.

Challenges:

1. There are interdependencies between Core Product Codes with Core Product Code Types (sub-classification codes), and other codes. These product types need to be matched with Core Product Codes providing correct sets of combination.
2. There is no readily defined mechanism to provide the above (Open data set publication, Schema Definitions, API, etc.)
3. RMA and FSA may recognize different sets of Core Product Code as they have not been through governance process to agree and recognize a single agreeable code sets.

Location Polygon Coordinates Profile under Acreage Crop Reporting needs the correct data type code and example.

https://usda.github.io/data-standards/data-elements/Location_Polygon_Coordinates.html

CLU is required but field operations software providers are not able to use it to relate planting records and harvest records.

It would be a lot easier if the CLU became publicly available and we did not have to cross-reference it to a field boundary defined by a retailer or the farmer. As a result of leaving in up to a farmer, and their farming operations, we have a lot of field boundaries that span across counties in a state.

There may be additional codes that have direct dependencies with Commodity Core Product Codes that ACRSI project may need to recognize.
Requirements

• Research on additional dependency such as "Intended Use Code" and their relationship with Core Product Code and Core Product Code Type.

It is redundant to include both min/maxLength and enumerated codes for example in organicPracticeTypeCode https://github.com/USDA/data-standards/blob/gh-pages/json-schema/agriculturalProductionPlan.json The validation could be done just by the enumerated lists.

The pros for having both in place are for clarity and ease of use. It will also help in determining whether to add new value that exceed current highest maxlength which could break backward compatibility of databases.

The cons are that it's additional information that will need to be kept up to date if enumerated list adds value that exceeds

In the documents field.json and all-elements.json, the cluIdentifier data type, minLength and maxLength do not match the Exchange Content Model, and the description is identical to that of fieldNumber. This page gives the following description:

A system-generated internal identifier of a common land unit (CLU). This identifier is for internal access use only. A CLU is the smallest unit of land that has a permanent, contiguous boundary, common land cover and land management, a common owner, and a common producer association. A CLU is closely related to FSA''s definition of 'fields', according to Handbook 2-CP. A CLU is also closely related to land units such as parcels, farmsteads, and lots that are used by NRCS, RMA and RD. The authoritative source of CLU Identifier is Farm Records. CLU Identifier can remain constant even if the precise geospatial shape of the CLU is slightly altered.

The Exchange Content Model suggests type = "string" with minLength = maxLength = 36, the same as the previous standard.

1. originalPlantedDate and finalPlantedDate minLength & maxLength in agriculturalProductionPlan.json should be 10 to match prior standards.
2. organicPracticeTypeCode maxLength in agriculturalProductionPlan.json should be 2 to match prior standards.

Some Boolean have Y or N and some Boolean have true and false. For example Precision Agricultural Sub Meter Accuracy Indicator has Y as example

With 2000+ unique Core Product Code Type (sub-classification codes of Core Product Code) that will be updated periodically, there is a need to publish these sub classification codes in parallel of ACRSI project releases.
Requirements:

• Allow third party software providers, producers, AIP (Approved Insurance Providers), County Offices to select and utilize correct set of core product code types while submitting their CART file.
  Advantage: Reduce or eliminate complex communication for exception handling during CART data file submissions.

Challenges:
Same challenges applied as defined in issue for ACRSI - Core Product Code

1. Page should load using the client browser settings for size, style, font to add accessibility to Section 508 users and for users with restricted system capabilities.
2. Normalize what you can to maximize breadth of user availability and access to information.
3. At top of page, include a left, vertical, Navigation Menu; "Where to go from this page."
4. Navigation Menu should always have a link to the "Site Map" and "References Page."
5. At the top of the page, include a thin horizontal navigation bar that is hyperlinked by page. "How the user got here."
6. Loop the internal links. If there is a link to another section on the page or to another page, provide a link for the user to return to the original page if they desire.
7. Manage user required throughput. If possible include an option to run dynamics hosted by the server to maximize breadth of user availability and access to dynamic content.

1. Create a "Dead Link Default" page or popup that self populates with the dead link URL and includes an email for notifying the Webmaster for corrections.
2. Add hyperlinks for agencies, organizations, and documents referred to in the text of the pages.
3. Add user orientation. The homepage header, navigation menu, and navigation bar should remain at the top of the page at all times so the user never feels as if they are getting lost or have hit a dead-end. The text or body of the page should scroll or can be hyperlinked by looped sections.
4. Add a regulatory user feedback option. Add a "Complaints, Comments, and Suggestions," link to an email popup on the bottom of each page that self populates with the page URL to allow the user to provide timely feedback. The email can be structured in an MS Outlook survey so it will automatically populate an Excel spreadsheet for ease of follow up, logging, and tracking.
5. Include the USDA Footer for including other required, regulatory notifications and user rights, etc.
6. For clarity, data integrity, and trust: Match text used with navigation links to the title of the page linked and the text of the page. For example:
   A "My Special Project" link on the Project Data Domain Page links to a page entitled: "My Special Project Data Standards and Collaboration Space." The title of the body text on the linked page reads "My Special Data Initiative." The title of the page and the text of the link should be the same. In this case, the navigation bar would look like: "My Special Project/My Special Project Data Standards and Collaboration Space." The link leads to an "Initiative" page. The actual “initiative” should also be available from the Initiative page. The page seems to be about the initiative but there is no definition or link to the initiative. The title of the link implies the user will find many links to standards and collaboration sites which are not included. A possible fix would have a Navigation Bar that reads: "My Special Project/My Special Project Data Standards and Collaboration Space/My Special Data Initiative." The Data Initiative information would be located as a link from the Standards and Collaboration page and would include a definition and reference links.
7. Ensure user orientation through consistency. Verify data with titles on the navigation bar. The Body and Text of the page should correspond to the title of the page which should be the same as the title of the link in the navigation bar and the title of the link in the text or menu on the page(s) that leads to the linked content.