bricestacey / foresters Goto Github PK

A scenario may exist as follows:

Person A clicks edit for a resource
Person B clicks edit for the same resource
Person A updates the resource
Person B updates the resource

Person B's changes would effectively wipe out the changes made by A.

Should kick off sphinx index

Whatever this means.

Export data to CSV. This can be a straight mapping of DB.

If the system is slow and the user hits “enter” a second time, a dupe record is created and needs to be deleted.

Users trying to add new courts after 1935 and there is no way for users to set the court id. It's just auto-generated.

They are checking to be sure none are reused. If so, will need to migrate the id to a different column.

You can get rid of the zipcode field on the data entry screen. State is still necessary as there are a few out of state records.

The year should be a text box because it would be too hard to scroll through 70-100 years.

For easy navigation

Add error if there exists a date missing less granular term in comparison to what exists.

For example, if the day is set, the month and year must also be set.