If we have more than 200 programmes on over 40 different topics, we are likely to have 40 different blogs. How will an internal user know about the blog where he can get the content on his topic of interest? Also, how to maintain a single repository of all the contents for various purposes (reference, legal, business or whatever).
One simple solution is to maintain a master blog where we have posts related to our blogs (few sentences and link to blogs).
ReplyDeleteThis system may cause problem if the person maintaining a programme blog deletes his blog.
A better solution is to export the blog to master blog or maintain repository of XML files.
Any blog can be exported by a click of the mouse at appropriate place. It creates a XML file. We can use this file to import the blog on the master blog or any repository site. These are very easy. You can try exporting and importing blogs and see how easy it is.
What will be best method to use the same blog of a particular topic by different co-ordinators / secretaries. Eg. P-1 occurs 4 times in a year and in case co-ordinated by 4 different faculties, how to share/ continue with the same blog by adding / deleting for all the other remaining three groups of participants of that particular year. Or If the topic continues in the next calendar of programmes, will it be o.k. to continue with the same blog to update material.
ReplyDeleteYes, this involves management decision. 3 possibilities come to my mind:
Delete1. Topic wise coordinator/ secretaries.
2. All coordinators/ secretaries of programmes on a topic becoming author of the blog on the topic.
3. Keeping exported files (xml file) in centralized repository. If new blog is required with contents of earlier blog then this file can be imported in the new blog.