You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Focuses on validating values in a data file submitted to Tripal Cultivate Phenotypes Share Importer.
There is a Plugin Type for validators which was created as part of #37. Each type of validation we want to do is an instance of this plugin. A scope is assigned to each validator instance to indicate what part of the file it validates and the order it should be in.
This issue is to design validator instances focused on validating the new phenotypes file format. The first attempt of this by Reynold, validated all values/columns in the file in a single validator. However, we would like to move to a different model.
Design
Create an instance of validator plugin: PhenoShareImportValues
Trait Name - Trait name exists in the cv configured for trait in the genus selected. This column is required.
Method Name - Method name exists in cv configured for method in the genus selected and is one of the methods paired to the trait name. This column is required.
Unit - Unit must exists in the cv configured for the unit in the genus selected. This column is required.
Germplasm Accession - Must exists in chado.stock table. This column is required.
Germplasm Name - Must exists in chado.stock table. This column is required
Year - A four digit value and must not exceed the current year. This column is required.
Replicate - an integer value. This column is required
Value - Use the unit data type to determine the data type for this column. A quantitative unit will require numeric value whereas qualitative value will be descriptive text. This column is required
Data Collector - String, name of a person, institute or organization. This column is required.
The text was updated successfully, but these errors were encountered:
These have been removed from the linked PR to allow it to be merged.
We are going another direction here with a row-level validator rather then needing a helper and each validator looping through the entire file. Also the columns are changing which changes this validation in particular.
That said, there is important code in these files that will be useful so I am attaching them here for use later.
Branch
g4.58-Phenoshare-Values-Validator
Groups
Group 4 - API | Services | Plugins
Describe
Focuses on validating values in a data file submitted to Tripal Cultivate Phenotypes Share Importer.
There is a Plugin Type for validators which was created as part of #37. Each type of validation we want to do is an instance of this plugin. A scope is assigned to each validator instance to indicate what part of the file it validates and the order it should be in.
This issue is to design validator instances focused on validating the new phenotypes file format. The first attempt of this by Reynold, validated all values/columns in the file in a single validator. However, we would like to move to a different model.
Design
Create an instance of validator plugin: PhenoShareImportValues
The plugin will validate the following:
The text was updated successfully, but these errors were encountered: