2. Quote

3. Picture

4. Summary of first day: themes and questions CMS/LMS/eLearning: Build vs Buy –Code portability –Sharing of tools/building and leveraging tools –Support/vendor reliability –Schools are revisiting decisions of several years ago: –Jury out--opportunities even for new vendors/new systems. Integration of CMS/LMS with services such as: –Library –Administrative applications –Authorization and Authentication –Portals, calendars etc. Frameworks and standards –Architecture standards in process--hope for the future –Hope for interoperability and stability. –Great interest in cataloging, archiving, indexing and reusing learning objects. –Standards are diverse--frameworks need to allow developers to deal with any standard. –Critical time ahead--next year or so--on practical use of frameworks for tools. How will budget cuts affect this development?

5. Summary of first day: themes and questions Using CMS/LMS/eLearning to Support Teaching –The practical side: however interesting the software, frameworks and standards are, we still need to provide support for the use of CMS/LMS/eLearning in teaching. –Faculty need to be involved. –CMS/LMS/eLearning systems must be transparent and easy for users. –There are no common metrics to evaluate use and success of tools. Adoption rates vary from school to school. –Does a CMS/LMS improve learning? How will we ever find out? Question: If you had to start from scratch today, what would you do for LMS/CMS/eLearning on your campus?