samarthtambad / blockchain-for-law-enforcement Goto Github PK

handle the case when:

1. registerCase is invoked when a case with same ID is already registered
2. addSuspectToCase is invoked when there is already a suspect added with same suspect ID

given a case number and suspect id, make suspect not active

given a case number, get all relevant information for that case

given a case number and suspect id, get all information for that suspect

given a case number and suspect id, retrieve status of the suspect

handle add evidence to suspect when no suspects added yet.

Add test transaction to save data (JSON) to state database and update test query to return JSON response. Parse the response.

given a case number, get all currently active suspects for that case

support for JSON based rich queries over key-value pairs provided by levelDB (default)

given a case number and suspect id, add evidence found against a particular suspect

create a user interface that supports:

1. User login
2. View list of cases
3. Invoking new chaincode transactions
4. Query via buttons, etc.

for each transaction, handle the case when record not found.

a case could have multiple suspects, add suspect (with a unique id) to a list of suspects for a given case number

For updating a suspect in a case, the entire case needs to be updated. This kind of design could lead to inefficient update as case size grows.

CreatedAt: time.Now() is causing error: [Channel.js]: compareProposalResponseResults - read/writes result sets do not match index=1

Don't use time.now() in the chaincode, find another way.

given a case number, add evidence found with respect to a case but not necessarily against a suspect

create application server and API to be able to run middleware scripts (indirectly invoke chaincode transactions) using curl commands to the server.

add the middleware api code to support curl commands.

register a case with a unique case number