Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate that Table_Character/Table_Binary fields match the field length definitions in the label #56

Closed
msbentley opened this issue Jul 24, 2019 · 7 comments · Fixed by #159
Assignees
Labels
enhancement New feature or request

Comments

@msbentley
Copy link

Is your feature request related to a problem? Please describe.
Currently, validate does not report when the definition of two fields in a Table_Character overlap. This is a relatively common error by data producers, and should be easy to flag.

Describe the solution you'd like
validate should report an error if fields overlap

@jordanpadams jordanpadams added enhancement New feature or request high and removed new-feature-request labels Aug 21, 2019
@jordanpadams jordanpadams changed the title Flagging of overlapping columns in Table_Character field definitions Validate that Table_Character fields do not overlap based upon field length definitions Aug 21, 2019
@jordanpadams jordanpadams added the requirement New requirements label Aug 21, 2019
@jordanpadams
Copy link
Member

@msbentley do you have a product we could use for testing?

@jordanpadams jordanpadams added enhancement New feature or request requirement New requirements and removed enhancement New feature or request requirement New requirements labels Aug 21, 2019
@msbentley
Copy link
Author

msbentley commented Aug 22, 2019

I've just created a (rather silly, admittedly) example product: validate_test_fields.zip

Two of the numeric fields here overlap. The product validates and indeed opens without error, but I can't think of a use case where this would be valid, but perhaps that's my lack of imagination (i.e. I'm not sure if this should be a warning or should fail validation...)

@jordanpadams jordanpadams changed the title Validate that Table_Character fields do not overlap based upon field length definitions Validate that Table_Character fields match the field length definitions in the label Oct 31, 2019
@hhlee445
Copy link
Contributor

hhlee445 commented Dec 9, 2019

Added error message when the definition of two fields in a Table_Character overlap.

Begin Content Validation: file:/Users/hyunlee/dev/pds_en/validate/issue_56/validate_test_fields/minimal_test_product.tab ERROR [error.table.field_value_overlap] table 1, record 1, field 3: The field is overlapping with the next field. Current field ends at 45. Next field starts at 43 ERROR [error.table.field_value_overlap] table 1, record 2, field 3: The field is overlapping with the next field. Current field ends at 45. Next field starts at 43 ERROR [error.table.field_value_overlap] table 1, record 3, field 3: The field is overlapping with the next field. Current field ends at 45. Next field starts at 43 ERROR [error.table.field_value_overlap] table 1, record 4, field 3: The field is overlapping with the next field. Current field ends at 45. Next field starts at 43

@msbentley
Copy link
Author

I assume the same check should be applied to Table_Binary?

@jordanpadams
Copy link
Member

@msbentley correct. do you by any chance have an example? if not, we can poke around.

@msbentley
Copy link
Author

For Table_Binary? No, but I could take my Table_Character example and change it to binary, if you can't find anything else...

@jordanpadams jordanpadams changed the title Validate that Table_Character fields match the field length definitions in the label Validate that Table_Character/Table_Binary fields match the field length definitions in the label Dec 11, 2019
@jordanpadams
Copy link
Member

thanks @msbentley we will ping you if we need it but we can probably do the conversion as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants