Tick lists about localcragapp

[dorthrithil]

I also plan to add an "FA" field. When this is filled, the FA info in the line model is overridden and the user detail page can be clicked on the name etc.

[PeterGrabowitz]

• Maybe allow for some "multi tick" option with the view of a sector spot (Bereich) if not too much work. Would not only be relevant for starting a scorecard and adding older ascents but quite regularly also after a normal crag visit when you´ve done 10 or more lines. Possible solution: When clicking "Linien ticken" from that view, the display changes to the following one:
  
  Relevant questions involve whether the grade and the rating should be preset to the "official" ones or whether users should have to chose them themselves completely. Probaly preset the grade, but not the rating. Preset the current date.

• Allow for ticking boulders from the line view, the topo picture view and the specific line view. Question whether that collides design wise with the multi tick feature.

• Allow for ticking flashs, but don´t count them differently pointwise for the rankings

• Allow for not providing a date for an ascent or only providing a year. Allow for specific days for personal log keeping but don´t really use them in statistics unless necessary. Unless that becomes a problem with the multi tick feature?

[dorthrithil]

1. I won't do multi-tick for now. Mainly because of the work overload compared to the use. It's only a real usecase for our few users where we have to tick a few hundred lines all at once. Later on it's fine to just click like 1-10 times, depending on your session. I also want to add a comment function in the ticking process which will be hard ux-wise when looking at multi tick functionality.
2. Yes, this will be possible form everywhere
3. Jep
4. Yes, I want to provide the options "year", "date" and "None" for the date.

[PeterGrabowitz]

Great!

A remark regarding use case of multi tick: Not sure whether this isn´t actually a pretty common case for any instance. Most users in the Eifel will have done lots of stuff before, same is true for any other instance created for a different region. It might be a not too trivial obstacle in adopting the scorecard by users. That was my idea behind it and not mainly to ease the workload for "us".

Of course it still stays a "very nice to have feature" and not an entirely separate feature that stands on its own when using the site. Hence the workload is a giant factor of course.