1 / 13

Microsoft Sharepoint

Microsoft Sharepoint. What is it? How does it work? Where does it fit in the grand plan? . Example of a sharepoint page. Web Mediated Collaboration. Teachers, admin, support staff, students need to collaborate via the web. Free access front and back end is not enough

RexAlvis
Télécharger la présentation

Microsoft Sharepoint

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Microsoft Sharepoint What is it? How does it work? Where does it fit in the grand plan?

  2. Example of a sharepoint page

  3. Web Mediated Collaboration • Teachers, admin, support staff, students need to collaborate via the web. • Free access front and back end is not enough • Dangerous, chaotic, insecure, and too difficult • Some new pathways, short cuts, and restrictions can make this work. • Sharepoint, moodle, google, facebook, myspace, ….

  4. Balance: Flexibility vs Security Reliable storage, including version control, can also be incorporated in this system. Version control complements reliable storage. But less so when it is app-centric, as in Office. Document locking, not shared access.

  5. Workflow: the document view, example: an exam Can we guide the flow of a document – eg generate messages? Yes. Can we prevent invalid pathways? Don’t know. Do changes to the documents affect the path? No. Support for forms? Partial. Need infopath?

  6. Workflow: assessment vs study book Contrast: Study Book under devt for 100+ hours.. Assessment: < 10 minsat most! Assessment is so complicated, it is hard to cater for it in any general purpose CMS. These documents are transitory, not content.

  7. Workflow: the person view The person-path tends tobe chaotic, and perhapsnot relevant. Or maybe we just don’t pay it enough attention?

  8. Sharepoint: what is it, really? • Web Server • Delivers web pages based on documents, scripts, and database content • SQL Database • Contains info about documents, users, projects (?), groups of users (?), pages • Scripts • Provides flexible delivery of content to pages; mostly built in, but can be crafted. • Documents • Users in groups, and have access rights and restrictions. • File locking and version control (app-centric). • Version Control • Provided by individual applications. Microsoft only. Less secure. Version control is Not Mandatory ?! • Workflow • Weakly supported; • Can work with Microsoft InfoPath. Excludes users of firefox and linux (and mac?). Sharepoint leverages theMicrosoft desktop and Infopath Leverages sharepoint.

  9. Sharepoint’s paradigm • The server is on the desktop • Not exclusive to sharepoint • Similar to google’s net computer paradigm • Opposite emphasis.

  10. Alternatives to Sharepoint • For teaching material: • Moodle, Blackboard, WebCT, …, ICE. • Content Management Systems • More than 100 free and commercial CMS. See: http://en.wikipedia.org/wiki/List_of_content_management_systems • Drupal, mambo – both use apache, php, mysql. We need more than one CMS. Context dictates usage. Compare: study book vs assignment.

  11. Alternatives: ICE, shpt, moodle, svn

  12. Conclusions • Sharepoint is a sort of CMS-light. • Flat learning curve for users. • Ideal for management document collaboration. • Leverages existing paradigms. • Microsoft-only discourse re-inforced. • Local expertise may be discounted. • Weak support for customization, eg workflow. • Beach-head for Microsoft Infopath.

  13. Conclusions: 2 • Users can use more than one CMS at once. • The choice of CMS should be tailored to the workflow patterns, pathways, and performance objectives of the work it serves.

More Related