search

marcardar / transcriptstudio-isha

Automatically exported from code.google.com/p/transcriptstudio4isha
0 stars 0 forks source link

Better handling of start/end dates in event/session builder #135

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
1. Currently user can define a session date outside the specified event
date range. Should implement some validation check to prevent this

2. When user enters event start-date, event end-date should automatically
be pre-populated with the same date. Similarly, all new sessions should be
pre-populated with the event start-date. (Since most events are only one
session long)

Original issue reported on code.google.com by swami.ke...@gmail.com on 15 Apr 2009 at 5:58

GoogleCodeExporter commented 9 years ago 
Fixed in r429.

Not a perfect fix, but most scenarios are covered.

In particular, when creating fresh new events/sessions (i.e. not importing 
transcript
at the same time) - this is fixed.

Examples of where this is not fixed:

1. Select transcript to import.
Create new event and change startAt to be a different value to the real date.
Create a new session and observe that the startAt is outside of the event range.

2. When editing an existing event's metadata, changes to the startAt, endAt do 
not
give a warning should one of the event's sessions become out-of-range.

I think these problems are minimal and could probably be tackled in an DB 
validation
process.

Other thoughts: I'm not sure how useful event/@endAt really is?

More thoughts - is this issue really High priority!?

Original comment by mjc1...@gmail.com on 16 Apr 2009 at 10:52