Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 327687

Summary:	Change how rooms are set in website schedule
Product:	z_Archived	Reporter:	Anne Jacko <anne.jacko>
Component:	Dash Submission System	Assignee:	Denis Roy <denis.roy>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Anne Jacko

2010-10-13 12:38:30 EDT

Right now summiteurope2010/table.php determines which rooms (column heads in the website schedule) are displayed. There are rooms includes in the csv schedule file, but table.php trumps them.

It would be much better if the rooms in the csv file are the ones displayed in the website schedule.

A related issue, however, is that we use the csv file to set rooms names for special sessions that are in rooms that are not included as column heads in the schedule, such as breaks, lunch, etc. We use empty columns in the cvs file to do this.

So if we change the system to use the rooms in the csv file to display on the website, then we have to figure out a different way to set the room names of those special sessions.

If this isn't clear, let me know, and I'll try to explain it more fully. Thanks.

Comment 1 Denis Roy

2010-10-13 15:13:08 EDT

> A related issue, however, is that we use the csv file to set rooms names for
> special sessions that are in rooms that are not included as column heads in the
> schedule, such as breaks, lunch, etc. We use empty columns in the cvs file to
> do this.

So what you're saying is that this CSV file is not used exclusively for the website schedule?

Comment 2 Anne Jacko

2010-10-13 15:18:09 EDT

> So what you're saying is that this CSV file is not used exclusively for the
> website schedule?

Yes. But I think Gabe must have used some other method to do the "special" room assignments for previous conferences, but I don't know what.

He suggested using the cvs file to handle it this year, but that is definitely a hack IMHO.

Comment 3 Denis Roy

2010-10-13 15:30:28 EDT

Can you help me understand who/what else consumes this CSV file?

Comment 4 Anne Jacko

2010-10-13 16:14:07 EDT

(In reply to comment #3)
> Can you help me understand who/what else consumes this CSV file?

AFAIK, just the import_schedule script consumes it. The only action I perform after editing it to make schedule changes is to commit it, deploy, and run the import_schedule script to create the preview schedule, and then use the Little Button in the sub sys to make the previewed changes propagate to the website schedule.

I don't know how it's created, because Gabe did the original version and I've just been editing that one for the updates.

Comment 5 Denis Roy

2010-10-14 11:22:40 EDT

> > Can you help me understand who/what else consumes this CSV file?
> 
> AFAIK, just the import_schedule script consumes it.

I must be dense. This doesn't help me understand why some special rooms need to be defined into a file that is used by import_schedule, if the purpose of import_schedule is to only create the schedule as it appears on the site.

Comment 6 Anne Jacko

2010-10-14 13:18:37 EDT

> I must be dense. This doesn't help me understand why some special rooms need to
> be defined into a file that is used by import_schedule, if the purpose of
> import_schedule is to only create the schedule as it appears on the site.

Well, you may be thinking you're dense, but I'm pretty sure I am clueless about how all this works.

I'd guess that the original purpose of the csv file and the import_schedule script was to just create the website schedule.

But there was a problem in that the special sessions all were assigned to "Room 1." Remember that? So I asked Gabe how we could make them be assigned to their real rooms. He suggested using the csv file to do it. It's very much a hack! I don't know the "correct" way to get the rooms assigned for lunch, breaks, etc.

If you can figure that out, then the csv file/import script can just be used to do their primary jobs.