SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Microsoft Sharepoint

RexAlvis avatar
RexAlvis
13 diapositives · 633 Views · Mar 04, 2011

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

#sharepoint server
Microsoft Sharepoint - slide 1
01 / 13Microsoft Sharepoint
1 / 17

Télécharger la présentation

Microsoft Sharepoint
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  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.