Feedback on 9/14 version

[emilyeros]

Worked well

• Overall impression: really good, handles the cases I needed
• Clever autocomplete on "regulation template" field was helpful for pulling up previously-used template names
• Copy + paste ability for populating multiple regulation template names at once
• Linked tables are a fantastic solution to the nested lists issue
• Timing is fixed and I like the built-in color-coded validation

Didn't work well or broke expected behavior

• Didn't find anything that I'd put in this category

Might confuse people, worth clarifying in docs

• I found myself looking for a save button to apply changes to a template, then realized everything I was doing would cascade immediately. Not a problem, just something I didn't necessarily intuit.
• Potential to modify previous templates without realizing it. Because the "regulation template" field in the first table only holds one template, we can't stack a handful of templates like how signs are stacked in real life. For example, I can't combine a "paid parking" template with a "motorcycles only" template. Or let's say I have metered handicap parking. I pull up the previous template for handicap parking, and add payment info. I don't realize that I've modified all other handicap parking to include payment terms. The same thing could happen to timespans. People may fuss with these without realizing it.

We could address this through documentation/training. We could also allow for multiple templates to be listed... but I don't think that's desirable. I'm curious if there's also a lightweight way to address it in the digitizer. Maybe highlight all the items that get changed when a modification is made? Or when a template is recycled for the first time, pull up the fields in the regulation table and add a comment saying, "Warning, any changes made to this template will apply to all other [or calculate the actual # of] curb features using the template". This comment/potential approach applies to timespan table.

Minor tweaks, will leave to your discretion

• Can userclasses use a clever autocomplete of suggested values? This is an area where we're going to see typos and inconsistencies between jurisdictions.
• It's possible to include a fragment of a regulation, like a few stray characters as a typo on a new regulation line. This is likely a validation issue. It may be beyond the scope of this version, but if there are lightweight ways to prevent it then that may help (e.g. flag or even clear all individual regulations that lack an activity property)

Stuff left to add, didn't include any comments about.

• Timespans beyond weekdays and hours (includes dates, event names ("snow emergencies"), "second monday of the month" iterations)
• Payment rates. We can do a lightweight version of this that covers most cases but doesn't require yet another nested table for payment timespans... happy to chat about that.
• Curblr/asset exports
• user-friendly terminology, possibly tooltips on hover-over for explanation of certain fields (if helpful, I can take a pass at this once everything is in there)