codefortulsa / courtbot Goto Github PK

The courbot home page should have some instructions on how it works, etc.

When we send the initial subscription confirmation to a client, if we have already found a matching court case and it already has upcoming events, include information about the next event in the subscription confirmation message.

Something to the effect of 'We found you have an event on description: . We'll send you a reminder the day before for this and any upcoming events related to the case'

We need some admin pages to be able to edit users, review message queues.

(I'll admit to django-envy here)

Provide a form that captures the following information and saves that to the CourtbotDB

1. Case number
2. Client name
3. Client phone number (and other interested parties' phone numbers)

For several reporting and administration features to be used by the public defender's office, we want to categorize clients/parties into three groups:

1. Self-subscribing users
2. Clients of the public defender's office
3. Interested parties (such as family members of defendants)

Default courtbot allows clients to self-subscribe to notifications by texting the service with a case number. Courtbot then searches data from a csv file to find their case information.

To get this up and running for our purposes, we need to replace the loadData function that loads CSV data to point to OSCN data.

Add a daily email to users of the application informing them of any need-to-know information, in particular to ensure that the service doesn't fail silently.

Include any failed messages, failures to find events for clients and parties, and any other such fail conditions so that they can be addressed.

Talk to Jill to see how far in advance she would like text messages to be sent and how many she would like to have sent to them before she is notified that they have not confirmed they received the messages (see #17).

Determine how often follow-up messages should be sent for this scenario.

Ideas for future reminders:

1. Paying fines
2. Probation officer (on assignment?, meetings?)
3. DA fees
   4 DUI School (?)

For users who attempt to self-subscribe, if we find no events within the time to live timeframe, make sure to send them a message explaining this and allow them to resubscribe.

This needs to be sure to not send messages over correct conditions where there are no more upcoming events, such as closed cases.

Add documentation, including:

[ ] Specifications on Courtbot behavior
[ ] Specifications on Courtbot installation
[ ] Specifications on interface for public defenders' office

Need to have a message to the user that reminders are best effort and we are can't guarantee 100%

In particular, we want to record all events and be able to show the history of interactions and messages sent to clients.

Include a report that shows defendants whose court dates are coming up that did not confirm they received the text messages notifying them of their upcoming date (see #17).

Add ability to unsubscribe from courtbot messages.

Have reminders for defendants registered by a public defender (see #15) solicit a confirmation message that they have received the reminder.

Have follow-up text messages sent a number of times to be determined until confirmation is received.

Sending a non-case gets no reply. We should send back a request for a case and a link to more info.

1. Public transit information for getting to appointments and court date
2. List of employers
3. Payment gamification

• At least something to give them encouragement and show progress on paying down fines

Set up on Heroku
Set up on Techlahoma's Twilio account

Current code automates the creation of the intial method. We want public defenders to be able to add new clients.

I am looking at adding the passport-local library which means:

1. npm installing passport-local
2. creating routes for login
3. html pages for login
4. some simple method for admining the users

Add ability to select and receive messages in other languages.

The message I received had a link to OSCN but not the original case number. It would be helpful to have a link to the OSCN case information. This may not exist in all reminders.

Tulsa's courtbot will include interaction with public defenders.

Need to add jade or some other template engine to make this easier

Current message are ANC specific. We need a layer of abstraction for

1. Easier management of TUL specific messages
2. Make courtbot easier for other cities
3. First step toward localization

In order to make courtbot more court-system agnostic, allowing other cities to easily implement courtbot for their own use, create an interface for retrieving case data to be implemented in a separate solution.

The interface will have two operations:

1. Get all parties for a case number
2. Get all events for a party and case number

Ensure that implementers of this API return court date information in ascending order and exclude past events.