DI-009 Data Integration - Transformation Transformations shall have the ability to re-start from point of last success A restart of a transformation occurs from the last know completed record/operation instead of from the beginning. DI-010 Data Integration - Transformation Transformations shall communicate and submit data through the EDR Data Services Transformation destinations shall be the EDR Data Services. DI-011 Data Integration - Transformation Transformations shall maintain a log indicating execution Date/Time, number and type of records submitted, number and type of records accepted, number and type of records rejected, elapsed of execution Transformation logs contain Date/Time, number and type of records submitted, number and type of records DI-012 Data Integration - Transformation Transformations shall be scalable, harnessing the power of multiple processors when needed, releasing when not needed Transformations make use of available multiple processors DI-013 Data Integration - Transformation Transformation shall provide configurable deployment options Configuration files over-ride design time values at deployment DI-014 Data Integration - Monitor/Schedule The scheduling component shall be able to support multiple schedules A transformation has multiple run schedules DI-015 Data Integration - Monitor/Schedule A single Schedule shall have the ability to be applied to multiple transformation jobs Two or more jobs share the same named schedule DI-016 Data Integration - Monitor/Schedule Scheduled jobs must be able to enable and/or execute other jobs A scheduled job starts another job DI-017 Data Integration - Court Migration Data from migrating court must be extracted from the ODS into a Migration Database in SQL Server A migration database exists and contains data received from the ODS DI-018 Data Integration - Court Migration Data must be in the exact same format and structure as JIS, with no transformations. Table structures and definitions in the migration database are identical to those from the ODS
DI-019 Data Integration - Court Migration The extraction queries must be able to be re-usable, allowing the migrating court to perform any data fixes that may be required multiple times Queries do not have to be re-written between passes DI-020 Data Integration - Court Migration Data cannot change until all data for a court has been migrated End user applications are turned off during the migration and aren't turned back on until migration is complete DI-021 Data Integration - Court Migration The migration database must be transferred to the local court for their local conversion The local court has a complete copy of the migration database. DI-022 Data Integration - Ongoing Updates Transactional replication shall be used to update the ODS The ODS is updated by transactional replication DI-024 Data Integration - Ongoing Updates Delete triggers shall be added to any new table added to the ODS Delete triggers exist on each table DI-025 Data Integration - Ongoing Updates The delete triggers shall mirror the functionality of the other ODS Tables. Delete triggers perform the same function as the other delete triggers DI-026 Data Integration - Purge Data stored in the migration database shall be the source for purging data from JIS Purge scripts grab data from the migration databases to determine which data in JIS to purge DI-027 Data Integration - Purge Data stored in the migration database shall remain as a source for recovery of purged data. Once migration is complete, the migration database is set to read only mode and kept available if needed for reversal of the purge DI-028 Data Integration - Purge Purge of migrated data must be done after converting court is done performing their conversion and sending "do not purge" records Only records that are not marked as "do not purge" will be purged from JIS and subsequently the EDR.
DI-039 Data Integration - Court Migration Post migration, if it is determined that the migration was not successful, the AOC Migration database shall be used to re-insert previously purged records. The JIS Database and the EDR are back to the state prior to migration DI-040 Data Integration - Transformation Transformations shall only pull data that has been added or updated since the last transformation execution Transformations use the date and time recorded in the log from the previous pull. DI-041 Data Integration - Transformation Transformations shall record the start time of the transformation The start time is recorded in the transformation log DI-042 Data Integration - Transformation Transformations shall log current status of execution (i.e. started, loading, complete with no exceptions, complete with exceptions, etc.) A review of the log throughout the execution of the transformations show what operations have completed and which ones are currently running. DI-043 Data Integration - Staging The staging area must be able to identify deleted records and retain for possible re-insertion. Records deleted at the source are present in the corresponding ZDEL table.
CRX – WHERE CRX_CRT_ITL_NU IN (…) CS – WHERE CS_CRT_ITL_NU IN (…) CSC – WHERE CSC_CRT_ITL_NU IN (…) CSG – NO FILTER CSU – WHERE CSU_CRT_ITL_NU IN (…) CTC – NO FILTER CTX – WHERE CTX_CRT_ITL_NU IN (…) CUD – WHERE CUD_CRT_ITL_NU IN (…) CUW – WHERE CUW_CRT_ITL_NU IN (…) CVC – NO FILTER CVO – NO FILTER CVP – NO FILTER CVS – NO FILTER CVW – WHERE CVW_CRT_ITL_NU IN (…) DCM – WHERE DCM_CRT_ITL_NU IN (…) DFJ - – WHERE DFJ_CRT_ITL_NU IN (…) DII – WHERE DII_CRT_ITL_NU IN (…) DIN – WHERE DIN_CRT_ITL_NU IN (…) DKC – NO FILTER DKT – WHERE DKT_CRT_ITL_NU IN (…) DT – NO FILTER DVO – WHERE DVO_CRT_ITL_NU IN (…) DVP – WHERE DVP_CRT_ITL_NU IN (…) EML – NO FILTER FCA – WHERE FCA_CRT_ITL_NU IN (…) FCN – WHERE FCN_CRT_ITL_NU IN (…) FWO – WHERE FWO_CRT_ITL_NU IN (…) GRN – WHERE GRN_CRT_ITL_NU IN (…) ICH – NO FILTER INF – WHERE INF_CRT_ITL_NU IN (…) ISS – WHERE ISS_CRT_ITL_NU IN (…) INV – NO FILTER IVT – WHERE INF_CRT_ITL_NU IN (…)
JNE – WHERE JNE_CRT_ITL_NU IN (…) JRT – WHERE JRT_CRT_ITL_NU IN (…) JSA – WHERE INF_CRT_ITL_NU IN (…) JTC – NO FILTER JVO – WHERE JVO_CRT_ITL_NU IN (…) JVP – NO FILTER LAW – NO FILTER LOC – NO FILTER MCF – WHERE MCF_CRT_ITL_NU IN (…) NCC – WHERE NCC_CRT_ITL_NU IN (…) NCJ – WHERE NCJ_CRT_ITL_NU IN (…) OAN – NO FILTER OAT – WHERE OAT_CRT_ITL_NU IN (…) OFL – NO FILTER OOT – NO FILTER ORA – NO FILTER ORG – NO FILTER PAD – NO FILTER PAR – WHERE PAR_CRT_ITL_NU IN (…) PCM – NO FILTER PCT – WHERE PCT_CRT_ITL_NU IN (…) PDN – NO FILTER PEM – NO FILTER PER – NO FILTER PHI – WHERE PHI_CRT_ITL_NU IN (…) PHN – NO FILTER PHP – NO FILTER PHS – WHERE PHS_CRT_ITL_NU IN (…) PIN – NO FILTER PKC – WHERE PKC_CRT_ITL_NU IN (…) PKI – WHERE PKI_CRT_ITL_NU IN (…) PML – WHERE PML_CRT_ITL_NU IN (…)
PNH – NO FILTER PNP – WHERE PNP_CRT_ITL_NU IN (…) PPH – NO FILTER PPN – WHERE PPN_CRT_ITL_NU IN (…) PPR – WHERE PPR_CRT_ITL_NU IN (…) PRC – WHERE PRC_CRT_ITL_NU IN (…) PRG – NO FILTER PRK – WHERE PRK_CRT_ITL_NU IN (…) PRX – NO FILTER PSH – WHERE PSH_CRT_ITL_NU IN (…) PSX – WHERE PSX_CRT_ITL_NU IN (…) PTD – WHERE PTD_CRT_ITL_NU IN (…) PTE – WHERE PTE_CRT_ITL_NU IN (…) RCU – NO FILTER RDS – WHERE RDS_CRT_ITL_NU IN (…) RES – WHERE RES_CRT_ITL_NU IN (…) RG – NO FILTER RIX – WHERE RIX_CRT_ITL_NU IN (…) RLN – NO FILTER RLX – NO FILTER TCR – WHERE TCR_CRT_ITL_NU IN (…) TPA – WHERE TPA_CRT_ITL_NU IN (…) TSL – NO FILTER UCP – WHERE UCP_CRT_ITL_NU IN (…) UTR – WHERE UTR_CRT_ITL_NU IN (…) VEL – NO FILTER VVC – NO FILTER VXR – WHERE VXR_CRT_ITL_NU IN (…) WJR – WHERE WJR_CRT_ITL_NU IN (…)