Difference between revisions of "Logging and Tracking"
(→The Event records) |
|||
| Line 18: | Line 18: | ||
Used in all phases of processing to know what tables to expect to find / process in each database<br/> | Used in all phases of processing to know what tables to expect to find / process in each database<br/> | ||
| − | ===The | + | ===The event records=== |
The events tables and types<br/> | The events tables and types<br/> | ||
Creating and filling event records<br/> | Creating and filling event records<br/> | ||
Revision as of 23:51, 2 November 2020
Contents
The need for logging and tracking
Separate components, all need to refer to a common 'map' of the status of the system
makes it easier to see what is happening for system, what has happened for users
Therefore, records of each of the 4 main processes, map of data package statuses, logging of issues
The source data tables
The source data tables
<< diagram of tables>>
study-study links (??? - in nk surely)
logging data layer - the logging repo
standard functions for doing the tracking
The source parameters
Holds a central position
Sources are orgs so that the original records for each source are in the contexts organisation table
That gives the ids
But processing specific data is in this table
Used in all phases of processing to know what tables to expect to find / process in each database
The event records
The events tables and types
Creating and filling event records
statistics linked to aggregation
Extraction notes
Purpose and usage
Extraction tables
feedback and notes, serialising feedback
