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

duplicate data in timeseries yoda file #38

Open
cdesyoun opened this issue Jan 20, 2016 · 2 comments
Open

duplicate data in timeseries yoda file #38

cdesyoun opened this issue Jan 20, 2016 · 2 comments

Comments

@cdesyoun
Copy link

Jeff,
I think there is duplicate data records below in your recent updated timeseries yoda file generated by ms excel.

Actions:
  - &ActionID0001 {ActionTypeCV:  "Observation", MethodObj: *MethodID0001, BeginDateTime:  "2010-06-03 11:15:00", BeginDateTimeUTCOffset:  -5, EndDateTime:  NULL, EndDateTimeUTCOffset:  NULL, ActionDescription:  "Generic observation action generated by Excel Template for TimeSeries v.0.3.0-alpha", ActionFileLink:  NULL}
  - &ActionID0002 {ActionTypeCV:  "Observation", MethodObj: *MethodID0001, BeginDateTime:  "2010-06-03 11:15:00", BeginDateTimeUTCOffset:  -5, EndDateTime:  NULL, EndDateTimeUTCOffset:  NULL, ActionDescription:  "Generic observation action generated by Excel Template for TimeSeries v.0.3.0-alpha", ActionFileLink:  NULL}
  - &ActionID0003 {ActionTypeCV:  "Observation", MethodObj: *MethodID0001, BeginDateTime:  "2010-06-03 11:15:00", BeginDateTimeUTCOffset:  -5, EndDateTime:  NULL, EndDateTimeUTCOffset:  NULL, ActionDescription:  "Generic observation action generated by Excel Template for TimeSeries v.0.3.0-alpha", ActionFileLink:  NULL}
FeatureActions:
  - &FeatureActionID0001 {SamplingFeatureObj:  *SamplingFeatureID0001, ActionObj:  *ActionID0001}
  - &FeatureActionID0002 {SamplingFeatureObj:  *SamplingFeatureID0001, ActionObj:  *ActionID0002}
  - &FeatureActionID0003 {SamplingFeatureObj:  *SamplingFeatureID0001, ActionObj:  *ActionID0003}
ActionBy:
  - {ActionObj:  *ActionID0001, AffiliationObj:  *AffiliationID0002, IsActionLead: TRUE, RoleDescription: NULL}
  - {ActionObj:  *ActionID0002, AffiliationObj:  *AffiliationID0002, IsActionLead: TRUE, RoleDescription: NULL}
  - {ActionObj:  *ActionID0003, AffiliationObj:  *AffiliationID0002, IsActionLead: TRUE, RoleDescription: NULL}

maybe the correction is as follows:

Actions:
  - &ActionID0001 {ActionTypeCV:  "Observation", MethodObj: *MethodID0001, BeginDateTime:  "2010-06-03 11:15:00", BeginDateTimeUTCOffset:  -5, EndDateTime:  NULL, EndDateTimeUTCOffset:  NULL, ActionDescription:  "Generic observation action generated by Excel Template for TimeSeries v.0.3.0-alpha", ActionFileLink:  NULL}
FeatureActions:
  - &FeatureActionID0001 {SamplingFeatureObj:  *SamplingFeatureID0001, ActionObj:  *ActionID0001}
ActionBy:
  - {ActionObj:  *ActionID0001, AffiliationObj:  *AffiliationID0002, IsActionLead: TRUE, RoleDescription: NULL}

Do I get misunderstood for this?

@horsburgh
Copy link
Member

@cdesyoun - This is a known issue with the current Excel template. It is technically correct and not duplicate data. I can have three separate actions - one for each of the results in the file. But, it would be better to have only one action that generated all three (as you suggest). @sreeder was working on this issue right before she left on maternity leave. She may be able to give us an update on where she got to with that.

@cdesyoun
Copy link
Author

In validation process, yoda tool does not check the duplicate records in yoda file. But, when loading yoda file into odm2 database, maybe these are in database if the duplication is not checked.

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