|
|
| (57 revisions intermèdies per 11 usuaris que no es mostren) |
| Línia 1: |
Línia 1: |
| {{Work in progress}} | | {{Moved_to_dev_docs}} |
| | |
| This evolving page will list possible Moodle projects for new developers derived from community suggestions, with special attention given to the [http://tracker.moodle.org/secure/IssueNavigator.jspa?mode=hide&requestId=10512 list of most voted-for new features].
| |
| | |
| ''If you have any ideas for new features in Moodle, please see [[Development:New feature ideas]].''
| |
| | |
| ==Custom report generator==
| |
| | |
| An interface for enabling Moodle admins to create custom reports.
| |
| | |
| * Using Moodle [http://moodle.org/mod/forum/discuss.php?d=116895 Feature for creating custom reports] forum discussion
| |
| * Tracker issue MDL-18323
| |
| | |
| ==Record audio repository plugin==
| |
| | |
| Use a Flash or Java plugin to record the audio to a suitable compressed format. The data could then be uploaded as for a File upload plugin.
| |
| | |
| * Using Moodle [http://moodle.org/mod/forum/discuss.php?d=117135 Record audio repository plugin] and [http://moodle.org/mod/forum/discuss.php?d=116968 GSOC: Record Audio/Video directly into resources/activities] forum discussions
| |
| * Tracker issue MDL-18341
| |
| | |
| ==See also==
| |
| | |
| * [[GSOC]] - describing Moodle's involvement with Google in their Summer of Code program
| |
| * [[Talk:Projects for new developers]] for 2008 project ideas which have not yet been implemented
| |
| | |
| [[Category:Project]]
| |
| | |
| Here's a bunch of things, some sections of which are systemic and interdependent:
| |
| - have a simple install wizard, with tick-box selection of features to be installed
| |
| - intuitive menus and wizards (If someone looks at a screen and doesn’t know what to do, you’ve probably got it wrong.)
| |
| - orientation to Moodle tutorial for staff
| |
| - orientation to Moodle tutorial for students
| |
| - orientation to Moodle tutorial for administrators
| |
| - context-sensitive help
| |
| - reduce the amount of techno-babble for system administrators
| |
| - move selected add-on modules to the core and make them optional installs. This has started to happen, but some core items are still only available in modules)
| |
| - have a way for students to input their own data by on-line application
| |
| - have a way for students to update their own data on-line
| |
| - have a way online for new staff to do induction and input their own data
| |
| - have a way for staff to update their own data on-line
| |
| - have the full automated database of student information (admissions, personal particulars, enrollments, enrollment statistics, academic records),
| |
| - graduate students/print diplomas and transcripts,
| |
| - archive records,
| |
| - have a structure that allows for different campuses/ departments/ regions/ etc.
| |
| - take credit card payments (only one option available as a module and then its quite standalone, not integrated,
| |
| - have an automated bookkeeping system to integrate online credit card payments, offline payments students data (e.g. billing, receipting, accounting, functions) and then export reports for institutional reporting, bank reconciliations, etc.
| |
| - manage staff, which are really just a special class of students from a database management point of view.
| |
| - have a central administrator console with GUI menus to do things, e.g. allocate permissions
| |
| - have a regional administrator console for people to run separate campuses/ departments/ regions/ etc of the same institution
| |
| - have a simple structure (and way of organizing) to differentiate between permitted areas: public website, library bookshelves, staff area, separate class area, separate campuses admins, etc.
| |
| | |
| I don't think Moodle has the plugins to do that, but it is all so closely interrelated and overlapping that the core needs to offer them. Some of it could be adapted from Gnucash. That's a full accounting program and the GNU source code is easy to get.
| |
| | |
| The more data entry and update that is done in the field, the less needs to be done in database upkeep. If people depend on the system and it's easy to use, we don't have to motivate them to use it.
| |
