Thanks for this, Bill!

I'd suggest starting with a very bare-bones MVP and seeing what feedback we get from our volunteer. One concern I have is that she'll find a lot of ways to input data we've never imagined, but I'm not terribly concerned about the UX being really good, honestly.

For documentation, I think the Wiki is probably the right spot?

I put this on Kevin's backlog, but I leave to y'all to prioritize.

I think the first thing we need to do is define what fields are going to be required for each court, this will allow us to see if we only need to add a few more fields to CourtUploadForm and restrict what fields are seen based on the court_id.

Regarding how to upload the opinions, the page could be similar to tennworkcompcl page where you click on a court button and it takes you to an independent page to upload the file using a static page where you will only see the specific fields.

If you think about this further into the future, we should probably divide the forms by state or something similar. Although this would complicate other things.

Just to avoid diffuse responsibility, I'd like to duck out of this one and let you guys come up with a plan/design that you like. Doesn't have to be perfect on the first go — just needs to be functional for a motivated engineer or volunteer. Thank you both!