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

As a user, I want to validate content for all possible PDS4 table types #217

Closed
4 tasks done
Tracked by #710
jordanpadams opened this issue Apr 17, 2020 · 6 comments
Closed
4 tasks done
Tracked by #710

Comments

@jordanpadams
Copy link
Member

jordanpadams commented Apr 17, 2020

Is your feature request related to a problem? Please describe.
Right now, Validate only handles a subset of table types, but we need to make sure we check all possible objects.

This is a follow-on to #149

See referenced from section under each of these for the classes we need examples and test cases for.

@rchenatjpl
Copy link
Contributor

Here are test files. In each set of 3, the ones with records=2 or 4 should fail while the one with records=2 should pass. Filenames: XXXYYYN.xml, where
XXX =
asc: Table_Character
tra: Transfer_Manifest
bin: Table_Binary
del: Table_Delimited
YYY =
anc: File_Area_Ancillary
bro: File_Area_Browse
met: File_Area_Metadata
obs: File_Area_Observational
sup: File_Area_Observational_Supplemental
upd: File_Area_Update
inv: File_Area_Inventory
N = value of . All data files have 3 records

These cases are covered, based on Jordan's IM list:
Table Character: anc bro met obs sup
Table Binary: anc bro obs sup
Table Delimited: anc bro met obs sub inv

Not covered: XXXsupN because File_Area_Update is deprecated
Not covered: traYYYN. Does someone have a sample? I don't work with NSSDC
Not covered: the IM does not mention Table_Delimited_Source_Product_External or Table_Delimited_Source_Product_Internal, but the .xsd does

val217.zip

@jordanpadams jordanpadams changed the title Update Content Validation to handle all table types As a user, I want to validate content for all possible PDS4 table types Mar 14, 2021
@jordanpadams jordanpadams added p.must-have requirement New requirements and removed enhancement New feature or request requirement-needed labels Mar 14, 2021
@jordanpadams jordanpadams added B13.0 and removed icebox labels May 9, 2022
@jordanpadams jordanpadams removed the B13.0 label Feb 3, 2023
@jordanpadams jordanpadams added B14.0 and removed B13.1 labels Mar 23, 2023
@al-niessner
Copy link
Contributor

@jordanpadams @rchenatjpl

This has been a few years waiting. It looks to already be fixed but want to make sure I understand the test data and expectations. It seems like records 2 and 3 pass because the table is smaller or equal to what is there while records of 4 fail. Is this the correct expectation?

@jordanpadams
Copy link
Member Author

jordanpadams commented May 11, 2023

Here are test files. In each set of 3, the ones with records=2 or 4 should fail while the one with records=2 should pass.

@rchenatjpl just to verify, should this say:

the ones with records=2 or 3 should fail while the one with records=4 should pass.

@rchenatjpl
Copy link
Contributor

@jordanpadams You're right. Boy, this is like software anthropology.

@jordanpadams
Copy link
Member Author

@al-niessner per above, that is correct. if those tests are implemented in the PR then we should be good to go

@jordanpadams
Copy link
Member Author

closed per #640

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants