Enhance docs about schedule creation
Add clearer notes about the preconditions for using a csv to populate the schedule. Update the sample data to one that makes it clear which date format must be used.
This commit is contained in:
		
							parent
							
								
									e48c8c171a
								
							
						
					
					
						commit
						18e338c2c1
					
				
					 1 changed files with 21 additions and 14 deletions
				
			
		|  | @ -25,25 +25,32 @@ available for Staff at:: | |||
| 
 | ||||
| /schedule/talks/edit | ||||
| 
 | ||||
| .. hint:: | ||||
|    Just to reiterate: before this form will work, you must | ||||
|    create a ``Section`` (``admin/symposion_conference/section/``) with | ||||
|    the slug ``talks``; and a ``Schedule`` | ||||
|    (``admin/symposion_schedule/schedule``) for that ``Section`` | ||||
| 
 | ||||
| 
 | ||||
| The form consumes a structured CSV file, from which it will build the schedule.  | ||||
| Sample CSV data is included below:: | ||||
| 
 | ||||
| "date","time_start","time_end","kind"," room " | ||||
| "12/12/2013","10:00 AM","11:00 AM","plenary","Room2" | ||||
| "12/12/2013","10:00 AM","11:00 AM","plenary","Room1" | ||||
| "12/12/2013","11:00 AM","12:00 PM","talk","Room1" | ||||
| "12/12/2013","11:00 AM","12:00 PM","talk","Room2" | ||||
| "12/12/2013","12:00 PM","12:45 PM","plenary","Room1" | ||||
| "12/12/2013","12:00 PM","12:45 PM","plenary","Room2" | ||||
| "12/13/2013","10:00 AM","11:00 AM","plenary","Room2" | ||||
| "12/13/2013","10:00 AM","11:00 AM","plenary","Room1" | ||||
| "12/13/2013","11:00 AM","12:00 PM","talk","Room1" | ||||
| "12/13/2013","11:00 AM","12:00 PM","talk","Room2" | ||||
| "12/13/2013","12:00 PM","12:45 PM","plenary","Room1" | ||||
| "12/13/2013","12:00 PM","12:45 PM","plenary","Room2" | ||||
| "01/24/2018","09:00 am","10:10 am","plenary","CB01.05.009" | ||||
| "01/24/2018","10:10 am","10:45 am","break","CB01.05.009" | ||||
| "01/24/2018","10:45 am","11:30 am","talk","CB01.05.009" | ||||
| "01/24/2018","10:45 am","11:30 am","talk","CB06.03.28" | ||||
| "01/24/2018","10:45 am","11:30 am","talk","CB11.00.405" | ||||
| "01/24/2018","10:45 am","11:30 am","talk","CB01.05.009" | ||||
| 
 | ||||
| It is worth noting that this generates the **structure** of the schedule. It  | ||||
| does not create Presentation objects. This will need to be done manually. | ||||
| 
 | ||||
| .. important:: | ||||
|    It is worth noting that this generates the **structure** of | ||||
|    the schedule. It does not create Presentation objects. This will | ||||
|    need to be done manually. | ||||
| 
 | ||||
| .. tip:: | ||||
|    Sessions such as the ``plenary`` and ``break`` which need to be exlusive will need to be flagged this way in the admin (``/admin/symposion_schedule/slot/``) | ||||
| 
 | ||||
| One can also **delete** an existing schedule via the delete action. This is | ||||
| irreversible (save for a database restore). | ||||
|  |  | |||
		Loading…
	
	Add table
		
		Reference in a new issue
	
	 James Polley
						James Polley