theCrag / website

theCrag.com: Add your voice and help guide the development of the world's largest collaborative rock climbing & bouldering platform
https://www.thecrag.com/
109 stars 8 forks source link

Better logging of artifical ascents #1319

Open birgander2 opened 10 years ago

birgander2 commented 10 years ago

As now, thecrag is not really usable to track your "indoor performance" (well, this might not be its main purpose...): Usually, routes in gyms are generic, i.e. there is only a single "grade 20 route", "grade 21 route", etc. in the database, even though there are more than one of those existing in that gym. Consequently, they can be ticked only once and the resulting statistics get wrong / biased. Exampe: You climb 10 different grade 30 routes, one of grade 25 and one of grade 20 - your general performance will be 25 only...

A solution could be to change the calculation of artifical ascents to count each ascent individually, or to add a button in the ticking process indicating that this ascent was not a repeat.

scd commented 10 years ago

Well spotted.

However I am in two minds about the generic gym. We have made about a dozen generic gyms in Australia and had very little activity. As you have pointed out there are some deficiencies with our implementation, however I would have thought there would be more activity if this was a desired feature.

My guess is that logging gym ascents is a totally different category of user so this is why the feature is under utilized. I think the next step is to work with a gym to get a non-generic solution and better UI so we can attract the gym user.

birgander2 commented 10 years ago

I agree that gym ascents is a totally different category and probably such a feature is really not important. But I doubt that a non-generic gym is possible: At least in the gyms I visit, the route settings are changed every few months. With the current solution it is not astonishing that activity is low, so probably consider a simple and quick intermediate solution (before finding a better concept)?

scd commented 10 years ago

BTW the repeat flag is a request feature elsewhere and is tied up with some other issues. It will be a while before I get onto this either way.

Mdemaillard commented 4 years ago

I think the standard logging for Gym should stay, but the interface improved to keep gym routes up-to-date. To that effect, 2 new features are required:

That way an easy process would be:

  1. duplicate whatever is required
  2. Archive whatever is obsolete
  3. Tick as standard
scd commented 4 years ago

We have just done some new edit route improvements for gyms. At the gym level you can set a gym edit filter which restricts the fields presented on the route form when creating routes. We have also created the ability to create templates so that fields are pre-filled. This creates the ability for bouldering to have their own color grade system specific to gyms. We have also re-purpused or comp ticking interface with a gym session ticking. This is all in beta and we are looking for gyms to start using it.

Set the input mask:

Screen Shot 2020-03-11 at 9 01 19 am

Configure field presets in route templates

Screen Shot 2020-03-11 at 9 03 11 am

You can select the template which sets the preset values when you save.

You cannot yet navigate there but we now have a session ticking interface for bouldering:

Screen Shot 2020-03-11 at 9 05 20 am

To get there add session-boulder to the end of the url at a gym or gym sector. For example:

https://www.thecrag.com/climbing/kletterwerk/area/529723647/session-boulder

Mdemaillard commented 4 years ago

This is awesome, and encompasses way more than duplicate. Kudo for doing the proper thing !

scd commented 4 years ago

The motivation was to give gyms the ability to do a custom grading system. This solution is pretty good for many things

On Wed., 11 Mar. 2020, 6:31 pm Marc dM, notifications@github.com wrote:

This is awesome, and encompasses way more than duplicate. Kudo for doing the proper thing !

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/theCrag/website/issues/1319?email_source=notifications&email_token=AAC3CQUK7L42UFCBNO7GBRTRG445BA5CNFSM4ALDG2O2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOOOGTQ#issuecomment-597484366, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC3CQTMG6LDBQR53ETJVS3RG445BANCNFSM4ALDG2OQ .