Wiki system concept for example and Community (draft)

For example,CommunityWiki system concept (draft)

 

 

Background

 

I. Interactive Q & A System

Sina love question, Baidu knows, and some other similar systems in2005-2006It can be said that the year has reached the peak.

Although multimedia calls it "a new search engine method" and "question-based search engine", I cannot agree that this system is just a Q & A system with search functions, second, open Q & A by all netizens is the core of searching. In essence, such a system can be seen as a forum that limits the form of posts.

 

We have also noticed that although this commercial model has achieved great success, it is not a new thing-not to mention that it has been available in foreign countries for a long time. In China,CsdnThe Q & A function of the Forum is actually the same as those of these systems. There are many other examples. I remember "ask experts"-A Q & A system that has been available for a long time. However, these systems are applied in the technical scope. Due to a small number of participants and a small number of respondents, no one answered the question and gradually declined.

 

This Q & A system is characteristic of solving a case-by-case problem. Anyone can answer the question and supervise it. In addition. This type of system is mostly "community-based": People who answer questions correctly will be rewarded in the form of Community rankings.

 

Ii. Knowledge Base System

Raise the knowledge baseWindowsDevelopers may immediately think of Microsoft'sKnowledge Base.

The knowledge base system I mentioned here refersMSOfKBIn that case, we will not answer all the questions we have encountered, but a system that will give a long explanation after the collection and arrangement, and manage and update them in different categories, therefore, it is a system oriented to general examples and Class I problems.

this kind of system is often not open; only professionals can write to ensure its highest authority. At the same time, however, it responds slowly to your questions. For example, if a person is using . net An issue was found and reported to MS , MS does not immediately publish an article kb the article tells him how to solve the problem; MS only the collection of sufficient issues with this aspect, to solve the problem.

Representatives of such systems, in addition to the KB of MS, all kinds of FAQs actually belong to this system. For a typical example, see http://www.syncfusion.com/faq/windowsforms /.
 

Iii. Open Knowledge Base System (Wiki)

in my opinion, wiki is likely to become it an important milestone in industry development, and recorded to 100 years later in history textbooks .

WikiWhile ensuring its openness, it has achieved extremely high authority and truly achieved knowledge sharing for all. At the same time,WikiA new network cooperation mode is provided.WikibookIn this regard, it can be said that it is fully reflected.

 

However, as far as I know,WikiIt seems that there is no open Q & A System (WikiI know very little about it. If so, please let me know ). Therefore,WikiIt is also a general-oriented system for solving general problems.

 

 

The comparison between the three methods is as follows:

comparison project	Q & A System	wiki System	Knowledge Base System
dynamic level	high	low	close to static
knowledge authority	relatively low	relatively high	high
openness of knowledge provision	anyone can provide	anyone can provide	provided by dedicated personnel
oriented questions	example	generic example	generic example
organization management	loose	strict	strict
community style	mostly	NO	NO
Q & A	Yes	NO	NO

 

 

System Concept

My basic idea is to develop a software development, especially. NetA dedicated Q & A system for development ". The quotation marks are added because they are different from the interactive Q & A system described above.WikiAndKBAdvantages of the system.
Therefore, I prefer to call it a case-oriented, community-oriented wiki system ".

The reason for not using a pure interactive Q & A system (such as Baidu Knows) is that:

First, a pure Q & A system will lead to a vicious circle if it is not popular (fewer people will access it if no one answers questions ).

Second, in the pure Q & A system, no one has sorted out the problems that have been solved, reducing the degree of reuse of old knowledge (we can see Baidu knows it and many questions are repeatedly asked, you can only use the search engine to check whether the same question has been asked.-Obtain answers "to obtain knowledge, while the opposite is to" Browse answers"-Knowledge acquisition ", because the answers are not sorted out, it is difficult to obtain.

 

So where is the positioning of the system I imagined?

The first is the authority of knowledge. Although answers are provided by netizensWikiThe system's editing mechanism enables High Authority of answers.

Second, the openness of knowledge. Anyone in the system can provide knowledge.

As for the system-oriented problem, it is a difficult aspect-case-oriented knowledge is difficult to reuse, and extensive-Oriented Knowledge is difficult to solve specific problems. You need to consider this aspect.

Management,WikiAlthough the management method is good, it is somewhat cumbersome (compared with Baidu know ). It is best to use a simplified model that ensures simple management and does not affect the time required for the Q & A loop.

Considering whether it is a Community form, considering that the system is confined to a certain field (. NET Programming), the Community style may be better.
Finally, it is of course the Q & A method, that is, the starting point for editing new knowledge items by asking questions from netizens.

 

 

The above is a draft without proper thinking, and may even fail to read it in many places.

If you are interested, you may criticize and give more comments. If you are interested in implementing the system, please contact me (ask the critics not to simply say "bad" and "What are things ", tell me the reason you think it is poor: P ).

Please contact me if you want to learn more about the ideas and solutions :)