Centralized data.accdb: Difference between revisions
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
Data Repository containing | Data Repository containing a de-identified copy of all data sent. De-identified by excluding chart, phin, names, and by using only month and year of birth. | ||
== How does data get into Centralized data.mdb == | == How does data get into Centralized data.mdb == | ||
Revision as of 10:46, 29 August 2013
Data Repository containing a de-identified copy of all data sent. De-identified by excluding chart, phin, names, and by using only month and year of birth.
How does data get into Centralized data.mdb
version 2012-12-21 implemented sending of data to Centralized_data.mdb.
This is accomplished by queries run at sending time. See sub send_data() for details.
Finding and fixing Errors
Will need to implement tools in centralized_data.mdb to help Pagasa with error checking. All data will be checked. Pagasa will correct "sent" data, for incomplete data she will notify collector. Doing that should probably be facilitated. Possibly in the future we can have a mechanism where Pagasa can just "reject" data that is bad, and where it will be sent back to collectors, either at n&b time, start time, or send time... needs to be thought about. Template:Question IT
Dependencies
TISS28 Data.mdb pulls data from Centralized data.mdb.