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

implement congruency checks between data & metadata #50

Open
atn38 opened this issue Nov 4, 2019 · 4 comments
Open

implement congruency checks between data & metadata #50

atn38 opened this issue Nov 4, 2019 · 4 comments

Comments

@atn38
Copy link
Contributor

atn38 commented Nov 4, 2019

the ones not yet in ECC

  • attribute order match between data header and EML
  • attribute names match between data header and EML
  • attribute missing codes and enumeration match between data and EML
@gastil
Copy link

gastil commented Nov 4, 2019

I was hoping the pasta checker would get around to those checks. Currently the header-match is an info-level, human-viewed check.
And the enum check would have saved me grief.
Are you concerned you might be duplicating effort, doing this both in MetaEgress and (in future) pasta? Tho they say errors are best caught closest to the source. And who knows when check coding will resume in pasta.
So I vote yes please.

@atn38
Copy link
Contributor Author

atn38 commented Nov 4, 2019 via email

@atn38
Copy link
Contributor Author

atn38 commented Nov 15, 2019

a first attempt at the function at https://github.com/BLE-LTER/MetaEgress/blob/congruence/R/check_attributes_congruence.R

next: integrating this into create_entity and issue warnings/errors as appropriate.
plus issue more detailed messages, think about a way to check for presence of missing codes in data not listed in metadata

@atn38
Copy link
Contributor Author

atn38 commented Jan 10, 2020

not closing this yet, since the function needs improvements

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

No branches or pull requests

2 participants