I thought I'd give some answers to your questions/issues.
As you say, the webparts need WSS to run. Therefore, the usernames are simply managed by the AD that the WSS server is set up with. SIMS provisions the AD - the idea being, if you host internally, you can set up the new users, then use the 'consolidation' tool to merge the new accounts with the existing AD accounts if desired.
Originally Posted by dwhyte85
You may think it will get minimal use, but that is down to how the school wants to use it. When we launch our portal to parents, they'll be able to see pupil data, book parents evenings, see how their kids are doing with merits/rewards within school etc... We're making sure parents will *want* to use it.
My main concern is that we're having to buy into a fairly big system (WSS/Moss) for solely showing these webparts, a lot of cost is concerned and as we're upgrading our conn for this... it seems like a lot of cost for something that will get minimal use - if any [of course, I am aware of the pressure being put on us to provide one].
It is all down to how you set up sharepoint - it isn't a SIMS SLG related issue really.
My HT rightly asked about security of logins, they tried to say we could got he RSA route which is a good... but not practical with teachers, the concern is they will change passwords to something obvious even with a policy in place and a leet hacksaw manage to get into the systems and amend live data.
Indeed, WSS will want a reasonable hosting server. Can't argue any point on that. However, you should never have it on the same server as your SIMS data, as that is a security risk. I'd say virtualise it.
Reasonable server spec required for this, should it be ran off of same server [if we didn't go hosted route].
See above for sharepoint/AD comments
Security of teacher login area - .htaccess possible and I change this on a daily basis and post to teachers? No matter how many policies in place someone will have a guessable password... data needs to be truly secure.
As it is sharepoint, it can be as accessible as you want, as you set up the theme for it.
Accessibility... we're not all as lucky to have 20/20 vision
I'm afraid we're now in an age where this is a consideration which most don't take into consideration - you can't cater for everyone, all of the time, otherwise you end up with either reduced functionality or huge costs. However, I don't see how SLG and WSS would be high-bandwidth. The pages are mostly text...
Consideration for low-bandwidth... some people may be on dial up still, if they have a connection at all...
Again, can't argue against that - these things cost a fair packet. This is why our LEA used top-sliced funding to provison SLG as a county-wide service.
Cost! This will severely impact any buying I do this year!
These systems are a tool for a job. If the school is just implementing it because they feel they have to, without a proper idea of *why* they are doing it, then it will fail. The school needs to come up with a plan as to what information they want parents to have access to, why, and then provision a solution to deal with that.
I can see the awesomeness of the idea but... this could be easily a weekly updated set of contents rather than a direct conn to Capita if hosted, or directly accessing DB, furthermore... CommandReporter could get enough information to suffice? I really doubt parents will be checking daily on progress
Remember, seeing a poor implementation of a sharepoint site, with a poor theme etc... is not a reason to dislike the SLG product. The rest of the site is as important, if not more important than the actual data connecting web parts.