eCAPRIS

eCapris is the capital projects and information system for the City of Austin maintained by FSD (Financial Services Division)

Resources

• [e-mail]

  • Create a ticket for help or reaching developers to request new database views or updates to existing views

• Transportation Capital Project Financial Codes dataset https://data.austintexas.gov/Transportation-and-Mobility/Transportation-Capital-Project-Financial-Codes/jega-nqf6/data_preview

• Transportation Department Financial Codes dataset https://data.austintexas.gov/Transportation-and-Mobility/Transportation-Department-Financial-Codes/bgrt-2m2z/data_preview

eCapris Tech

• ColdFusion front end with some Java and Javascript

• Oracle database

  • Database views can query:

    • Data Warehouse

      • This is the preferred data source for integrations.

      • ~30 min behind data updates written to eCAPRIS database

      • Financial data like FDUs is current up to the EOB of the previous day

      • infoprod service name

      • See also https://github.com/cityofaustin/atd-finance-data

    • Source side

      • less latency

      • fsaprod service name

Moped to eCAPRIS

Summary

Adding funding sources from eCAPRIS data: Moped users can add an eCAPRIS subproject ID to a project. This unlocks the ability to add funding sources to the funding table from an open dataset (jega-nqf6) that can match funding sources to the subproject ID.

Creating new funding sources using Fund and Dept-unit dropdowns: Moped users can add a blank funding source row and populate the Fund and Dept-unit inputs using dropdown options provided by an open dataset (bgrt-2m2z)

Sync eCAPRIS statuses into Moped: Moped users can add an eCAPRIS subproject ID to a project. The Notes tab on a project has a switch that is disabled on projects without a subproject ID set. There is also a filter button that is disabled without a subproject ID set.

When a subproject id is added to a Moped project, the switch enables and can be toggled on or off. Toggling the switch on happens automatically when a subproject id is added to a project. Once the switch is toggled on, we have an ETL running in the background that queries the Moped project table and looks for projects that have should_sync_ecapris_statuses to true and also have an eCAPRIS subproject id stored on them. The ETL will then queries the FSD Data Warehouse for any new statuses for that id and add new rows to the ecapris_subproject_statuses table. These rows can be used by any projects that share the same eCAPRIS subproject id association.

eCAPRIS statuses are viewed in the same timeline as Moped status updates and internal notes. They also appear as the latest status update in the Moped dashboard, the project summary page, and in the AGOL components dataset if the syncing is toggled on.