Open School MIS
School Open MIS
OpenMIS sounds good to me I think putting SIMS in the final name would be risky.
Open School MIS
School Open MIS
The names not really an issue at this point as there is no product.
All your input will help it become one!
If you have any ideas about names, features, best practice etc please register on the wiki www.schoolsict.com and add your ideas and thoughts.
OSMOSIS - Open Source Management Of Secure Information System
Sounds cool and catchy don't you think? How about a logo of data passing through a "membrane"?
how about eOSMOSIS.org for the domain?
Is there any reason that you aren't participating in The SchoolTool Project (www.schooltool.org) rather than starting a new project? Many Open Source projects fail because once the initial enthusiasm wanes, they become one or two man projects and these individuals don't have the resources to drive the project forward. The Shuttleworth Foundation are supporting SchoolTool, and I think a product will emerge at some point.
Sorry, stickmen are the extent of my drawing capabilities!
Just had a quick look, osmosis.org is available, why not have that?
We have talked about a number of reason to start from scratch and some for not.
As you are at a preliminary evaluation stage, I have a working (not yet feature complete) management information system I wrote for my school over the past 18 months.
I've been debating whether or not to release the whole thing as open source, or whether to release the core system under a non OS license but provide modularity for plug ins.
Part of the problem is that the system is considerably more complex than an application such as a web-forum, with many dependencies on the core systems.
Waiting on trademarking at the moment, but features are thus:
Written in PHP with MySQL Database
Built on the Codeigniter MVC Rapid Development Framework
Uses CSS for gui
Current working systems:
Group management (for classes, clubs and entry years).
Calendar system (we use for assigning applicants to weekly visits and assessments).
Correspondence template system (used to generate various letters during enrol process - pulls data from calendar + user systems).
Config in database so that admin section can be used to alter settings.
Electronic Testing system.
Digital signage page
Export (currently exports year groups to ranger AD tool and moodle, but can be tooled to export to any csv)
Accounting invoice generation (operational)
Ability to modify external LDAP database passwords
Features not yet developed:
Templates (not too hard to do - separate folders)
"my page" for vle
"delete" functionality for various parts of the system
Application's admin section
Active Directory integration (needs modification of existing ldap code + config to select on/off and type).
It sounds from your information that my application meets all of your design requirements as a base.
I honestly think that for such a project to succeed, the open source or collaborative portions of the system have to be modular.
Registration / Attendance system
Add / Remove Modules
If I were to get the system to a point of modularity, would it be something you might be interested in contributing to? Would you be influenced by whether it were released under an OSS or other license if it were available to use for free?
I think you would get a lot of support for an OSS version. Is there a demo avaliable?
There are currently 1 users browsing this thread. (0 members and 1 guests)