thanks for taking the time to review this! I currently have a test site developed, consisting of an auth, menu, several forms, and a MySQL backend. I will provide the url if you're interested.
It is setup locally as there are about 9 small locations that have staff at them who need to log in and enter information. There is an authentication by physical location, and staff is entered and tracked through the session. Staff can only update information related to their physical location (center).
Once into the system, if you were the user your main function is to create a client intake - this is an incident report that they file to track and provide support for victims of sexual abuse, and is the primary object in the system. There is a lot of information on this form and are currently working to put it into different tabs on the same page to make it look better.
What I need to do first is take the client intake link and have that go to a different form where you choose new or existing client, and if it is an existing client you can search by last name/first name, select client from a list, and continue onto the intake form. A client may be associated with multiple incidents, so to save the user time and maintain integrity, we need to be able to pick a client from the list if we are creating an incident report for a client we have already gathered information from.
1. Split client intake - have user choose new or existing client before entering the intake form. If they choose an existing client, that client's information is stored in the session and used to populate the fields on the intake form that are related to the client. Should be traditional search feature that allows user to search for client by last name (required) and first name (optional).
Once the intake form is filled out, you currently click submit and are transfered to the service log entry, which is currently a one page form to add one service log. A service log is a line item record of a service that the user is providing to the victim - generally some sort of social service. What I need is to have a button to "add service log" to the client intake, which will open a new window with an inline formset ([url removed, login to view]). The intake->service log relationship is one-to-many, so the user should be able to add multiple service log entries from this one form without leaving that page. When they finish, the information will be stored in the session and that window will close (if it's not possible to do this in a new window, we can use the existing one, the more important part is the inline form that allows for multiple service log entries).
2. Update service log to represent the one-to-many relationship between client intake and service log as an inline formset that can add multiple rows (records) in one attempt and associate them to the intake record.
Finally, the support group model has changed a little in that it can be added as a service in the service log. So, if a support group exists, the user should be able to add this as a service log record on the "add service log" page. The model should change accordingly. Also, most of the current fields in the support group model should be calculated, not stored (anything related to client demographics should be determined by the clients associated with this support group via the intake service log, not stored in the DB)
3. Implement Support group as a type of service that can be added as a line item in the service log form, model updated as needed.
This needs to be done in the next 36 hours. I will send more info if you are interested.