Data Management System

Summary The project needs to be developed as a Joomla 3 extension and should ideally also be accessible from mobile devices. The structure should be as follows. Each installation of the extension should allow for the creation of multiple systems each comprising of the same 3 facilities viz. User management; form management and report management. Data within a specific system should be able to be cross referenced. When creating a new system, there must be an option to create a unique identifier for that system, which will allow forms to know “who” the data is for e.g. identification number. This unique identifier must allow for auto population of data from other forms if any of the fields have been previously used in a form in that system e.g. if you start the form with the student number then other fields such as name and surname which may have been inputted in another form must be auto populated with the default data for that student number. Component 1 – User Management Admin must be able to create, edit and delete individual users and groups and be able to assign users to groups. Standard user info must be captured e.g. username, password, name, surname, email address, phone. etc Component 2 – Form Management Must allow for viewing, creation, editing and deletion of forms Field types • Text • Password • Email • Date • Number • URL • Hidden • Text Area • Checkbox • Radio Button • Select • File Upload • Button • Fields separator • Tables Field Functionality List • Please refer to CK form [login to view URL] for basic functionality. • Additional functionality: o Default user/group rights per form with the option to edit the rights per field o Dependent fields i.e. a field only become visible depending on the response of another specific field o Default value of a field auto-populated if the same data was input in another form for the unique identifier o Default value of a field calculated from the value of another field e.g. start date field is 01-03-2013 then we must be able to create a default value for end date by specifying which field it is calculated from and what function to apply. o Email sent to specified users/groups depending on the response of specific field e.g. field asks “has assignment been submitted” if the response is es then email sent to examiner to mark assignment o Reminders - send periodical email reminders (which user must be able to specify the interval) until the response to the field changes e.g. if an assignment has not been submitted then an email reminder must be sent every 2 weeks until it has been submitted. Component 3 – Report Management In the report section, user should be able to create reports and report templates from data input into the forms. Reports must get archived and report templates must be saved so that it may be reused. Reports must be allowed to be downloaded as pdf or excel and/or emailed as pdf to specified users. Report section must also have rights assigned as to who can view, create, modify or delete reports/report templates Data should be displayed in table format, pie chart and bar graph etc. The user should be able to choose which option/s to display as well as data set and range See [login to view URL] for chart types.