If not, I came across these that could possibly be used:
The fact that it doesn't scale yet is because the first objective was to get it running with some minimum functionality, and only then did the scalability problem arise.
I 'm confident that we can make it be fast and scalable. And my personal experience with MyDMS and the chat daemon advises against trying to port something else into Moodle. You just end up rewriting the whole thing, while possibly inheriting some of its drawbacks.
I 'd recommend the following rough plan:
- Let your developers get acquainted with DMS (code-wise). It doesn't matter what they do, let them hack into it to do anything. They won't get it perfect the first time, but they 'll learn how to get it on the second try.
- Meanwhile, define a clear goal you want to achieve. For example, a couple such goals floating in my head are:
- Rewrite the "folder display" logic in such a way so as to be scalable when displaying huge folder trees (it should be able to give out a simple display of folder contents even if the underlying tree contains thousands of records, with the DB load definitely NOT being proportional to the whole tree's population).
- Rewrite the "search" function to use an "eager" approach (do as much work as you can as soon as you can, to save time later) and thus enable it to do whole phrase matching, include/exclude operators, "smart" result set sorting and a few other things.
- When this preliminary phase is complete, you can formulate a plan for the new development and discuss it to smooth out any wrinkles. I 'd be very happy to help in this stage!
And then, of course, the easy work: coding
I strongly advise against starting from MyDMS to get the feel of the code. The current Moodle DMS code (which you can get at anytime from CVS contrib/) has really few thing in common with its MyDMS ancestor. Thus it would be pointless to start with MyDMS... you 'll only get confused later on.
- is it possible to give all the students only their own privat directory?
- and only the view of only the others that are shared with them personally?
- The questions you asked do not concern scalability at all...
- I think that the answer is "yes, by default" to both of them. Are you having trouble?
What is then the scalability problemin your DMS?
(I did not try to use it as a student, first We test as "the three admins",I only have that IE-problem, so I wait, don't hurry, take your time, i am at least six months ahead of our users..)
- Tell them to comment, you should be able to read their code and see what is going on.
- Tell them to learn the Moodle api and use it whenever possible.
- Tell them to study other (core) Moodle modules and try to make their code follow similar patterns.
- Tell them to keep data and display separate