Contenu connexe


Developing Conference Managment Software: Functionality Review by Example of the LVEE Engine

  1. Developing Conference Management Software: Functionality Review by Example of the LVEE Engine Dubitski A.V. Brest State Technical University CERES. Centers of Excellence for young RESearchers ( 544137-TEMPUS-1-2013-SK-JPHES) Zaporizhzhya, Ukraine, 21-26 September 2016 summer school “Modern trends in Young Education”
  2. Typical Functions of a Conference Management System  Email Notifications  Registration Management  Schedule Management  Publication Support  User Blogs  User Profiles  Accepting Payments and etc.
  3. Conference management systems
  4. LVEE Engine
  5. LVEE Engine Functions  Registration of Participants Management  Content Management  Abstracts Management  Wiki Edit  Email Notifications and etc.
  6. Editors RSS channel subscription Approvement receive Abstracts creation Communication with reviewers Filling participation form Badge editing Edit/translate content/news Account registration Conference subscription Adding abstracts to content Commenting abstracts Conferences creation News publishing Working with wiki Registration opening Approving participation requests Working with e-mail robot Visual theme editing Menu editing «user» role «editor» role «admin» role «reviewer» sub-role Languages addition Working with participants database Placing partners attribution Files upload Timer- scheduled execution content (textile) Web form e-mail Special marks:
  7. Registration The process of registration consists of several steps:  Creating user's profile  Сomplete an application form for the conference  Add his abstracts (an option)  Approval of a user's application form (an option)  Filling in additional fields of the form  Badge editing
  8. User roles  None  Unprivileged user  Editor  Has permissions to edit/translate web site content  Reviewer  Participant of the abstracts peer-review  Admin  A lot of additional capabilities
  9. Editing content
  10. Abstracts Editing
  11. Why was Ruby on Rails chosen?  High speed development  Patterns  Code reuse  Acceptable quality code
  12. Thank you for your attention! Site of conference: Github repository: