90 likes | 238 Views
Computer comunication B. Intranet. Literature. R. Brandsma & P.Spijker, 2003: Intranet als praktisch communicatiemiddel . Alphen a/d Rijn: Kluwer. W. Hendrikx, 2004: Handboek intranet. Een praktische gids voor overheid, non-profit en bedrijfsleven . Den Haag: Sdu uitgevers.
E N D
Computer comunication B Intranet
Literature • R. Brandsma & P.Spijker, 2003: Intranet als praktisch communicatiemiddel. Alphen a/d Rijn: Kluwer. • W. Hendrikx, 2004: Handboek intranet. Een praktische gids voor overheid, non-profit en bedrijfsleven. Den Haag: Sdu uitgevers. • H. Koeleman e.a., 2002: Intranet voor de communicatieprofessional. Een handleiding voor de opzet en verbetering van intranet in organisaties. Alphen aan den Rijn: Kluwer. Internet: In Dutch: • http://www.naarvoren.nl/artikel/intranet/ • http://www.kennisportal.com/main.asp?ChapterID=804 • http://www.kennisportal.com/main.asp?ChapterID=817 • http://www.communicatiecoach.com/vakgebied_internet_sd_intranet.htm • http://www.kennisportal.com/main.asp?ChapterID=1025 In English • http://www.intrack.com/intranet/ • http://www.libsci.sc.edu/bob/class/clis724/SpecialLibrariesHandbook/Int&SpecLib.html • http://www.intranetjournal.com/
Intranet: CMS Content Management Systems 1 • It is a system that is used to manage the content of a website • It is a web-application that allow us to upload (publish) on the internet/intranet without many problems • There is a difference between content and presentation • The content changes often and has to be constantly maintained and updated • The suppliers of the contents do not need to have specific knowledge about the technical parts or not even about the graphical parts • The way data are presented (the outlook) remains constant • For this designers are useful • CMSs permit to the suppliers of the content to work by themselves on the basis of what they want. Designers think about the rest
Intranet: CMS Content Management Systems 2 • How does it work? • Data are added like normal text • It is possible to have an automatic lay-out with the help of templates • Supports for logos • CMSs are useful for the maintenance and the update of websites • They are less suitable for the (complete) creation of websites • Weblog-software is a form of CMS as well • CMSs can be generic but can be created in specific formats as well
Intranet: CMS Content Management Systems 3 • Necessary parts • An administrator module (usually protected) for importing, adapting and removal of data • A database for the storage of data • A presentation module to visualize the added data • Optional parts • A search module • A module for the administration of the data of visitors and managers • A module for the administration of the presentation-template • A module for the storage of articles that will be showed in different pages
Intranet: CMS Content Management Systems 4 • There are thousands of different CMS (aprox 730 are listed in http://www.cmsmatrix.org/ • They function under different platforms (usually PHP [Hypertext Preprocessor; it is a scripting language] or Java • They support different databases (MySQL, Oracle, IBM, DB etc) • The range in prize is large: from free to thousands of Euros • Difference for website builders like FrontPage or Dreameweaver: they require technical skills • Difference between Wiki’s and CMS: not for everybody and without possibility to elaborate everything in a browser (without additional software) • Confront the systems on http://www.cmsmatrix.org/
Intranet: Steps in the choice for a CMS1 • Determine the purposes for the CMS dependently to your data • Which is the content that you want to manage with the CMS? • How do you want to manage that content? • Get information from (in order) : WWW, books/articles, consultants (expensive!), Professional reports (expensive!) • For special CMS work together with a specialized consultant • Think and document the necessities and the demands before the implementation of a CMS and ask for offers • Offers should be detailed documents on how your necessities should be implemented • The people who make the offer are obliged to maintain their promises • Do not be to technical in the specifications
Intranet: Steps in the choice for a CMS2 • Test the demo-system to have a feeling about the system • Transpose (a part of) your necessities in one scenario • Make a prototype with a part of your data (there are extra costs linked to that, but it is profitable) • Make a clear plan about what parts have to be delivered, and when they should be ready
Intranet:steps of content-processing in one CMS • Organize the content to make it as “processable” as possible (classifications, hierarchies, determination of technical terms • Workflow: How is organized the compiling of data? • Create: The implementation of the content according to the first two steps • Saving: In which format and in which way? (databases? XML? Pictures?) • Check the versions: Who can change the data and when, and how to cope with contradictory changes • make data available: HTML, PDF, … • Archive (retain the choice about retained and cancelled part of data)