Within the Case Management System (CMS) ecosystem, Digital Recording supports the capture of court proceedings through hardware or software-based means in a digitally encoded format. This digital format is then preserved on an electronic storage device with links to the cases recording. A user can play back the recording through a decoding process.
- An interface to control a recording session from an external component
- The control functions need to include basic control functions (initiate/start, pause, stop, request current status)
- The control functions should also allow external control and/or passthrough commands to the AV equipment being used to capture the record for actions like muting (attorney-client or attorney-judge conversations) as well as signage notifications (for in-room alerting of recording status)
- Contains the ability to inherit limited properties of (or be a child of) another object in the system through an identifier passed from the external component (use case: recording session for a case in Case Manager)
- This includes both the ability to store the external identifier as well as provide a unique identifier for the recording session to the external component
- Provides an interface to access digital recording file(s) from another component. This would be for reference, metadata, publishing/copying, or playback purposes
- This interface assumes that the default state for access (network, direct, or other) can only be done through the interface. This allows other components to affect/control/limit this access as needed (security, permissions, user control, case management, sealed cases, etc.)
- An ability to access general metadata about the recording including, but not limited to: recording filename(s), recording length, recording format, channel information
- Also, with the ability that external components (like search from a case manager) can search this meta data as needed through a search interface
- Recording filenames should be available in a common format. Therefore, the interface should have the ability to translate filenames into the common format for any instance where a different file naming structure is used inside the digital recording solution
- Trigger/call to operator when specific events occur
- These events to include when recording failures are detected (to the limit of the ability of the solution to detect failures)
- These events to also include when recording control functions occur (is started, stopped, or paused)
- Provides an interface for confidence monitoring of the recorded file as it is being written
- This interface provides the same functions as provided for playback of a previously recorded session
- Provides the ability to purge recordings based on user action or court rule (e.g., delete all recordings for XX case type after YY period of time)