Self-Organizing Community System

Abstract

The invention provides self-organization methodologies and system for internet users to build web-based organizational hierarchical structure that is constituent of units within which direct and sufficient communication can be fulfilled. Each unit is administrated autonomously through the democratic-decision process, and processes information internally. The members of unit can designate or replace its leader anytime through election; the leader elect of a unit will then become a member of its direct upper unit in the structure, representing its unit to participate in the management and election of upper unit and to bring the consolidated results of its unit to the upper unit for further consolidation; recursively, a hierarchical structure is to form from bottom to upper progressively, and to produce different level of end products at different layer. Taking the advantage of self-organization methodologies, the SOC & SOwiki platform and systems are to be designed and implemented to support various applications of SOC & SOwiki structures that are created to satisfy different social needs or business models.

Description

This application claims the benefit of U.S. Provisional Patent Application, Ser. No. 61/375,021, filed on Aug. 18, 2010

FIELD OF THE INVENTION

This invention relates in general to web application, more specifically to methods and systems for effective collaboration and collective actions of web users, which can be used to build various functions and operation models.

BACKGROUND OF THE INVENTION

With the advent of Web 2.0, the way of information distribution and communication by evolving from “read-only” to “participation from virtually all the users” has inevitably led to information overload. Without effective filtering, verifying, refining and consolidation, useful contents is buried among an enormous amount of useless information, hence serves no use. The present inventor recognizes the questions of how to solve information overload, to consolidate information, and to take advantage of the information has become a major pressing issue of the Internet evolution.

SUMMARY OF THE INVENTION

A method and system of organizing and filtering information is provided. In one embodiment, Self-Organizing Community (SOC) method and system is provided.

SOC can be applied to build self-organization structure from nonexistence which grows as viral expansion loop and has the mechanism of self-consolidation. As an entity, SOC is a hierarchical, multi-layer organization, formed through progressive election from the bottom up, layer by layer, the overall information consolidation in this structure is fulfilled through democratic-decision process and progressive election from the bottom up, layer by layer, to the top.

In one embodiment, a Self-Organizing Wiki (SoWiki) system and method is provided. The SoWiki is a hierarchical, multi-layered and self-organizing wiki system implemented by infusing wiki function with the SOC. Each unit in SOC structure has wiki function. Members create or update contents through wiki methods, which will become effective if the majority of members vote in favor. The elected leader is empowered to take the contents into to a high unit for further consolidation. Recursively, this will lead to a hierarchy structure of information consolidation, which will not only solve information overload, but also minimize the cost given that it is assumed and distributed among all the units/users of the SoWiki.

In one embodiment, the SOC and SOWiki platform provides the self-organization functions for users to create SOC and SOwiki structures, and the systems to support their respective applications and objectives, as well as their needs in terms structure unit, reorganization, and/or collaboration.

In one embodiment, A Self-Organization Information Process System (SOIPS) is one application of SOwiki, which allows users to filter and consolidate the enormous information collaboratively to create various information products targeting in different regions, field or customers, hence to form business models.

Numerous other advantages and features of the invention will be become readily apparent from the following detailed description of the invention and the embodiments thereof, from the claims, and from the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow diagram depicting an exemplary system and process of forming a SOC (Self-Organizing Community) structure. Starting from inception, SOC expands in size by absorbing new members, grows in hierarchy by unit splitting and new layer creation; the end result of such processes is a hierarchical, multi-layered and self-organizing community, namely, a SOC entity.

FIG. 2 is a flow diagram depicting the system and processes of creating a Sowiki (Self-Organizing Wiki) structure by infusing a wiki with SOC methodologies, and how objectives at each layer of the Sowiki structure can be achieved and evolved through information gathering, filtering, verifying, refining and consolidating progressively layer by layer from bottom up.

FIG. 3 is a flow diagram depicting the system and processes of SOC and SOwiki structure reorganization by creating dynamic and rich forms of SOC or Sowiki structures through unit or branch transferring, merging, seceding or affiliating within the same structure or among different structures.

FIG. 4 is a flow diagram depicting how users use the Self-Organization Information Process System (SOIPS) to filter, consolidate and refine the web information through SOC-SOwiki structure layer by layer from bottom up, based on which how various information products are created.

FIG. 5 is a flow diagram depicting some functions of SOC and SOwiki System.

DETAILED DESCRIPTION

A method and system of organizing and filtering information is provided. The following description is presented to enable any person skilled in the art to make and use the invention. For the purposes of explanation, specific nomenclature is set forth to provide a plural understanding of the present invention. While this invention is susceptible of embodiment in many different forms, there are shown in the drawings, and will be described herein in detail, specific embodiments thereof with the understanding that the present disclosure is to be considered as an exemplification of the principles of the invention and is not intended to limit the invention to the specific embodiments illustrated.

SOC (Self-Organizing Community)

A SOC (Self-Organizing Community) is a system and method that can be applied to build self-organization structure from nonexistence which grows through a viral expansion loop. The SOC has a mechanism of self-consolidation. The SOC has a hierarchical, multi-layer organization, formed through progressive election from the bottom up, layer by layer, the overall information consolidation in this structure is fulfilled through democratic-decision process and progressive election from the bottom up, layer by layer, to the top.

FIG. 1 provides a flow diagram of a SOC showing the one exemplary method of forming a SOC from inception to a hierarchical, multi-layered and self-organizing community.

To build a SOC structure from non-existence, the first step is to gather n+1 (₁110) (n>=3) founders or initiators from outside the system, which is generally the only external action necessary. In some embodiments, it is required to have at least three members to form a unit to ensure that the unit does not deadlock and has sufficient diversity of participation. In some embodiments, from this point forward, all the actions are operated within the system with no further external control.

A series of parameters need to be taken into consideration to start SOC system: a value n to limit the size of SOC unit; a required motion second minimum number of members who second a motion for changes to prompt the voting process; a pass ratio to pass a resolution for each type of voting; and an algorithm to calculate weight of each vote (explained below), and an inactivity maximum defining how long a member is allowed inactive etc. System provides default values for all the parameters, but founders/initiators have the options to either use default values or provide values they prefer. In one embodiment, n=3, required motion second minimum number of members is ⅔ of of n, the unit pass ratio is a ⅔ of the members in a unit and a leader pass ratio a majority of the leaders at the highest layer of the SOC structure. In some embodiments, a majority vote as referenced in this description may be assigned other values by the system default or by vote of the members, e.g. two-thirds. Whenever there is a suggestion or motion to reset parameter(s) (₅303), and the motion receives the a motion second parameter minimum number of members (e.g. ⅔ of n) for change the parameter(s), the system will prompt a voting process and the parameter(s) will be reset if predefined percentage (default value: ½) of all the members and a predefined percentage of the leaders (default value: ⅔) at the highest layer vote in favor.

The SOC system also provides functions, tools, and processes for SOC its operation. At least a portion of these functions are shown in FIG. 5. For example, functions, tools, and/or processes are provided for members to set or reset parameter values at any phase whenever there is a suggestion by a member to reset parameter(s) ₅303, as long as at least the predefined or member-defined motion second minimum number of members second the motion, system will prompt the voting process and the parameter(s) will be set or reset if certain percentage (default value: two-thirds) of all the members and of the leaders (default value: ⅔) at the highest layer vote in favor of the change.

SOC system provides multiple interfaces/tools for members to utilize to present information, communicate with each other, and keep records etc. In some embodiments, these interfaces/tools include one or more of a personal blog, a position blog, a unit forum, and a branch forum. In some embodiments, a blog is a webpage or website maintained by its owner having regular or as required entries with, for example, commentary, descriptions of events, or other material including graphics and video. The content can be entered into the blog in blog posts that are normally displayed in reverse chronological order. In some embodiments, a forum is a webpage, a number of webpages, or a website where members can post entries of commentary, descriptions of events, or other material including graphics and video in forum posts. In some embodiments, the interfaces/tools include messaging services, such as Twitter, Skype, email, and other chat services. The system may utilize an application user interface (API) to communite with third party services. The system provides each member of SOC with a personal blog ₅307. In some embodiments, all the opinions or activities of a member in SOC are presented and recorded in his or her corresponding personal blog. A personal blog is attached to and moves with its member-owner.

The system provides each leader of the SOC is equipped with position blog ₅307. In some embodiments, all the opinions or activities in SOC related to the position are presented and recorded in the corresponding position blog. The blog is only editable by incumbent leader presently occupying the position corresponding to a given position blog but is viewable by members at higher levels than the given position. A given position blog belongs to and stays with the corresponding position. In some embodiment, all contents or records of each position blog is archived by the system, and no removal or deletion is allowed.

The unit(s) at each layer of SOC has two types of forums ₅308. The first is a unit forum. A unit form is for unit members to deal with internal affairs of the unit through discussion or decision making (voting) and is not open to the public. Only the members of a corresponding unit can submit inputs to the corresponding unit form. The units that are subordinate to higher unit can view/monitor the contents of the higher unit, but no input from a subordinate unit is permitted to avoid interference. The second type of forum is a branch forum. All the members in a given branch can submit/view inputs and provide feedbacks to the corresponding branch forum. It is a place for opinions. In some embodiments, referendum via a voting module ₅306 can be proposed on the forum within the corresponding branch.

Value “n” is a range set to limit the size of an SOC unit. n ₁100, the minimum size of unit, is a value set to enforce an effective democratic process as is provided by a sufficient minimum number of users. The ñ, the maximum size of unit, is a value set to secure sufficient communication and voting among members of the unit.

The trigger point when a given unit has reached the upper limit ñ is that when the unit can be split into at least n (the lower limit of a unit) units, and each unit consists of at least n members in addition to the leader.

The first or inceptive unit ₁113 should be founded or initiated by no less than n+1 people ₁110, which guarantees that this unit still has no less than n ₁114 people after its leader ₁122 is elected ₅302 and promoted to a higher level.

Members ₁112, ₁222, ₁332, ₁101 and ₁201 in any given layer are represented as dots in FIG. 1 and the shown member has characteristics that are applicable to all the members in that layer. Units ₁113, ₁212, ₁322, and ₁311 in any given layer are represented as an ellipse and it has characteristics that are applicable to all the units in that layer.

Each SOC unit has autonomous right to manage its internal affairs, which may include leader election ₁121 and new member ₁101 recruiting ₁103, other rights as determined by voting processes of the unit, etc. In a given structure, such as layer ₁213, the leaders elected ₁122 by the subordinate units ₁214, ₁217, ₁218 are to form a new unit ₁223 of a higher layer, and as well become new unit ₁223 members ₁222 who possess dual identities: each assuming all the responsibilities and rights of the corresponding subordinate units ₁214, ₁217 and ₁218 respectively as leaders, and as well, assuming all the responsibilities and rights of the unit ₁223 of a higher layer as regular members.

In some embodiment, when voting process is prompted for resolution of an issue or question, the factors used to calculate voting weight are: the voting weight of a leader as a member in the upper unit equals to the sum of the weight of all its subordinate units; and the voting weight of a leader in its own unit equals to the average weight of the unit. The weight of each unit is the sum of the number of members within the unit. The weight of each branch is the sum of the weight of all subordinate units within the branch.

Leaders at each layer ₁122, ₁222, ₁232, ₁332, ₁342 are elected respectively by the units they belong to. The election can be conducted as requested by a predefined number of unit members or on a predefined schedule. The incumbent leader is not allowed to vote in re-election. Once elected, the new leader will replace the incumbent leader that was not successful in the election.

The members are not allowed to vote for themselves as leader except for the ones in base units. Base units have no subordinate units underneath of them. But if a base unit has failed a predetermined number of times—for example, 5 times—to elect a leader who can meet or exceed the predefined number of votes required for election, the system will interfere so the members in the base units will not be allowed to vote for themselves as leader until leaders are successfully elected.

Whenever a decision is democratically reached by election in a unit, its elected leader is accountable to execute and implement the decision. And the decision is applicable to the unit, as well as its subordinate branch (if existing). A subordinate branch includes all units under or subordinate to a given unit.

SOC can grow by recruiting new members ₁101, ₁201 from outside of the structure through its lowest/base level by invitation—which is the method available in the initial phase of SOC implementation—or by self-introduction by the potential new member. The base level or layer includes all units not have a subordinate unit underneath of it. The system will prompt a voting process for the unit that prospective member is intended to join to cast votes, and the prospective member will become member officially and assume all the responsibilities and rights if the majority ₁100 of the unit vote in favor.

When the inceptive unit ₁113 reaches the maximum size of ñ ₁116, a splitting process ₁115 will be prompted. If there is no upper layer on top yet, e.g. no unit superior to the inceptive unit at the initial stage, the unit will split into no less than n new units, each of which should have no less than n members, the minimum members for a unit. During the splitting process, members have the option to group freely through coordination. In rare case that such grouping can't meet the requirement within each splitting unit have a membership of n=<n<ñ after several repetitions, the system will intervene to re-allocate randomly so that the requirement can be met. The representation of n=<n<ñ means that each splitting unit has at least n and less than ñ members.

The open ellipse ₁214, ₁324 followed with n on the right side of each represents n units respectively, each of which contains no less than n members. When the unit ₁113 reaches the upper limit ñ ₁116, it will split into n ₁214 units, which demonstrates SOC structure expansion in size as shown in layer ₁213. Exemplary unit ₁212 represents any unit of layer ₁213, and exemplary unit ₁222 represents elected leader of any unit in layer ₁213.

The leaders elected from the units in layer ₁213 are as well grouped into units, but at one higher level, which has unit ₁223, which demonstrates the SOC structure growth in hierarchy. The leaders in layer ₁213 are also the members of the higher layer unit ₁223. Member ₁222 shows such dual identities of being a leader of one unit in layer ₁213 and a member in one unit ₁223 of the next higher layer. Member/leader ₁232 represents leaders of one higher level or layer elected by the units ₁223 in the next higher layer.

In some embodiments, the principle to emphasize is that in SOC structure, a leader at any given level can't concurrently be the leader or member at its subordinate level. As shown in FIG. 1, when the unit ₁113 reaches its upper limit ñ, it will split into smaller units ₁214, and its leader ₁122 will advance to become the leader ₁232 of its upper level unit ₁223 which comprises the leaders of the units ₁214. Or if there is disagreement, an election will be held within the units ₁214, and the new leader elect from one of the units ₁214 will exchange the position with ₁122 and become leader ₁232.

Unit in ₁213 will be prompted into splitting process when it reaches ñ the upper limit ₁216. Given it already has an upper unit ₁223, it only needs to split into two units to satisfy the requirement for n<ñ and the requirement that any unit should contain no less than n members. The leaders elected by the newly split units will join unit ₁223 as members. When the unit ₁223 reaches ñ ₁226, the splitting process ₁225 will be prompted. Given there is no upper layer on top yet, the unit should split into no less than n new units ₁324 which contain members no less than n respectively, the minimum number required for a unit.

During splitting process, members have the option to group freely through coordination. In rare case that grouping can't meet the requirement n=<n<ñ after several repetition ₁100, system will intervene and re-allocate members randomly to the resulting units so that the requirement can be met. Following the splitting of unit ₁223, layer ₁213 will be separated accordingly into several groups ₁219 of units of same type which have the same structure and follow the same principles.

When reaching ñ, the unit ₁223 will split into n new units ₁324, which leads to SOC's growth in hierarchy or layer ₁323. The leaders ₁332 elected by the each of the units ₁322 form a new unit ₁333 of a higher level or layer, and the newly formed unit then elect its leader ₁342.

FIG. 1 shows a structure (unit or branch) ₁311 either within this SOC or from other SOCs on the same platform. If structure ₁311 decides to be transferred under the unit ₁322, it will become a direct subordinate structure under unit ₁322 and merge with the original structures under the unit ₁322 into one SOC structure (unit or branch) if the majority ₁100 of the members of the unit ₁322 vote in favor of the merger.

Recursively as described above, SOC expands in size as well as grows in hierarchy by constantly, or on demand, or periodically absorbing new members from its bottom level, splitting into new units and forming new layers at higher level.

SOwiki (Self-Organization Wiki)

Sowiki (Self-Organizing Wiki) is a hierarchical, multi-layered and self-organizing wiki system implemented by infusing wiki function ₅402 with the SOC method. An exemplary SOwiki structure is shown in FIG. 2. Each unit in SOC structure has wiki function carried out by the wiki tool as described below. Members can create or update contents through wiki methods with the wiki tool, which will become effective only if the majority of members vote in favor. The leader elect is empowered to take the contents into its upper unit for further consolidation. Recursively, this will lead to a hierarchy structure of information consolidation, which will not only solve information overload, but also minimize the cost given that it is assumed among all the units/users.

In some embodiments, creating a Sowiki structure starts with a SOC initially, that is accountable to define and determine the objectives and form of the SOwiki structure through SOC democratic-decision mechanism. Sowiki structure can be then established by transforming all the members of the SOC into the Sowiki structure as founders or initiators, and expand/grow by absorbing new members on demand, periodically, or constantly.

The method of Sowiki's absorbing new members is similar to that described for SOC: both absorb new members from base layer through invitation or self-invitation. SOC absorbs new members mainly through invitation, but Sowiki mainly through self-introduction in that a prospective member participates by providing submissions, inputs, or content, such as information, webpages, portions or webpages, video, pictures, text, or other content, through a Wiki at the base layer, and will then become the new member ₅401 if the majority ₁100 of the member of the unit that the prospective member is intended to join vote in favor of the inputs or contribution provided to the Wiki by the prospective member.

Sowiki structure operates as detailed below.

Units At Base Level

In the FIG. 2, a functional area ₂100 of existing units at base level of a Sowiki structure is shown. Each unit in functional area ₂100 may include one or more projects ₂101 that the unit in functional area ₂100 is working on through participation and collaboration using wiki tool which allows any changes to be submitted in the mode of wiki editing, where inputs and changes are logged by the wiki tool and are not made effective unless approved by the pass rate minimum number of members of a unit upon a vote of those members. In some embodiments, the wiki tool is a website that allows the creation and editing of any number of interlinked web pages via a web browser using a simplified markup language or a WYSIWYG text editor. In some embodiments, the wiki tool is that described in U.S. Pat. No. 7,954,052, which is herein incorporated by reference to the extent not inconsistent with the present disclosure and except to the extent than according to the present invention edits and changes made to content via the wiki tool are not made effective to the unit project until a majority of the members of the unit where the edit or change was made must approve the edit or change by a predefined approval minimum number of members of that unit before the edit or change is accepted. The outcomes of the projects are dynamic and up-to-date by periodically, on demand, or constantly reflecting new participations and inputs in a timely manner. An inceptive unit ₂104 creates projects ₂101, and is entitled to manage and consolidate the project outcomes. The updates to projects ₂101 will become effective by the system only if the majority ₁100 of the members of the unit ₂104 vote ₂113 in favor, which reflects the basic rule of Sowiki.

The participation in projects ₂101 comes from two directions: one from one or more members ₂105 of unit ₂104 shown as member participation ₂112, another direction from one or more external users ₂106, which may represents any individual of same categories outside the unit ₂104, such as member from other units either within or outside this Sowiki structure, shown as external input ₂111.

The inputs ₂103 from a participant, such as a member or a unit ₂104 via member participation ₂112 or an external user via external input ₂111, will not be accepted automatically into the project ₂101, but will be temporarily stored in the mode of an editable Wiki ₂102 pending approval from unit ₂104 to become effective. The inputs ₂103 will become eligible ₂114 and be added into ₂101 if the unit ₂104 votes in favor; otherwise, the inputs ₂103 will be discarded ₂115.

External users ₂106 from outside of the Sowiki structure can only participate through units at base level. Units above base level only allow its official members to work in its functional areas as shown in functional area ₂300. Inputs from external users ₂106 will become effective only if the majority ₁100 of the members of the unit ₂104 vote ₂113 in favor and external user ₂106 will then be automatically invited to become a member of the unit ₂104, as shown by the invitation routes ₂116 pointing to ₂106 and ₂104.

Because SOwiki is used to create/verify contents, the members who have not participated in any work, including inputs or decisions, for predetermined inactivity period might lose the familiarity or understanding of the contents of the project, so the system will categorize such members as “inactive members”. When calculating the weight of a vote for a member in an upper unit, the system won't include any inactive members in its subordinate units. However, the inactive members can become active anytime and be included in the weight calculation as soon as they resume their participation.

In general, the base units of Sowiki structure are open to the public in order to absorb new members. But Sowiki structure has the option to choose to be exclusive so that only members can participate in its activities. In such case, the system sets parameter for ₂106 to allow only internal member participation.

Multiple functional areas ₂107 of base units can be provided under functional area ₂300 at upper layer. Similarly, multiple functional areas ₂207, of second level units can be provided under functional area ₂300 at upper layer and multiple functional areas ₂307 of third level units can be provided.

Units At Upper Layer

Functional area ₂300 at upper layer has the same structure as ₂100, comprising units ₂304, projects ₂301 and Wiki ₂302.

The units ₂304 in ₂300 are comprised of leaders ₂305 elected by the units ₂104, ₂107 of the next directly subordinate layer. The elected leaders will automatically become member of its upper units ₂304. Recursively, new layers will be formed progressively layer by layer as shown by arrow ₂308.

In Sowiki structure, all the units except ones at base layer are formed by the leaders elected by their directly subordinate units using the principal rules of the SOC method, namely, the “progressive election layer-by-layer” depicted in FIG. 1.

Project outcomes/contents at base layer are open to the public for editing, but the ones at upper layers can only be edited by members of the unit that the project belongs to: such as the project outcomes/contents ₂301 in the functional area ₂300 can only be edited by the members of the unit ₂304. However, except the right of editing, any unit has the authority to decide the right of participation from outside (within or outside of the structure, such as members of other units or external users) regarding attendance of discussions within a unit, viewing contents within a unit, etc., which can be provisioned through setting parameters. This so-called “right of progressive editing” is applicable to all layers. Outcomes/contents become effective only if they are approved by the unit they belong to through voting, regardless of layer they are at.

For instance, the leaders ₂305 will adjust and consolidate the project contents or deliverables ₂101 submitted from the subordinate units such as ₂100, ₂107 with respect to overall objectives and requirements of project ₂301 and ensure they are consistent with its existing, if any, outcomes/contents in ₂301. The adjusted and consolidated results/inputs ₂303 won't be accepted automatically by the project ₂301, but will be temporarily stored in the mode of an editable wiki ₂302 pending approval from unit ₂304 to become effective. The inputs ₂303 will become effective and be added into project ₂301 if unit ₂304 votes in favor, otherwise the inputs will be discarded ₂315, the leaders, as well as the members of the subordinate units have to repeat the steps mentioned above until their submissions are approved and added into project ₂301.

After the project deliverables from ₂101 are all validated and added into project ₂301, every member ₂305 of unit ₂304 is eligible to edit any section of project ₂301 (including the ones that are not submitted by his/her unit) to dynamically reflect updates from subordinate units. The updates will be submitted in the through the wiki tool providing a mode of Wiki editing for approval. The input will become effective ₂314 if unit ₂304 votes in favor, otherwise ineffective ₂315.

When the members in an upper unit of SOwiki structure need to vote on certain issues—i.e. participation, content examination etc., the voting result is based on the votes as weighted from each member: the weight of vote of each member in an upper unit is equal to the total members of the branch underneath the unit from which he is elected as a leader.

The consolidation mentioned above periodically, on demand, or continually elevates progressively layer by layer from bottom up. In one embodiment, the Sowiki can be implemented in an example of writing a book through collective effort of multiple authors: if project ₂101 represent sections of a book, then project ₂301 can be considered as chapters of a book which are consolidated from the sections in project ₂101, progressively by applying the same rules to the bigger consolidation areas, chapters are then consolidated into books, books into collection of works and so on. Continuation ₂309 represents such elevation.

The project outcomes/contents at upper layers are also dynamic by reflecting updates that rapidly bubble up progressively layer by layer from bottom: on the one hand, subordinate units require their leaders elected to reflect updates to the upper units; on the other hand, leaders won't just report updates passively, in addition to self-actualization, leaders are motivated as well by a SOC promotion mechanism that promotes leaders who aggressively pursue the units directions. The SOC promotes a democratic system where a leader of a unit will be motive to effectively pursue the will and direction of the unit, as expressed through voting, otherwise the leader could lose the leadership position at re-election or on demand by a re-call vote of the members of the unit.

The democratic operation mechanism of SOwiki structure can prevent the leaders elected at each layer from being negligent in terms of reflecting updates, or neglecting proper representing their corresponding units. This control comes from following aspects: a subordinate unit can recall its leader anytime through election; all the information at any upper layers is transparent to their subordinate layers; leaders' inputs to the upper layer have to be approved by the upper unit through voting. Therefore, participation in Sowiki structure is not random, only members and leaders that promote the overall objectives of this SOwiki structure will be accepted by the other members and leader.

Creating New Unit

By creating new units, Sowiki structure can dynamically self-grow both in size and in hierarchy. The self-grow process is detailed as below.

In the Sowiki structure, any unit either outside of the structure, such as from external users ₂106, or inside of the structure, such as from members ₂105, can apply to a targeted unit such as unit ₂304 to create a subordinate unit such as unit ₂204 and its functional area such as functional area ₂200. This new unit ₂204 is to assume certain sub-project(s) of the overall or parent project such as project ₂301 of the targeted unit such as ₂304. The new unit will become part of the Sowiki structure and undertake the assumed responsibilities if the targeted unit such as ₂304 votes in favor. The applicants for creating such a new unit will become initial members of the new unit.

Regardless which layer a new unit is to be created under, it will have all the attributes of a unit at base layer given it has no subordinate units at the time of creation. Members or users either from external of the Sowiki or internal of the Sowiki ₂106, ₂105, and ₂305 are eligible to provide input ₂211 for consideration in the projects ₂201. And the inputs ₂203 will be submitted via the wiki tool in the mode of an editable Wiki ₂202 pending approval from the unit ₂204. However, the inputs ₂203 submitted ₂212 by the members ₂205 of the unit ₂204 require the same type of approval.

The new unit ₂203 is not eligible to vote if the number of its members is less than n. The right of voting will be surrogated by its upper unit ₂304. The inputs ₂203 will become effective ₂214 if unit ₂304 votes ₂231 in favor, otherwise, will become ineffective or discarded ₂215. The voting right will be restored to the unit ₂204 once the number of the members of unit ₂204 is equal to or greater than n.

Once the inputs are approved by the new unit or its upper unit, the participant who provided the inputs will automatically be accepted as member of the new unit and assume all the responsibilities and rights of a unit member ₂205 via path ₂216.

Once the new unit ₂204 grows to a point of having a numbers of member equal to or greater than n, it becomes eligible to operate independently by assuming all the responsibilities and rights of a regular unit such as making decision for the unit by voting ₂213; electing ₂232 its leader to represent the unit in its upper unit ₂304 etc. Unit ₂304 will no longer play the role of guardian or surrogate for unit ₂204, and functional area ₂200 will operate the same as functional area ₂100 from that point forward.

Unit Splitting

The Sowiki structure is constructed for the objectives of its projects with respect to contents, which should not be divided randomly by Sowiki. So Sowiki unit will not split automatically as occurs with the SOC method when the unit reaches its upper limit, which is why Sowiki structure only prescribes the lower limit n of a unit; the upper limit ñ will be defined by unit according to the nature of its project instead being set rigidly by system. The Sowiki unit will split if the majority of its members agree that their project can and/or should be split into branches.

The process of Sowiki unit splitting provides that, when the unit to be split has no upper layers, the projects of the splitting unit will be split into n sub-projects first based on the decision democratically made by the unit through voting, and the members of original unit will then be associated with sub-projects around which the new subordinate units are formed. If the original unit is at base layer, its members will populate the new subordinate units by choosing the sub-project they are interested in, otherwise, they will populate new subordinate units by choosing the sub-project that the units they are representing are interested in respectively. However, each unit has to meet the requirement for having no less than n members. In the case of deadlock where the unit splitting cannot meet the minimum n members requirement after several ₁100 repetition of the steps mentioned above, system will intervene and splitting process will be completed by system randomly or according to a predefined algorithm that is designed to simulate random placement, such an algorithm that utilizes numbers provided by an algorithm that simulate the random output of number known in the art. But when the unit to be split has upper layers, it can be split into less than n subunits which are all subordinate to the original upper unit in the higher layer.

The units above base layer can decide autonomously if they should grow/create new subordinate units, the process of which is similar to that of splitting except that the process of creating new subordinate units does not need to comply with the constraint that the original unit is required to split into no less than n subordinate units. The newly created subordinate unit will be at the same layer of, and in parallel with, the original subordinate units under the senior unit that indicated the subordinate unit creation. New subordinate unit can be created flexibly whenever needed.

SOC And SOwiki Structure Reorganizations

In FIG. 3, triangle represents branches of Sowiki structure and a small triangle in a big triangle represents a small branch within a big branch. The lateral ellipses ₃121, ₃221, ₃321, ₃120, ₃220, ₃320, ₃500 represent the lateral expansion by the addition of the same respective structures laterally along the same layer or level. The vertical ellipses ₃130, ₃230, ₃330 represent hierarchical expansion by layers respectively upward.

The highest elected leaders ₃112, ₃101, ₃201, ₃301, ₃421 in each respective branch are shown. Further, in FIG. 3, the highest unit ₃231, ₃331 and ₃404 in a respective branch are shown and members ₃232, ₃332, ₃405 of the highest branch respectively are shown. Details for certain units or portions of branches are not shown in FIG. 3 so as to demonstrate the overall structure.

Structure (Units Or Branches) Transferring

When a unit or branch in a Sowiki structure secedes from its upper unit, and joins under another unit within the same Sowiki structure is called transferring.

In case that branch ₃100 and branch ₃200 belong to a same Sowiki structure, and structure ₃111 (which may be a unit or branch) decides to transfer under or within branch ₃210, the elected leader ₃112 of the structure ₃111 will need to file application to the upper unit ₃231 (consisting of the elected leaders ₃232 from the units ₃211 and ₃221) for such transfer. Structure ₃111 will then be transferred into ₃210, hence become a subordinate structure ₃221 under the unit ₃231 if the unit ₃231 votes in favor; the elected leader ₃112 will become a member ₃232 of unit ₃231. If structure ₃111 is a branch with subordinate units, the whole branch (including all the subordinate units) will be transferred together into branch ₃210.

The Sowiki structure will not allow a unit or branch to have more than one immediately senior/upper unit to avoid overlapped voting rights. Therefore, the first step of transferring is to secede from the original upper unit in order to avoid having two immediately superior unit.

Whether or how the transferred units can take away the projects they are working on to the new structure depend on the setting of the Sowiki structure based on the agreement achieved within the structure. Therefore, in some embodiments (1) the transferred unit can take all of the projects currently pending to the new structure, (2) the transferred unit can not take the projects currently pending to the new structure, and (3) the transferred unit can take the projects currently pending to a new structure only if a majority of the members of the immediately senior unit above the transferred unit approves of the transfer of currently pending projects.

Structure (Unit Or Branches) Merger

One of the methods to merge units is to combine different units within the same Sowiki structure, along with their projects and members. If the to-be-merged units are subordinate to the same upper unit, they, as well as their projects and members, can merge into one bigger unit if the majority of the immediately upper unit vote in favor for the motion of merger. The merged unit will then assume all the responsibilities and rights with respect to the combined projects.

The units, that are within the same SOwiki structure, but subordinate to different units, can merge provided that the upper unit of the unit at the receiving end votes in favor to the motion of taking over the unit that has applied to merge in. The unit to be taken over will be required to “transfer” (refer to transferring section) first under the upper unit at the receiving end and then merge as demonstrated in the proceeding paragraph.

Another method of merging is with respect to different Sowiki structures. Therefore in some embodiments, it is assumed that branch/structure ₃200 is an independently created and self-evolved Sowiki structure and decides to merge into structure ₃310 in another Sowiki structure ₃300 and to be one of structures ₃321 at the same level with structure ₃311, the highest elected leader ₃201 of the structure ₃200 will need to file application ₃221a to the unit ₃331; The structure ₃200 will be then merged into structure ₃310 and become one of the structures ₃321 and leader ₃201 will be accepted as a member ₃332 of unit ₃331 if the majority of the members of unit ₃331 vote in favor of the merger. Whether a structure is accepted for merger depends on the vote of the receiving superior unit as well was whether the resulting merge structure will violate any parameters of the system, such as structure size, which is considered by the receiving superior unit.

Structure (Unit Or Branch) Secession

As mentioned above, the process of a structure (unit or branch) transferring consists of two major steps: secede from its original upper unit first; and then merge into the targeted structure. Alternatively, a structure can decide to secede from the Sowiki structure it belongs to and become an independent Sowiki structure.

It is the given right of Sowiki unit or branches to secede, but the key is if the projects they are working on can secede as well and go along with the seceding structure, which requires the agreement or contract with respect to secession being established during the inception of Sowiki structure. The agreements or contracts can be executed and guaranteed by the Sowiki operating system/platform through parameter setting.

If the secession leads to that the members of the original unit become less than n, the seceded unit will lose its right of autonomy, which will be surrogated by its upper unit, and reinstated once the number of its members grows to no less than n.

Structure (Unit Or Branch) Affiliation

Horizontal affiliation is to achieve specific objectives by uniting different Sowiki structures without losing their attributes and intactness as independent structure (unit or branch). The affiliation is of extensive applicability and can be either temporary or permanent.

Horizontal affiliation can be created by loosely uniting different units or branches within a Sowiki structure. In some embodiments, assuming that ₃111, ₃200, ₃300 are different branches in the same Sowiki (they might be at different levels, but this will not have an impact on affiliation), the process to unite them requires that the highest elected leader of the affiliating branches ₃112, ₃201, ₃301 reach agreements for affiliation in terms of objectives, parameters and new leader election ₃421 etc. with respect to the new structure (each affiliation is considered as creating a new structure) by negotiation and collaboration. The leaders from each original structure form a new unit ₃404 and the affiliation will then be administrated by the leader ₃421 elected by unit ₃404 or directly by unit ₃404 working as a committee. Once the affiliation is created, its functional area ₃400 will be automatically created by the Sowiki platform and open for use.

The members ₃112, ₃201 and ₃301 of the unit ₃404 at highest level of the Sowiki affiliated structure will adjust and consolidate the projects they are representing respectively with respect to overall objectives and requirements of unit ₃404. The adjusted and consolidated input ₃403 won't be accepted automatically by the project ₃401 and will be temporarily stored in the mode of an editable wiki ₃402 pending approval from unit ₃404 to become effective. If unit ₂404 votes in favor ₃413, the inputs ₃403 will become effective and be added into project ₃401; otherwise, the steps mentioned above are repeated until approved and added into project ₃401. Further adjustment and consolidation of project ₃401 by the unit ₃404 follows the general Sowiki rules and principles depicted in FIG. 2 and the related description.

However, this horizontal affiliation can as well be created by uniting units or branches from different Sowiki structures. In some embodiments, if it is assumed that ₃111, ₃200, ₃300 in FIG. 3 are different Sowiki structures, the flow diagram of creating such an affiliation is the same as demonstrated above.

Once the affiliated structure is formed, the appropriate forums, wiki areas, position blogs etc. will be created automatically by the platform and open for use as detailed in the section above on the SOC.

The affiliation can be objective oriented or structure oriented. The objective oriented affiliation is usually temporary and will be dismissed after the objectives are achieved. The structure oriented affiliation usually has long-term goals and therefore more stable.

Such affiliation is realized only through the leaders at the highest levels i.e. ₃100, ₃200, ₃300 and each individual Sowiki structure is kept intact and can be removed from a new structure and restored to original structure easily. This loosely connected structure keeps the advantages of small structures: higher-level of autonomy, efficiency and varieties etc., as well has the benefits of big structure: broader spectrum of view, more resources.

Affiliations can cross and overlap, for instance, the leader elected ₃421 of the affiliation can choose to unite with another structure to form a new structure with respect to new projects or new objectives.

In summary, SOC and Sowiki have rich and flexible ways of evolving horizontally or vertically in terms of hierarchy and size by utilizing the methods and functions mentioned above such as new units creating, unit splitting, unit merging and combining etc., hence to achieve an evolving space to accomplish very effectively various objectives.

Self-Organization Information Process System (SOIPS)

The flow diagram FIG. 4 depicts how users may use a Self-Organization Information Process System (SOIPS) to filter, consolidate and refine web information through SOC-SOwiki structures layer by layer from the bottom up, based on how various information products are created. In one embodiment, the SOC, SOwiki, and SOIPS are systems and methods of the distributed allocation of work.

The grey dots in the FIG. 4 represent any one item of the same categories in which all the items possess the same attributes. The solid dots represent multiple projects of same kind.

Participation

As shown in FIG. 4, any web user can become a participant ₄201. The SOIPS provides a user interface. In some embodiments, the SOIPS includes a standalone program installable on a user's device, such as a computer, tablet, mobile smart phone, or other programmable computing device. In some embodiments, the SOIPS includes an internet web browser plug-in ₄205 that is installed in the user's browser ₄203. In some embodiments, the SOIPS is accessible over, a computer network, such as the Internet via the browser ₄203 without the need of any software installed on the user's computer or computing device.

Information is submitted to the SOIPS computer database ₄215 by participants. In some embodiments, access to the database may be mediated through a database management system, such as those known in the art. When a participant ₄201 browse or process web information, if the participant believes that some information, content, data—such as a website, webpage, or a portion of a webpage, such as a paragraph, headline, picture, video, or the like—is worth sharing, the participant can click the Share button ₄208 provided by the plug-in ₄205 or other user interface, and the information will be automatically collected by the SOIPS, processed into standard format, and then stored in the computer database ₄215.

Some embodiments, the information shared by the participant is saved in a link record ₆620 as shown in FIG. 6. The link record includes a result ID section ₆621, a network address section ₆622, a category(ies)/tag section ₆623, a level section ₆624, a type section ₆625, a clip section ₆646, and a rank section ₆647. The result ID is a unique result identifier, such as a number. The network address section ₆622 contains information about where the content is located on the network. The network address section ₆622 may be a Uniform Resource Locator (URL), an IP address, a page location indicator for identifying where on an Internet web page the selected content is, or any combination of the forgoing, or other network location information formats known in the art. The category(ies)/tags section contains one or more categories or tags that purport to classify or describe the information associated with the network address. Tags and categories may be chosen from system defined lists or may be freeform entered by a user or member. The type section ₆652 contains information about what type of information is found at the network address, e.g. text, video, pictures, animation, or other classes of content. The clip ₆646 may section contains a portion of the content at the network address. The clip section may contain a section of text, an image, a thumbnail of an image, a section of video, or the like. The rank section ₆647 contains the DR rank, as explained below, of the contents associated with the network address.

Information can be submitted to the SOIPS from any Internet or network source, such as search engines ₄101, Twitter ₄102, blogs ₄103, forums ₄104, images ₄105, video ₄106, audio ₄107, webpages ₄108, Internet business ₄109, social networks ₄111, RSS readers ₄112, etc.

In some embodiments, the computer database ₄215 is connected to a server or other computer (not shown) for providing access and modification to the database. The database may be maintained on a computer storage, such as a hard-drive, a number of hard-drives, solid state storage, or other database storage mediums known in the art.

Each participant can categorize ₄210 the information to be shared by adding one or more tag. Tags may be understood as a keyword(s), or term(s) assigned to a piece of information, which may provide additional information about the information being tagged. Tags may be understood as metadata for the information being tagged. In some embodiments, the SOIPS has a duplication reduction function that can process the data submitted by participants to consolidate data about the same information that might be submitted by different participants. In some embodiments, the SOIPS has an automatic categorization function where by comparing the content of the information submitted to a pre-existing word association database, the categorization function can add tag and category information based on matches generated.

As information is submitted to the SOIPS, a large dataset may be accumulated. Participants filter the information. After the steps mentioned above, the enormous and complex internet information in this database is filtered by participants, has formed the preliminary category structures, hence possess the value to “Select/View” ₄216, and will be also given the DR value (see the section “DjRank for details).

The SOIPS has a select/view function ₄212 that allows a participant to select and review information in the database ₄215. The view/select function allows a user to define or select the categories ₄210 of information that each user wishes to review. In some embodiments, participants or users ₄201 only need to click the “Select/View” button on the plug-in ₄205 to select and review the filtered/categorized/tag information that they are interested in. And the SOIPS will automatically assign ₄214 certain contents to a participant, such as a small fragment of contents within the subjects/categories area chosen by or preset by or for the user that they are interested. Each participant will be given different non-overlapped fragments of the contents within the database ₄215. The select/view function divides the contents of the database under according to certain predefined characteristics, such as categories and apportions a subset of that data into affordable or manageable assignments to be assumed and processed by a plurality of corresponding participants.

The SOIPS has a recommend for promotion/recommendation function ₄217 where a participant, at the time of select/view function ₄212 can vote or decide whether the information begin reviewed, in the participant's judgment, is valuable for the given category of information. If the participant finds the information valuable, the participant can through the recommend for promotion function ₄217 recommend said information as being valuable for the corresponding given category(ies) of information. In one embodiment, the SOIPS provides a recommend button that a participant can press to recommend the reviewed information during the review process.

The SOIPS also provides a re-categorize function so that each participant can not only recommend the contents further that he/she believes are of any value by clicking the the recommendation button, but can also correct or further categorize ₄213 the information being reviewed. If there are enough participants, although each only assumes a fragment of the contents of the database, a second round of filtering and consolidation utilizing the SOIPS with respect to the data stored in the database can be achieved.

SOC System And Method

The contents that are recommended under the recommendation function ₄217 by the participants ₄201 during Select/View function ₄212 will be added into SOC-SOwiki structure ₄300 (see FIG. 4) pending further review under the pending review function ₄301.

The information in the pending review function ₄301 will be automatically categorized and tagged by the SOIPS system. In some embodiments, the SOIPS has an automatic categorization function where information is categorized based on keywords extracted from the information which can be based on the full text of the information, the title of the page having the information, the backlinks to the page having the information, the anchor text associated with the backlinks to the page having the information. In some embodiment, the automatic categorization of information in a search database may be any such function or method known in the art and not inconsistent with the present disclosure. The SOIPS will then assign information queued in the pending review function to one of the units ₄306 in layer 1 of the SOC-Sowiki. In one embodiment, each of the units ₄306 has one or more categorizes of information that it is assigned to review and the SOIPS assigns information queued in the pending review function to one or more units based on each having an assigned category corresponding to the category of the information queued. Once information is assigned to a unit ₄306 in layer 1, it is further assigned by the SOIPS to a layer 1 member ₄304 of that layer 1 unit ₄306, for further assessment or correction. For instance, the information will be corrected if the previous categorization is not accurate and then be returned to pending review function ₄301, and the system will then reassign the information to a different unit ₄306 of that layer having unit category corresponding to the category of the information.

The system provides a two step information review. The first step is a preliminary review by a member of layer 1. Each layer 1 member ₄304 will perform a preliminary review of the information that the system has assigned them. If the member believes that the information is worthy of further recommendation, the member ₄304 will preliminarily recommend that information by signaling the same to the system. At the second step, the system initiates a unit vote where the contents recommended by layer 1 members of a unit will be sent by the system to all the other members in that unit and each member will then to vote on whether the information should be promoted to the next layer.

The information that has the votes meeting or exceeding the passing rate (pre-set parameter) will be sent to the layer 1 subjects section ₄310, and the participants ₄201 who have recommended the contents during select/view function ₄212 will automatically be invited into membership of layer 1 by the system. As members of layer 1 they are eligible to manage the layer 1 subjects, and will assume all the responsibilities, as well as the rights of layer 1 members. However, the invited participant may refuse to accept or may decline the membership invitation to layer 1 or any other layer.

The content that does not have votes meeting or exceeding the passing rate, will not be included in layer 1 subjects. However, if the content was recommended at the recommendation function 4217 and by at least one reviewing layer 1 member 4304 it will be assigned a DJ (see the DR Rank section below) ranking.

The leader elected ₄308 by the layer 1 members will become a layer 2 member ₄312. Therefore, the number of the members in layer 2 units ₄314 is equal to the number of its direct subordinate layer 1 units.

The layer 2 members ₄312 review the contents in layer 1 subjects ₄310 that were recommended by the layer 1 units. The system distributes the contents in layer 1 subjects to the layer 2 members according to a predefined algorithm. In some embodiment, the algorithm is designed to similar random assignment. However, if the contents was assigned to one given layer 1 unit, the system will not assign that contents to a layer 2 member that is a member of the given layer 1 unit, where that contents was previously considered by that given layer 1 unit, to avoid prejudice. Each layer 2 members can further recommend the contents that he/she believes are of value during preliminary review at layer 2. Contents recommended by layer 2 members are the preliminary reviewed will then be presented by the system for a unit vote. If the votes of the members received meet or exceed the pre-set passing rate ₄315, the contents will then be automatically sent to layer 2 subject area_—4317.

The leader elected ₄316 by the layer 2 members will become the members of the upper layer, namely here layer 3 members. The contents of layer 2 subjects area will be assessed by preliminary review and a unit vote will be conducted among the layer 3 members, if the votes of the layer 3 members meet or exceed the pre-set passing rate, the content will be escalated and become the layer 3 subjects. The dotted lines ₄316 and ₄322 represent the that there may be any number of intermediate layers (not shown) and subjects (not shown) towards the highest layer N units ₄320 and its layer N subjects ₄324. The rules at each layer are the same.

DR Rank

The aforementioned system and methods provide means to attract participants into SOC structure through which information can be filtered layer by layer from the bottom up, and the filtered information will be given a value according to the level it has reached. Different from filtering system through machine-only_algorithm, DR ranking takes advantage of human knowledge and wisdom to enhance the quality of search ₄413 results. It is hard to judge the quality of search results through the ranking generated by a computer algorithm. Taking advantage of human wisdom is way to enhance the search result with higher accuracy in terms of statistic significance that is achieved through participants input, as well, by the filtering power of the layered SOC structure. In some embodiments, the large scale participation of participants can distribute the work and further enhance the accuracy of the search results ₄413.

SOC structure filters information in two ways: voting by members and decisions by the leader. DR ranks may be provided on information based on the filtering process. Under the voting by members process, members will receive distributed contents from the subordinating units, or from Internet user if the unit is on the base layer (see ₄217), from which, members will preliminarily recommend the information he/she believes is of value. The recommended information will be reviewed by all the other members in the unit and the unit members will vote if the recommended contents is worthy of escalating to next higher level. Recursively, each layer follows the same rules to filter information. In some embodiments of the DR rank system, the system will increase the rank of contents by a value of 1 each time a unit votes to promote the contents. In some embodiments of the DR rank system, the system will increase the rank of contents by a value of 1 each time a member preliminarily recommends the contents and increase the rank of the contents by a value of 1 when a unit votes to promote the contents. In some embodiments, a different value is assigned to content receiving a preliminary recommendation than is assigned to content receiving a unit vote to promote, e.g. +1 for preliminary vote and +3 for a unit vote to promote.

Another method is “decision by leader” where members with receive distributed contents from the subordinating units, or from Internet user if the unit is on the base layer (see ₄217) from which members will recommend information he/she believes is of value. The leader will select the ones from the recommended contents that he/she believes of value, and escalate them to the next higher level. Recursively, each layer follows the same rules to filter information.

Therefore, at least three types of value events may indicate the content is valuable and thus provide a basis for increasing the DR rank associated with the content, a preliminary recommendation by a member to promote the content, a unit vote of a unit to promote the content, a leader recommendation to promote the content.

In some embodiments the DR rank system, the system will increase the rank of contents by a value of 1 each time a leader promotes the contents. In some embodiments, a different value is assigned to content receiving a leader promotion recommendation than is assigned to content receiving a unit vote to promote, e.g. +1 for preliminary vote and +2 for a leader promotion recommendation. Other incremental values can be assigned each type of value event. In some embodiments, DR rank is the sum rank increases resulting from a preliminary recommendation, a unit vote to promote, and/or a leader promotion recommendation at any layer. In some embodiments, the DR rank of contents is only increase when the content is promoted by a unit vote to promote.

In general, the method “decision by leader” is more efficient than the method “voting by member”, especially in initial phase of SOC structure implementation. Once the SOC structure becomes mature and members are active to certain extent, the method “voting by member” should be used as a regular operation as it embodies the SOC advantages, that is, the accuracy in terms of statistic significance through large scale of participation.

The data selected/filtered using “Self-Organization Information Process System” (FIG. 4)—including the data “Shared” ₄208 or Selected/Viewed ₄212 by all the participants, as well as the “Recommended” ₄217 through the layers of SOC structures—are stored in the database ₄215. The information in this database is hand-picked by individuals and reviewed/assessed by groups (units), hence is of higher quality compared with the enormous random Internet information; all the data collected in the database is given DR values using the methods mentioned above. When the data accumulate to certain extent, users can search by key words—searching results are ordered according to its DR value, or taking advantage of layered SOC structure that covers certain subjects by regions or fields, users can directly go to certain layer of SOC structure, review the information that is filtered to such extent namely, according to the associated DR value.

DR rank is an application of SOC structure, and DR value reflects the results of information filtering through SOC structure. The DR value pyramid represents the quality level of the information, is used to organize information from general to specific by regions or fields, and to provide the convenience to find the targeted information. In SOC structure, the information amount is further reduced and refined over the layers from bottom up which is the way to solve information overload and to enhance searching results. Therefore, DR rank can be used as a new searching method to complement the existing ones, and to mitigate their inefficiency.

Taking advantage of SOC open interface platform and sharable database, users can implement SOC structures (SOC structure can be merged or united) to filter/refine/categorize information by regions or fields. DR value is obtained for each piece of information along the process, and targeted information products are in the mean time generated—Scroll News ₄405 in the order of DR value, various guides ₄404, Audio/Video Channels ₄407 and Data Warehouse ₄408 etc., These products are the end results of massive participation of users, hence represent and address the needs of users.

SOwiki Methods

SOwiki system and methods are the same as SOC system and methods in terms of its structure and creation. The difference between SOwiki system and SOC system is that members in Sowiki system will also take part in editing and consolidating information in addition to reviewing or recommending information. Under one embodiment of the SOC system, the results consist of a listing of links or contents without any editorial commentary, whereas SOwiki system provides members the ability to reorganize and consolidate contents provide commentary. If the SOC system provides an ordered listing of content, the SOwiki system has the functionality of, in an analogy with the news industry, editorial control to consolidate, paraphrase, reorganize, and editorialize on information based on primary sources, or input from members. The steps are detailed in the following.

The pending layer 1 review contents ₄301 by layer 1 units ₄306 will be distributed automatically by the system among the unit members. Each member will consolidate the information assigned to him/her, and submit the result to the layer 1 subjects module ₄310. Each member can create subjects, expand the scope of the existing subjects, or revisit the subjects already considered. However, all each members efforts of consolidating, creating, expanding, revisiting, etc., must be approved by the other members in his/her unit through voting in order to make them effective.

Hence, the contents of the layer 1 subjects are not composites of the recommended information listed in parallel, as in SOC system, instead, it is a whole piece consolidated by all the members in the unit.

The leader elected by the layer 1 members will become a layer 2 member ₄312 of a layer 2 unit ₄314, bringing the consolidated and voting approved layer 1 subjects ₄310 into the layer 2, which if approved by the layer 2 members will become layer 2 subjects ₄317, and the leader will participate in further consolidation of the layer 2 subjects representing the unit from which he/she is elected.

A layer 2 subject is comprised of a number of the layer 1 subjects. Each layer 2 member is also the leader of a layer 1 unit, and he/she is not only working on the subject from his original layer 1 unit, but also the subjects from other members in the layer 2 unit. All the members work on the subjects has to be approved by the majority of the members in the corresponding unit through voting.

Dotted lines ₄316, ₄322 represent multiple intermediate layers (not shown) and subjects (not shown) towards the highest layer N units and layer N subjects. Each layer follows the same rules.

Information Products

The consolidated results at each layer through SOwiki structure all possess a certain value to the targeted groups of users. For instance, the news category at each level and sub category area (i.e. communities to town, city, global) are of a value to the users that are covered by this layer or area; in the professional fields, the contents at each layer and field are of value to the users in the targeted field, Therefore, newspapers series that cover different areas, fields or levels ₄403 can be produced naturally from the bottom to up.

The information that is filtered from Internet sources, such as Facebook or Twitter, using SOC methods may be presented in the form of news scroll ₄405, and distributed at any time through wireless network, mobiles etc, hence becoming the new media to satisfy the needs of community communication, city life, public entertainment, and the like.

Automatic searching is mainly conducted based on letters or characters by machine which is very limited in terms of assessing and ranking audio/video program where the use of human intelligence has preponderant advantage. In addition, the selected programs can be edited or consolidated using SOwiki methods and presented/distributed in the forms of various web “Audio/Video” stations ₄407.

Assessing and filtering the information that are provided by participants ₄201, SOwiki members (acting as editors) can obtain accurate, comprehensive, up-to-date information and create various guides ₄404 to satisfy the needs of users in various fields (traveling, medical insurance, consumer reports, interests, etc.).

The attributes that SOC-SOwiki methods to consolidate information from different branches layer by layer, will attract many users to collaborate in a structured way for collaborative projects ₄406 such as surveys, subject study, collective writing, magazine editing, translation, etc.

The final products will be distributed through SOC-SOwiki Platform ₄410 so that network, users, such as Internet users ₄411 can take advantage of its information to create various business models.

Technical Support

The SOIPS has a number of administrative functions. The products (or the extension of the products) created by the members of SOC-SOwiki will be credited by the module of “Credit Points Management System” ₄501 (crediting algorithm is predefined and agreed by SOC-SOwiki). The Financial System ₄503 will distribute the revenue among members based on the credit points they contribute.

Because a user can join multiple structures with different subjects, or be selected as a leader of any units that might not be at the same level, ₄502 is a powerful ID management System to manage the complex member IDs and the permissions related the user's ID and corresponding access level.

The Self-Organization Information Process System is a platform which supports SOC-Sowiki structures to process information independently and respectively in order to create their own information products ₄402. However the database tools ₄504 allow the database to be sharable to make structure reorganization or transition easy.

Functionalities of SOC And SOwiki System

The FIG. 5 demonstrates the functionalities of SOC and Sowiki System. The platform supports all the functions needed to create/operate SOC applications (covered in the dashed-line frame ₅300 and as well as SOwiki applications (covered in the solid line frame ₅400). Functions of SOC system are the subset of SOwiki system.

Members of SOC or SOwiki structures come from network users, such as Internet users ₅200. The sources of information ₅100 are either created or collected from the network, such as the Internet by members. Various applications/products ₅780 can be created/implemented by taking advantage of SOC or SOwiki functions.

SOC ₅300

A member management module ₅310 provides the functions for users to grow SOC by recruiting people from outside through its lowest/base level by invitation or self-introduction. A voting process will be prompted for the unit that prospective member is intended to join, and the prospective member will become member officially and assume all the responsibilities and rights if the majority of the unit vote in favor of the prospective member joining the unit. The module also provides the function to develop restrictions over memberships in addition to regular membership management.

A system set-up module ₅303 provides the functions to set system parameters. A series of parameters need to be taken into consideration to start a system. The system set-up module provides default values, but founders/initiators of SOC or SOwiki structure have the option to either use default values or to provide values they prefer. It also provides tools and processes for members to determine/reset parameter values at any phase. Whenever there is a proposal to reset parameter(s) and the required motion second minimum number of members seconds the motion to change given parameters, the system will prompt a voting process. The parameter(s) will be reset if certain percentage (default value: ½) of all the members, and of the leaders (default value: ⅔) at the highest layer vote in favor.

An election module ₅302 provides the functions for members to elect leaders. Progressing from bottom up, each unit elects its leader by voting. That elected leader is then a member of the next immediately higher layer. Any member can propose a motion for re-election of its unit leader at any time, and responsibilities and rights of the position will be automatically transferred from the old leader, if the old leader loses the election, to the newly leader-elect if a majority (or a value as pre-defined) vote in favor of the new leader.

A unit splitting module ₅304 provides functions to split a unit when the unit reaches ñ (maximum size of a unit, a parameter defined in system set-up), a splitting process will be prompted by the system. If there is upper layer on top, the unit will split into no less than n (the minimum size of a unit, a parameter defined in system set-up) new units, each of which should have no less than n members.

A layer growing module ₅305 provides functions to grow layers of SOC and SOwiki structures. When a unit reaches ñ (maximum size of a unit, a parameter defined in system set-up), it will be split into at least n (the minimum size of a unit, a parameter defined in system set-up) new units. The elected leaders of each of the new units then form a new unit of a higher level, and hence a new layer, if it does not already exist. The units at higher level can grow new layers from up and down as well as shown in FIG. 2.

A voting module ₅306 provides functions for members to cast votes. Voting can be conducted within a unit, or as referendum within a branch or whole system/structure for the purpose of decision making on various matters. The weighted votes are automatically calculated, and the results are the keys to automatically turn on/off related rights that result from the election.

A blog module ₅307 creates and provides functionality to each blog of the system. Each member is provided with personal blog and the opinions or activities of this person are presented and recorded in this blog. Each leader is equipped with position blog and the opinions or activities related to this position are presented and recorded in this blog.

A forum module ₅308 creates and provides functionality to each forum of the system. Each unit is provided with internal forum for unit members to deal with internal affairs through discussion or decision making (voting or electing); each branch is provided with internal forum for its members to submit/view inputs and provide feedbacks, and as well, to conduct referendum within it.

A reorganization module ₅309 provides the functions to create dynamic and rich forms of SOC structures through unit or branch transferring, merging, seceding or affiliating within same structure or among different structures.

Sowiki ₅400

A member management nodule ₅401 provides functions to support Sowiki's methods of absorbing new members. Sowiki absorbs new members mainly through self-introduction by way of a prospective member's participation by providing inputs through Wiki at the base layer, and will then become member if the majority of the members of the unit that the prospective member is intended to join vote in favor for the inputs/content submitted by the prospective member. The members who have been inactive for predetermined time will be categorized as inactive member and won't be included in the calculation of vote weight.

A wiki module ₅402 provides the functions for members to create, provide, or revise information in the system.

A wiki consolidation module ₅403 provides functionality to review and consolidate contents based on voting. Content that is created, provided, or updated is provisionally stored pending for review. The content will become effective or not according to the voting of the unit that the contents belong to.

A unit creation module ₅404 provides the functions for members to create subordinate new unit, and supports the methods of unit management. For example a new unit will not be eligible to vote if the number of its members is less then n (the minimum size of a unit, a parameter defined in system set-up). The unit's right of voting will be surrogated by its upper unit and be restituted to the unit once the number of the members reaches ≧n.

A content re-organization module ₅405 provides functions to support SOC structure re-organization, this module provides the functions for members, using Sowiki methods, to reorganize the Sowiki structures as well as the contents resulting from such restructure.

One or more application program interfaces (APIs) ₅601 and ₅ 602 may be provided. The APIs allow user to implement their own programs to be used in the SOC-SOwiki platform or in conjunction therewith.

It will be understood that the structures and information presented above may be saved in computer database in any format known in the art. In some embodiments, each unit of the structure has unit record ₆640 stored in a computer datastore, such as a database. The unit record or structure has a unit ID section ₆641, a superior unit section ₆642, a leader section ₆644, a project(s) section ₆644, and a history section ₆645. The unit ID section contains a unique unit identifier. The superior unit section ₆642 contains the unit ID which the unit is subordinate to in the next immediately higher layer. The leader section ₆643 contains the name or unique identifier of the member that is the leader of that unit. The project(s) section ₆644 contains one or more projects or goals of the unit. The history section ₆645 contains a transaction history of events occurring in the unit, such a votes on leadership of the unit, votes on any topic in the unit, the joining of members to the unit, the exiting of members from the group, information on whether results or content submitted by the unit to superior unit was accepted or rejected, or the like.

One skilled in the art will recognize that not every section of the unit record ₆640 is necessary to implement the invention. For example, in some embodiments, the hierarchal structure of the SOC or the SoWiki is represented in a relationship table ₆630. As shown in FIG. 6, the table has a unit column ₆631 and a superior unit column ₆632. Therefore, for each unit in the unit column, that unit's immediately superior unit is recorded in the superior unit column of that row. The example shown in FIG. 6 provides that a first layer having units 1, 3, 4, 5, 8, 9, 11, 12, 13, and 14, a second layer having units 2, 6, and 10, and a third layer having unit 7. Units 1, 3 and 8 in the first layer are subordinate to unit 2 in the second layer; units 4, 5, 9, and 11 are subordinate to unit 6 in the second layer; and units 12, 13, and 14 are subordinate to unit 10 in the second layer. Units 2, 6, and 10 in the second layer are subordinate to unit 7 in the third layer. The value 0 in column ₆632 across from unit 7 indicates unit 7 is presently in the top layer with no other units superior to it. Other values can be provided to show a top layer unit. Units 1, 2, 3, 7, and 8 comprise one branch of the structure. Units 4, 5, 6, 7, and 9 comprise a second branch of the structure. Units 10, 12, 13, 14, and 7 comprise a third branch of the structure. Other sub-branches can be described from this structure and others. Therefore the structure of the SOC and the SoWiki can be represented in a flat relationship table. Other associations between units can also be shown in a table in a similar manner, such as an affiliation between units as explained about with reference to FIG. 3. In other embodiments, the SOC and SoWiki structure is represented by other relationship recording structures in a computer datastore, such as a database, flat file, or other computer data structures known in the art.

In some embodiments, each member of any unit of the structure has member record ₆610 stored in a computer datastore, such as a database. The member record ₆610 has a record ID section ₆611, a member name section ₆612, a password section ₆613, a unit membership ₆614 section, and a leadership section ₆615. The record ID section ₆611 contains a unique user record ID value. The member name section contains the member's user name. In some embodiments, all member user names are unique, in which case the record ID section is not used and instead the member name section is relied on for identification. The password section contains authentication information such as a password. The unit membership section contains information about which units the member has a membership in. The leadership section contains information about which units that a member is a leader of.

One skilled in the art will recognize that not every section of the unit record ₆640 is necessary to implement the invention. For example, in some embodiments, a members unit membership information is represented in a user table ₇650. Member ID's are listed in the member ID column ₇650 for each member of the SOC or SoWiki structure. In unit column ₇652 each unit of which the member has membership in is listed. In leader column ₇653 each unit that the member is a leader of is listed. Therefore member ID 00002 is a member of units 2 and 7 and is a leader of unit 2.

The forgoing SOC, SoWiki, and SOIPS and any step, function, module, or method described above may be implemented as instructions on a programmable general computer, or across multiple computers, capable of carrying out the instructions to achieve the step, function, module, method, or result indicated. In some embodiments, the general purpose computer has a processor signal connected to a memory, an input/output device, and a network adapter. The general purpose computer may be a service connected to a database. The general purpose computer may be accessible over a network, such as the Internet.

From the foregoing, it will be observed that numerous variations and modifications may be effected without departing from the spirit and scope of the invention. It is to be understood that no limitation with respect to the specific apparatus illustrated herein is intended or should be inferred.

Claims

1. A computer implemented method of completing a project, comprising the steps of:

receiving an input for a unit project in a unit in a present layer of an organizing structure maintained in a computer readable medium, the unit having a unit minimum number of members;

prompting an input vote of the members of the unit whether to accept the input; and

sending the input accepted for the unit project to a superior unit in a next layer above the present layer of the organizing structure if said superior unit exists.

2. The method of claim 1, comprising the step of:

repeating the step of receiving, prompting, and sending in each successive layers of the organizing structure if there exists a superior unit above the unit sending within a branch in the organizing structure.

3. The method of claim 1, comprising the step of establishing the organizing structure by:

forming a plurality of units in the layer, each unit having at least the unit minimum number of members;

prompting an election in each unit, by a election vote of the members of the unit, one member of the unit as a leader for the unit; and

promoting the leader of each unit to membership in the superior unit in the next layer above the present layer if said superior unit exists.

4. The method of claim 1, comprising the step of repeating the steps of receiving, determining, and sending in each successive layer of the organizing structure so that hierarchal tree of units are formed, the organizing structure having a plurality of layers and a plurality of said units on each layer below a top layer; each unit located below the top layer has only one an immediately superior unit; each unit above a base layer has at least three immediately subordinate units.

5. The method of claim 1, wherein the step of receiving an input comprises the step of receiving an input selected from the group consisting of: new input and modification of previously submitted input.

6. The method of claim 1, wherein the step of receiving an input comprises the step of receiving an input from one of the members of the unit.

7. The method of claim 1, wherein the step of receiving an input comprises the step of receiving an input from a nonmember.

8. The method of claim 1, wherein the step of receiving an input comprises receiving input about one or more objectives of the unit project of the unit.

9. A project management computer system comprising:

a computer system having stored thereon,

a datastore configured to hold an organizing structure comprising one or more units in a layer of a hierarchal tree of units, each unit having at least a unit minimum number of members, each unit having a unit project;

a project deliverable acceptance function configured to accept by a unit one or more unit project deliverables when a pass number of members of the unit approve the one or more unit project deliverables;

a leader election function configured to prompt an election, among the members in each unit, of one member of the unit as a leader for the unit;

a hierarchal expansion function configured to promote the leader of each unit to membership in a superior unit in a next immediately superior next layer of the organizing structure; and

a project delivery function configured to submit unit project deliverables of each of the one or more units to the corresponding unit's superior unit when the superior unit exists.

10. The system of claim 9, wherein the organizing structure comprises a plurality of layers and a plurality of said units on each layer below a top layer; each unit below the top layer has only one an immediately superior unit; each unit above a base layer has at least three immediately subordinate units; units at the top layer have no superior unit, units in a branch of the organizing structure have at least one upper unit in common.

11. The system of claim 9, comprising, a unit splitting function configured to split one of the units into a predefined minimum split units number of units and to allow members of the unit split to associate with the units resulting from the split.

12. The system of claim 9, comprising a member invitation function configured to invite a non-member to become one of the members of a base layer unit when the non-member provides a submission to the unit project of the base layer unit and the base layer unit accepts by a favorable vote of a predefined number of members of the base layer unit receiving the submission.

13. The system of claim 9, comprising a history recording function configured to record in the datastore actions occurring within each unit.

14. The system of claim 9, wherein each unit comprises a unit communication forum for facilitating communication among members of the corresponding unit.

15. The system of claim 9, comprising a vote weighing function for weighing a vote of each voting member in a unit above a base layer, wherein a vote weight of the vote of each voting member is equal to the number of members a branch of the structure subordinate to the unit in which the voting member is voting.

16. A distributed work allocation computer system comprising:

a computer system having stored thereon,

a datastore configured to hold an organizing structure comprising one or more units in a present layer, each unit having at least a unit minimum number of members, each unit having a unit project;

a project deliverable acceptance function configured to accept by a unit one or more unit project deliverables when a pass number of members of the unit approve the one or more unit project deliverables;

a leader election function configured to prompt an election, among the members in each unit, of one member of the unit as a leader for the unit;

a hierarchal expansion function configured to promote the leader of each unit to membership in a superior unit in a next layer of the organizing structure above the present layer when the present layer has at least the a minimum number of units; and

a project delivery function configured to submit unit project deliverables of each unit of the one or more units to the corresponding unit's superior unit when the superior unit exists.

17. The system of claim 16, wherein the organizing structure comprises hierarchal tree of units, the organizing structure having a plurality of layers and a plurality of said units on each layer below a top layer; each unit below the top layer has only one an immediately superior unit; each unit above a base layer has at least three immediately subordinate units; units at the top layer have no superior unit, units in a branch of the organizing structure have at least one upper unit in common.

18. The system of claim 16, comprising a unit splitting function configured to split a unit into a predefined minimum split units number of units and to allow members of the unit split to associate with the units resulting from the split.

19. The system of claim 16, comprising a transferring function configured to transfer a portion of the organizing structure from a first node to a second node of the organizing structure, wherein the first node is a first branch of the organizing structure or one of said one or more units, and the second node is a second branch of the organizing structure, when an first node application by the first node receives a transfer minimum number of votes from members of a senior unit of the second node.

20. The system of claim 16, comprising:

a merging function configured to merge a portion of organizing structure from a first node into a second node of the organizing structure, wherein the first node is one of said one or more units or a first branch of the organizing structure, and the second node is one of said one or more units or a second branch of the organizing structure, when an application by the first node receives a merger minimum number of votes from members of a senior unit of the second node;

a seceding function configured to secede the first node from the organizing structure when a predefined seceding number of members of a the first node vote to secede; and

an input affiliating function configured to affiliate a plurality of units of said one or more units wherein leaders from affiliating units become members of a resulting affiliated unit.