Closed asaunier closed 8 years ago
Concerning the organisation of the attributes (steps), it is currently a bit complicated and not intuitive. Probably too many steps.
I did it, but putting everything in figures makes the form very long. You forgot about contact, access, transports, ratings... But if it's better that way :no_mouth:
isn't a 'Rating' most commonly represented with stars ? If it's not a special value like those letters in other ratings why not use stars ? 5 = 5 stars, it's very speaking :star: :star: :star: :star: :star: Or tell me that users will not get what the stars are and are so used to a scale 1-5, then ok :P
It's more about the difficulty of a route. For the real rating there is a field awesomeness
for outings. That's where we can use stars.
that's exactly what I did, this time i would not let it go if it weren't stars :gun:
got it!
isn't a 'Rating' most commonly represented with stars ?
That's not a quality rating. It's a difficulty indicator. A paragliding takeoff with difficulty 5 is very difficult, not very cool :P
whoa so difficult it must be awesomely hardcore!
I did it, but putting everything in figures makes the form very long. You forgot about contact, access, transports, ratings... But if it's better that way
Don't make too much changes about this. It's still discussed by the client. I'm urging them to make a choice.
Errors reported about the WP editing form:
Climbing indoor:
Climbing outdoor:
Yes/no attributes (eg. "gas unstaffed") should also be set to none (if the info is not available) => the radio buttons should be uncheckable. Perhaps use a "exclusive" checkboxes that supports 0 or 1 value.
- [x] @ginold Are you sure this point can be checked? In the demo the yes/no attributes are still set using 2 radio buttons and it's not possible to unset them when you have checked one of the radios.
Huts:
Discussed with the client. the fields in the WP editing form must be reorganised to make it more consistent.
Depending on the waypoint_type, we would have 2 to 3 steps (not including the "preview" step before saving).
title + lang waypoint_type elevation (+ prominence for summits) longitude + latitude interactive map maps_references
associations summary description quality
Fields for other types will be provided in additional comments below.
title + lang
waypoint_type
longitude + latitude
interactive map
elevation
maps_references
climbing_styles + climbing_indoor_types routes_quantity + height_max climbing_rating_min + climbing_rating_median + climbing_rating_max URL + phone
associations
summary
description
quality
title + lang waypoint_type elevation longitude + latitude interactive map maps_references
climbing_outdoor_types + climbing_styles orientation + best_periods rock_types routes_quantity + equipment_ratings height_min + height_max + height_median climbing_rating_min + climbing_rating_max + climbing_rating_median rain_proof + children_proof + access_time URL
associations summary access description access_period quality
title + lang waypoint_type elevation longitude + latitude interactive map maps_references
custodianship + capacity_staffed + capacity URL + phone + phone_custodian matress_unstaffed + blanket_unstaffed + gas_unstaffed + heating_unstaffed
associations summary access_period description quality
title + lang waypoint_type elevation + elevation min longitude + latitude interactive map maps_references?
lift_access + parking_fee snow_clearance public_transportation_rating public_transportation_types
associations summary access_period road access (= description?) public transportation access (= access?) quality
Paragliding WP, webcam, weather stations: 2 steps if not a lot of dedicated attributes, 3 steps if quite a lot (eg. paragliding)
and have you thought about any names for those steps ? or we stick with 'figures' etc?
what is quality ?!
have you thought about any names for those steps ?
Not yet. I ask the client and let you know.
what is quality ?!
https://github.com/c2corg/v6_api/blob/master/c2corg_api/models/document.py#L65 It's a meta attribute about the status of the document: https://github.com/c2corg/v6_api/blob/master/c2corg_api/models/document.py#L28-L34 useful to figure out the documents that must be improved (or even not publicly listed, for example the empty outings).
Fixed by #266