Opened 6 years ago
Closed 4 years ago
#139 closed defect (fixed)
Create a lecture: confusing language at the least
Reported by: | jherr | Owned by: | acastill |
---|---|---|---|
Priority: | normal | Milestone: | v0.98.1 |
Component: | General | Version: | 0.98-dev |
Keywords: | Cc: |
Description
When I create a new lecture here:
conferenceCreation.py?categId=0&event_type=simple_event
It says:
"The lecture will take place in NNN date(s) "
This is very confusing, since use of the preposition "in" makes it look like it is asking if the lecture will take place tomorrow, or the next day, etc. But actually it is asking for the number of days the lecture will be held (which, by the way, makes no sense because then it is multiple lectures, not one lecture).
Anyway, I suggest the following:
1) At the very least, change the text as follows:
The lecture(s) take place on NNN distinct days (if only one lecture, leave the default value of 1)
better yet...
2) By default, only display the single calendar entry. Then have a button for "click here to create a multi-part lecture spread over multiple days"
even better...
3) If the "lecture" actually consists of three separate parts, then people should not be allowed to use this page to create it! They should create a meeting instead. It makes no sense do allow the lecture creation page to create three separate conference IDs, especially since Indico does not know that they have anything to do with each other, other than the very klugey method of using URLs attached as content to link them together. When people search for the 3-day lecture they will not necessarily find all three days.
Change History (10)
comment:1 Changed 6 years ago by pferreir
- Milestone set to v0.98
- Version set to 0.98
comment:2 Changed 6 years ago by pferreir
comment:3 Changed 4 years ago by jbenito
- Owner set to acastill
- Status changed from new to assigned
To discuss with Jose before starting
comment:4 Changed 4 years ago by acastill
- Status changed from assigned to in_work
comment:5 Changed 4 years ago by acastill
- Status changed from in_work to awaiting_merge
comment:6 Changed 4 years ago by jbenito
- Status changed from awaiting_merge to merging
comment:7 Changed 4 years ago by jmonnich
new merge request (in my repo of course)
comment:8 Changed 4 years ago by pferreir
- Status changed from merging to assigned
comment:9 Changed 4 years ago by pferreir
- Status changed from assigned to awaiting_merge
comment:10 Changed 4 years ago by Alexis Castilla Hernandez <alexis.castilla.hernandez@…>
- Resolution set to fixed
- Status changed from awaiting_merge to closed
See #148 too.