Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| development:speaker_ready_room:start [2016/02/13 20:44] – don.lee | development:speaker_ready_room:start [2016/05/15 23:42] (current) – removed don.lee | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Speaker Ready Room System (SRRS) ====== | ||
| - | ===== Workflow ===== | ||
| - | |||
| - | * Speaker login the system with his barcode and lastname (e.g. 59190, Husain) | ||
| - | * SRRS will then show all his presentation topics, sorted by date and start time | ||
| - | * Speaker could click to upload the PPT to each topic. | ||
| - | * Speaker could also click the uploaded file to review it and make sure the upload is completed. | ||
| - | * Speaker logout the SRRS. | ||
| - | |||
| - | The above workflow is already done in the existing SRRS. You may login the system with dummy account " | ||
| - | |||
| - | Some modifications, | ||
| - | * The current login mechanism is by looking up the user object in data/user folder. It should be changed to lookup the User object for admin users and then Topic.speaker object for speaker. (see below for detailed Topic object structure). For the User object, the structure is not so important as you might hard code the admin user in the database because it is only for our own use. You would better added a role in the admin User object to identify who is an admin. | ||
| - | * For a speaker login, it should go directly to the " | ||
| - | * For a speaker login, you could make use of the existing search function on the left by filling in his barcode and auto do a search for the topic. It will then list out his presentations. | ||
| - | * But then the search function should be disabled so that the speaker could not enter other speaker' | ||
| - | * Need a way to import the data from Session data. You may choose to save the web service data to a local file in a certain folder (e.g. data/ | ||
| - | * During the congress, we may need to modify the Session date, time or venue (only these 3 will be changed). So when we re-import the data again, be careful NOT to delete the old data, instead we should only update the data as speaker may already upload the PPT. | ||
| - | |||
| - | ===== Problems ===== | ||
| - | |||
| - | ^ Problem | The SRR is not using MongoDB at all, need to change that to a local db | | ||
| - | ^ Solution | Since SRR will be used without internet, the MongoDB must be local on the same machine. But during the development, | ||
| - | ^ Fixed | 2016-02-13 | | ||
| - | |||
| - | ^ Problem | Need to convert the Session data to Topic instead | | ||
| - | ^ Solution | | | ||
| - | ^ Fixed | | | ||
| - | |||
| - | Current Topic object, could be found in folder /data/topic | ||
| - | < | ||
| - | { | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | } | ||
| - | </ | ||
| - | |||
| - | New Topic Object | ||
| - | < | ||
| - | { | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | }, | ||
| - | " | ||
| - | }, | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | } | ||
| - | </ | ||