Editure+My+PLS

Editure has a suite of educational LMSs including Learning Point and Mysuite. Their new product is MyPLS.

This is my summary from the Presentation: 18/10/2010 : In reality, we only saw their portal, not the LMS. I thought their interface was simple and clean, but was not a learning pathway development program - which is specifically want we want. I have now got some sample logins for us to try and will publish a full list by the end of this week with all the different packages we have seen for folks to begin sorting through them. Thanks.

Logins:

These are the meeting notes from 5th October. MF = Editure/ My PLS meeting  = 5 October 2010 – 9am Jon Kerr, Peter Evans, Andrew and Mif

ARP – Background Adhoc committee. Must get academic staff on board. PE – most of the technology can do what you need. MGS ahead of the game knowing that the implementation is paramount. ARP - Board is very positive, looking to implement a good system. Coming towards the end of the Strategic Plan where there was a decision not to go IT one-to-one. The landscape has changed a lot since then. Laptops are an ongoing cost. Indentified that the intranet is lacking at MGS. The information distribution system needs to be strong no matter what the delivery receivers are. A good system creates easy links between teacher and students, and creates a repository for curriculum. Tagging – should be auto indexed. Outsourced info systems – encyclopedia, echo, etc. Uptake is not good. Single portal system – paramount! – Got to be the same as logging in to email to see what’s happening every day. Texas – district use. System wide home page. NZ HM – must have digital page for every class taught. Windows login to login to everything. Access to all. Similar to the LDAP system we use now. Jon - Social media. How do we use it? MGS policy, generally, is that social media is blocked. ARP - why block it when they can 3G, so we need to have a system where we can monitor their usage and identify problems. Teacher classroom management is paramount. Poor management creates poor usage. Incorporation is necessary but not mandatory, eg. A calculator is a great tool, but unless I actually need to use it, it stays in the pencil case. Same with physical IT tools (phones, iPads, etc.) and virtual IT tools (internet, social networking, etc.) PE - Three years down the stream, what does success look like? ARP – We have a checklist. Crawl, walk run. Three year plan. PE – Excellent! Scaffold the learning. Not ‘training’, PD. Long term journey. Outcome focused, eg. Collaborative process (wiki, blog, etc.) pull resources from online sources, internal etc. to create a multi-user project. Jon – Maximize the educational and technological outcomes over time. The onion diagram – Things that need to be in place.

Software ||  The people factor (in conjunction with Editure) ||  Ecotech the school IT support – looking at systems and improving ||
 * infrastructure Prof Dev
 * Prof Dev: – long term
 * Software:

Servers/ infrastructure delayed owing to changing Business managers – but ARP confident that matches the anticipated need. Prof Dev – right on track. Absolute agreement. Software – need to make the right decision. Features of this system - LAMS, Portals, Mobile version, Learning pathway, integration of MS Exchange (sounds very similar to Desire2Learn) MGS uses Web content filtering – Fortigate (and soon Fortigate Analyser) ARP – query Data management between TASS/VASS and LMS. Peter - SIF Australian standard (systems interoperative framework). SMS needs to push forward into SIF (xls) standard. PK – encourage ARP to talk to TASS about SIF. Meeting arranged to see the system in use. Closed at 1035am