TMP dates imported backwards: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m cat |
Ttenbergen (talk | contribs) m Text replacement - "Category:All Legacy Projects" to "Category:Legacy project data" |
||
| (One intermediate revision by the same user not shown) | |||
| Line 14: | Line 14: | ||
== Plan == | == Plan == | ||
* link [[TmpV2 1.mdb]] table '''' into [[Centralized data front end. | * link [[TmpV2 1.mdb]] table '''' into [[Centralized data front end.accdb]] | ||
* confirm a record exists in TmpV2 for each entry in centralized and vice versa | * confirm a record exists in TmpV2 for each entry in centralized and vice versa | ||
** query '''' | ** query '''' | ||
| Line 23: | Line 23: | ||
Storing here for future reference as it will be removed from front end once done. | Storing here for future reference as it will be removed from front end once done. | ||
[[Category: | [[Category:Legacy project data]] | ||
Latest revision as of 00:22, 3 January 2019
will be addressed by Re-import of TmpV2 data from Julie's Export 2014-09-08
When we imported the TMP date var day and month got switched around for some, i.e. instead of April 1 it will be imported as January 4.
Pagasa has continued to keep tmpV2_1.mdb up to date so we can get proper values from there.
Solution
We will update the values in centralized_data.mdb with the proper values from TmpV2 1.mdb.
Spun this out into its own article since it will be a bulk update from query and we should have a record of what we did if we later find that anything went weird.
Plan
- link TmpV2 1.mdb table ' into Centralized data front end.accdb
- confirm a record exists in TmpV2 for each entry in centralized and vice versa
- query '
- query '
- run query fix_tmp_dates to update centralized from TmpV2
SQL for query fix_tmp_dates
Storing here for future reference as it will be removed from front end once done.