DRISTI
  • 👋Welcome to DRISTI
    • Why DRISTI?
  • ⚖️About DRISTI
    • Overview
    • Design Principles
    • Value Proposition
    • Architecture Overview
    • System Users
    • Key Modules
      • Async Applications & Submissions
        • Key Features
        • Process & Workflows
        • Specifications
      • Case Management
        • Key Features
        • Process & Workflows
        • Specifications
      • E-Filling, Scrutiny and Admission
        • Key Features
        • Process & Workflows
        • Specifications
        • Sequence Diagrams
      • Evidence
        • Key Features
        • Process & Workflows
        • Specifications
      • Listing & Scheduling
        • Key Features
        • Process & Workflows
        • Specifications
      • Hearings
        • Key Features
        • Process & Workflows
        • Specifications
      • Orders & Tasks
        • Key Features
        • Process & Workflows
        • Specifications
      • Summons, Bails, Warrants
        • Key Features
        • Process & Workflows
        • Specifications
      • User Benefits
      • User Registration
        • Key Features
        • Process & Workflows
        • Specifications
        • Sequence Diagrams
      • Roles per Module
    • API Specifications
    • Security
    • Privacy
  • 🧰DRISTI Platform
    • Architecture
      • Overview
      • Principles
      • High Level Design
        • Technology Stack
        • Access Control & Roles
        • Data & Analytics
        • Non Functional Requirements
          • Performance
          • Security
          • Data Retention
        • Logging Guidelines
      • Low Level Design
        • Advocate
          • Advocate - API Specifications
          • Sequence Diagram
        • Application
          • Application - API Specifications
          • Sequence Diagram
        • Case
          • Case - API Specifications
          • Sequence Diagram
        • Case Management
          • Case Management - API Specifications
          • Sequence Diagram
        • Evidence
          • Evidence - API Specifications
          • Sequence Diagram
        • Hearing
          • Hearing - API Specifications
          • Sequence Diagram
        • Order
          • Order - API Specifications
          • Sequence Diagram
        • Task
          • Task - API Specifications
          • Sequence Diagram
          • Summons
          • Warrant
      • Architectural and Design Decisions
        • Data Visibility
        • Detailed Case Access
        • Case Numbering
          • Filing Number
          • Court Case Number
          • CNR Number
          • Case Stages, Numbers & Dates
    • Interoperability
    • Release Notes
      • Release 1.1.0
      • Release 1.2.0
      • Release 1.3.0
      • Release 1.4.0
      • Release 1.5.0
      • Release 1.6.0
    • Hotfixes
      • Hotfix Release 17.3
      • Hotfix Release 18.1
      • Hotfix Release 18.2
      • Hotfix Release 18.3
      • Hotfix Release 18.4
      • Hotfix Release 19.1
      • Hotfix Release 19.2
      • Hotfix Release 19.3
      • Hotfix Release 20.1
      • Hotfix Release 20.2
      • Hotfixes Release 20.3
  • 🪝Setup
    • Planning DRISTI Implementation
    • Establish Project & Team
    • Gather Requirements
    • Installation
      • Infrastructure Setup
        • Azure Setup
        • SDC - OpenShift Setup
      • Code Deployment
      • Configuration
        • Functional Configuration
        • Service Configuration
          • Court
            • Court UI
          • Case
            • Case UI
          • Advocate
            • Advocate UI
          • Application
            • Application UI
          • Task
            • Task UI
          • Order
            • Order UI
          • Hearing
            • Hearing UI
          • Evidence
            • Evidence UI
    • Quality Assurance Testing
    • Go Live
    • Operational Support
    • Monitoring
  • 🛣️Roadmap & Updates
    • Roadmap
  • 🌾Resources
    • Source Code
    • Technology Stack
    • Licensing
    • Legal Taxonomy
  • 🌐COMMUNITY
    • Interested in Contributing?
    • Github Discussion
    • Code of Conduct
  • 🪝Setup
    • Coming soon...
    • 🟢ABOUT US
Powered by GitBook
On this page
  • Overview
  • Workflow
  • Actions
  1. DRISTI Platform
  2. Architecture
  3. Low Level Design

Evidence

PreviousSequence DiagramNextEvidence - API Specifications

Last updated 4 months ago

Overview

The Evidence registry and Service is designed to manage the submission, storage, retrieval, and handling of documents in judicial proceedings. This ensures that all documents related to a case are securely managed, accurately documented, and easily accessible to authorized users, thereby supporting the integrity and fairness of the legal process.

The repository is used for storing all types of documents, including digital files, photographs, videos, and documents. Each piece of document is catalogued with a unique identifier, type and subtype ensuring that it can be accurately referenced and retrieved whenever needed. Further, certain documents can be tagged as evidence for a case.

Potential uses of this service include:

  1. Secure Submission of Digital Evidence: A law enforcement agency needs to submit digital evidence, such as surveillance footage or forensic reports, to be used in a court case. The agency integrates with the Evidence API to securely upload digital evidence directly into the judicial system. The API validates the evidence, assigns it a unique identifier, and links it to the relevant case. This process ensures that the evidence is securely stored and readily available for review by authorised legal professionals.

  2. Evidence Retrieval for Case Review: An advocate preparing for a trial needs to review all evidence related to their case, including documents, photographs, and videos. The advocate uses the Evidence API to retrieve all relevant evidence linked to the case. The API ensures that only authorised users can access the evidence, protecting sensitive information while providing the advocate with the materials they need to build their case. This streamlined access to evidence helps legal professionals work more efficiently and effectively.

  3. Integration with Forensic Analysis Tools: A forensic analysis service needs to process digital evidence, such as analysing video footage or extracting data from electronic devices, and then submit the findings back into the judicial system. The forensic analysis service integrates with the Evidence API to retrieve raw evidence for analysis and then submit the processed results back into the system. The API ensures that the analysis is linked to the original evidence and the corresponding case, providing a clear and traceable record of the forensic process. This integration helps to ensure that forensic evidence is handled with the utmost care and accuracy.

  4. Evidence-Based Monitoring and Research: A research organisation is studying patterns in criminal evidence, such as the use of certain types of evidence in successful prosecutions or the prevalence of digital evidence in recent cases. The research organisation uses the Evidence API to access anonymised data related to evidence across multiple cases. The API provides them with the tools to analyse trends, generate reports, and conduct studies on the effectiveness of different types of evidence. This research can provide valuable insights into the judicial process and help to improve legal practices over time.

Workflow

Actions

  • Create (/v1/_create): Creates a new piece of evidence, requiring details like tenant ID, case ID, filing number, evidence number, media type, evidence type, source type, and the creation date.

  • Update (/v1/_update): Updates an existing piece of evidence with similar details as the create operation.

  • Search (/v1/_search): Allows searching for evidence-based on various criteria, such as tenant ID, case ID, filing number, evidence number, media type, evidence type, source type, and creation date.

  • Add Comment (/v1/addComment): Adds a comment to an existing piece of evidence, requiring the tenant ID, case ID, evidence ID, and the comment text.

🧰
Evidence - API Specifications
dristi/docs/evidence/workflow/workflowConfig.json at main · pucardotorg/dristiGitHub
Logo