MES Curator startup behavior

When the MES Curator is started for the very first time, it performs the following actions on those types with a polling frequency > 0.

• All reference data (the datatype whose staging_type_config.is_reference_type = 1) from the MES production database will be curated and staged in the staging table, as long as those reference data are created after the year 2000.

• Events (the datatype whose staging_type_config.is_reference_type = 0) that are created within last 5 days from the current UTC time will be curated from the MES production database and staged in the staging table.

• The staging_curator_status.curate_reference_data flag is turned on by default, so that data is curated automatically by the MES Curator. Once the data is curated, the MES Curator service automatically turns off this flag.

• Updates staging_curator_status table with the service host name, user, and execution time.

When the MES Curator is subsequently started, it will perform the following actions:

• All reference data (the datatype whose staging_type_config.is_reference_type = 1) from where they are last left off from the MES production database will be curated and staged in the staging table.

• All events data (the datatype whose staging_type_config.is_reference_type = 0) from where they are last left off from the MES production database will be curated and staged in the staging table. If the last left off datetime is older than 5 days in the past, then the events are limited to last 5 days in the past from the current time.

  Note: For a datatype, if the number of records in the MES production database exceed the configured curation limit, then those production records are curated in multiple pages, and staged to the staging table in groups.