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

Test dates for matching data with metadata #32

Open
33 of 36 tasks
peterdesmet opened this issue Dec 8, 2014 · 1 comment
Open
33 of 36 tasks

Test dates for matching data with metadata #32

peterdesmet opened this issue Dec 8, 2014 · 1 comment
Assignees

Comments

@peterdesmet
Copy link
Member

Data will be matched to receivers using receiver_id and date_time. Errors or missing information in the metadata can cause errors though. Here are a number of test cases and the predicted output. We'll have to review if this is adequate enough.

Receiver only deployed once

Test date: 2012-06-30

  • a-single: 2012-07-01 / 2014-07-09 → No match
  • b-single: 2012-07-01 / null → No match
  • c-single: null / 2014-07-09 → Match before
  • d-single: 2014-07-09 / 2012-07-01 (error in metadata) → No match
  • e-single: null / null → Match

Test date: 2013-01-01

  • a-single: 2012-07-01 / 2014-07-09 → Match between
  • b-single: 2012-07-01 / null → Match after
  • c-single: null / 2014-07-09 → Match before
  • d-single: 2014-07-09 / 2012-07-01 (error in metadata) → No match
  • e-single: null / null → Match

Test date: 2014-07-10

  • a-single: 2012-07-01 / 2014-07-09 → No match
  • b-single: 2012-07-01 / null → Match after
  • c-single: null / 2014-07-09 → No match
  • d-single: 2014-07-09 / 2012-07-01 (error in metadata) → No match
  • e-single: null / null → Match

Receiver deployed two times

Test date: 2012-06-30

  • a-double: 2012-01-01 / 2012-06-29, 2012-07-01 / 2014-07-09 → No match (between pairs)
  • b-double: null / 2012-06-29, 2012-07-01 / null → No match
  • c-double: null / 2012-07-01, 2012-06-29 / null (error in metadata) → Match for both
  • d-double: 2012-01-01 / null, null / 2014-07-09 (missing info in metadata) → Match between both
  • e-double: null / 2012-06-29, null / 2014-07-09 (missing info in metadata) → Match before second
  • f-double: 2012-01-01 / null, 2012-07-01 / null (missing info in metadata) → Match after first
  • g-double: null / null, null / null (missing info in metadata) → Match for both

Test date: 2013-01-01

  • a-double: 2012-01-01 / 2012-06-29, 2012-07-01 / 2014-07-09 → Match between second pair
  • b-double: null / 2012-06-29, 2012-07-01 / null → Match after second
  • c-double: null / 2012-07-01, 2012-06-29 / null (error in metadata) → Match after second
  • d-double: 2012-01-01 / null, null / 2014-07-09 (missing info in metadata) → Match between both
  • e-double: null / 2012-06-29, null / 2014-07-09 (missing info in metadata) → Match before second
  • f-double: 2012-01-01 / null, 2012-07-01 / null (missing info in metadata) → Match after both
  • g-double: null / null, null / null (missing info in metadata) → Match for both

Test date: 2014-07-10

  • a-double: 2012-01-01 / 2012-06-29, 2012-07-01 / 2014-07-09 → No match
  • b-double: null / 2012-06-29, 2012-07-01 / null → Match after second
  • c-double: null / 2012-07-01, 2012-06-29 / null (error in metadata) → Match after second
  • d-double: 2012-01-01 / null, null / 2014-07-09 (missing info in metadata) → Match after first
  • e-double: null / 2012-06-29, null / 2014-07-09 (missing info in metadata) → No match
  • f-double: 2012-01-01 / null, 2012-07-01 / null (missing info in metadata) → Match after both
  • g-double: null / null, null / null (missing info in metadata) → Match for both
@peterdesmet peterdesmet self-assigned this Dec 8, 2014
@peterdesmet peterdesmet added this to the Change data flow milestone Dec 8, 2014
@peterdesmet
Copy link
Member Author

I created an SQL querie that passes the test, but we'll have to discuss if those results are what we actually want.

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

1 participant