| |
1394 - Migrate JABS from EDR Producer to EDR Consumer Database
|
|
| Request Status Summary |
| Request Status |
Awaiting Analysis |
|
| Request Detail |
| Requestor Name: |
| |
Kumar, Mahesh |
| Origination Date: |
| |
05/05/2025 |
| |
|
|
Recommended Endorser:
|
| |
AOC (endorses for other communities) |
|
| Request Type: |
Change or Enhancement
|
| Which Systems are affected? |
Judicial Access Browser System (JABS)
Other
|
| Other affected Systems / Business Processes |
EDR |
| Business Area: |
Other
|
| Communities Impacted: |
AOC
Supreme Court Clerks
Appellate Court Judges
Appellate Court Clerks
Superior Court Judges
County Clerks
Superior Court Administrators
CLJ Judges
CLJ Managers
Family and Juvenile Law Judges
Juvenile Court Administrators
State Agencies
|
| Impact if not Resolved: |
High |
| Impact Description: |
|
It is crucial that all the consuming applications that are still integrated with EDR Producer be modified to use EDR Consumer. Failing to do so will jeopardize the technical viability of the EDR as a repository of data for both data producers and data consumers, now and into the future. Moving to EDRSDW will make all the necessary adjustments to enable us to support the sustainability, operability and maintainability of the EDR system, especially as additional data producers are on-boarded. As JABS is the most used consuming application, it is recommended that it should be the first consuming application to be modified to use EDR Consumer (EDRSDW) instead of EDR Producer.
|
|
|
| What is the Business Problem or Opportunity |
|
The optimum architecture for the EDR is to separate data writing activity from data consuming activities. The problems mentioned above could be avoided if all consumer applications sourced their data from EDR Consumer (EDRSDW) database. A consuming database is designed for more efficient reading of data. It uses a highly de-normalized, 'read optimized' structure which reduces the number of tables used, leading to simpler queries and quicker access to information. Also, the Data Processing component translates 'Source' data from courts into statewide 'standard' data while loading the EDR Consumer table. This removes the need for the consuming applications to do the translations themselves, in their complex queries and stored procedures. Applications may use shared standard queries and validated, already populated data, ensuring data quality and consistency across applications.
JABS application uses 39 stored procedures in EDRJabs schema. These are exclusively built for JABS use. It also uses stored procedures in EDR Reference schema that are shared between applications. There are 264 non-unique references to EDR Reference objects in the JABS codebase that would also need to be addressed. These will potentially be replaced by APIs that will return data from EDRSDW using standardized queries.
|
| Expected Benefit: |
|
Producer performance will improve as consuming application queries will no longer conflict with the data transferred by onboarded courts. Because Producer and Consumer are decoupled, changes to either will be possible with less effort and impact. Maintenance and/or migration downtime for Producer will be reduced, as applications may continue to use Consumer even if Producer is temporarily inaccessible.
JABS is one of the consumers of EDR data. It is a web application for looking up the details of a specific case, or all cases involving a particular person. County clerks, Judges, and Law enforcement agencies are among some of the prominent users of JABS. JABS should be modified to get onboarded court data from EDR Consumer instead of EDR Producer database. This will ensure JABS is consuming clean, validated, and historic EDR data.
|
| Any Additional Information: |
|
None
|
| Endorsement Detail
|
| Endorsing Committee |
| |
AOC (endorses for other communities) |
| Endorser Name: |
| |
Escudero, Arsenio on behalf of AOC Endorsement Group |
| Origination Date: |
| |
05/16/2025 |
|
| Endorsing Action: |
Endorsed |
|
|
|
|
