all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Yellow
|
|
||||||
|
||||||
|
|
|
Notes:
|
|
Ideas & concepts for the multi-media training tool 1. Make a template for learning and distributing knowledge. 2. Knowledge = Information (correct & right information) x Experience or K= I x E 3. Add a crumb trail to help the users know where they are at… 4. Secure multi-media player. Be multi-media I mean graphics, buttons, links, text, searchable, printable, audio(mp3), video, mapping, motion, PDF, web, controllable, code once – use many, dynamic templates, database fed, permissions, history, usage, forums, feedback, charts, pod casts, dynamic outlines, decision trees within presentation, still images, automated output, etc. 5. Be able to mix and match what the player can do… 6. The end goal is to automate as much as possible. We may have to take some steps to get to that stage. 7. Usage permissions – General public (no login required), all users per corp (requires a valid login), only specific users may view (1-many from training to users). 8. Usage histories – Every time a user views a clip – we record a history note behind the scenes. Random idea – maybe show the users which ones they have seen and when. Maybe even a started and completed flag. 9. If a valid login is required, how can we help the users know if their time limit is up and/or getting close. Maybe run a check against the login table and then prompt them to keep the session alive by searching or refreshing their login history page. 10. On usage histories – it may be cool if you could require certain training modules before allowing a user to use a specific part of the application. This could get out of control but may help educate people before you just turn them loose. 11. The usage history would also need some special reports to help managers and trainers know what is being viewed and what might need a touch-up or revisit. 12. As long as we are doing training… what about testing and evaluations? Why not include a testing module. Not required at all unless you want it. We provide the database, question templates, etc. We also provide the correcting reports to managers. 13. What about a valid login plus an IP address – additional security? Just an idea. Maybe a white list of IP addresses. This may come later if needed. Another idea is require the IP addresses on the login not the media. 14. Training could be as simple as a narrated slideshow or as complicated as a branching interactive video with different sub sections. Because it is a multi-media player – you could even mix and match presentation types in a single player. 15. Ask the question – what would I do? 16. Maybe allow for web services or domain name aliases… 17. Allow outside users to login under a public username and password to submit content for review and formatting. This may require an approval process or an approval/sign off field(s). Only show items that have been approved. 18. Be able to categorize training. This also includes sort options. 19. Keep things fast and efficient – this may require a hybrid solution… 20. We might need to use frames – standard adilas header, player window, extra content to print or add/edit something, standard footer a. This could help with branding, searchable and printable text, etc. b. This might need to be three or four windows within a single master window – you might need to scroll the whole page as a unit. You may also need to scroll the extra content window. It is possible to also use an I-frame instead of a normal frame. 21. One of the goals is to lessen the number of clicks… leave menus open, show indicators, simulate a back-type button, etc. Make it a good experience. This also includes a play all of next clip. 22. Allow the user to determine what buttons to show… this would be done during the set-up phase of the media clip. Different buttons might be play, pause, stop, rewind, fast forward, full speed, ¾ speed, ½ speed, ¼ speed, loop, back to start, step forward, step back, volume, mute, scroll up, scroll down, scroll right, scroll left, zoom in/out. 23. “Apply” what you learn! Do this along the way… don’t wait to the end. The more you apply it, the more it becomes a part of you. 24. Be able to choose options like video, slide show, horizontal scroll (h-scroll), vertical scroll (v-scroll), audio, web link(s), animation, step-by-step, etc. Each section or sub section could have their own button options. You could also show/hide and call any button from a function call on the fly. 25. Make the player as generic as possible. It also needs to be as flexible as possible. It should be able to respond to any event or need. In order to do this, all functions will need to be available and published (written & documented). We may even need to provide flash code samples. Make it easy, I don’t want to be the bottle neck… open it up for other developers. 26. If a change is made in the process, maybe have a piece at the end that shows additions or modifications. That way you don’t have to totally redo the entire clip. 27. Another idea is to break the pieces into smaller pieces so that it would be easy to cut and paste or fill in changes or gaps. Think “bite size” pieces. 28. Allow backgrounds and text colors to be modified. Maybe even think about variable (dynamic) symbols and buttons (icons). Make everything transparent to help show custom background colors. 29. Another option is to allow dynamic player buttons, use .swf files, and allow the player to be fully customized. Even allow a custom loader to be used. 30. The smaller more modular pieces, the better. This will help with branching logic, videos within videos, smaller downloads, and snap-on components and functionality. 31. Remember the non-flash users. This could be html or .mov files. 32. Push vs. Pull technology. Allow the user options to show related clips or possible next steps. 33. Once we start in to flash… I can see navigation, sub modules, shopping carts, schedulers, training, etc. Starting to play in the same base player. It might be cool if there were optional choices or options for classic html or interactive Flash. 34. I want options for QuickTime, mp3 audio, html step-by-steps, & Flash. I want to service all of our clients and their learning styles. 35. Training may fit best as an element of time similar to a document, outline, or idea. The media assets and contents could then be tied to subs. Think of an interactive outline that has subs and dynamic content. That outline becomes the training as it is organized and then sent to a player to allow the user to interact with it. 36. What about tests, quizzes, and evaluations being tied to education and training pieces? This is not required but might be a cool option. 37. Allow the doors to be opened to recruit or enlist help… This could be flow, concepts, media, content, suggestions, needs, etc. The goal would be to provide a clear and logical path with built-in checkpoints and checks. This is a way to duplicate yourself and share the load. 38. Dealing with content, media, and/or other assets… What about having a place for credits… This is the who behind the pieces… This could help to motivate people to play and even drive business to them as individuals. 39. Random idea – Inside of LTF we have a music selection (jukebox or iPod). It might be fun to allow others to be able to change music or have some fun and control of different tunes and/or moods. This doesn’t have to be tied just to music. It could be for music, background sounds, different levels and takes, tracks, different teachers and/or instructors, additional commentary, etc. Sound and music are a big part of learning and defining who people are and what they enjoy and/or feel comfortable with. 40. Instruction could also be a form of meditation or visualizing certain steps and/or events. Think of some calm backgrounds with someone talking or taking you on a mental journey. 41. What about custom help files or standard operating procedures? Because each page has a help file id, we could technically allow a user to tie in their own procedures dynamically so that their users would see or have access to the correct help files or custom help files. This could be HTML, pdf, audio, video, graphics, or other…. (added 12/14/12) |