Perhaps a model along this line would work.
One storage location - primary
All links go to this primary location.
When new primary is generated, all links shift to new primary with a
backlink for old primary.
Offshoots or various edits become satellite mini-primaries. Satellites
are sortable by popularity. Content of popular satellites are
incorporated into primary.
Goal: Produce primary repository. Allow for editing and historical
content. Successful edits are eventually incorporated into primary
based on criteria such as popularity.
Rogue satellites - no link to primary - mean uncontrolled information
which may pull traffic links from primary. Perhaps partially reclaimed
by linking from primary to rogue in an offshoots page.
Alan
Frank Peters wrote:
marbux wrote:
Background: An IT principle (actually, it's older than that) is to
store any one piece of information in only one place. A consequence
of violating this principle is confusion for the users when they
notice differences among multiple sources. A worse consequence is
that they make decisions based on obsolete information, which
errors could have been prevented simply by
Like marbux noted, this is an ideal hardly ever reached. This would
also require everyone to have access the one location that holds
the information.
Instead, we need to think about one information source and different
delivery formats. The source being in one single place where ideally
users can contribute to it. The delivery format would allow to
distribute the information in accordance to the user's needs.
Yeah, that's what we need. Concrete suggestions. This one would be
relatively easy to implement once we have the help on the wiki
for collaboration. Add a link on every help page that points to the
corresponding wiki page to allow for discussions, fixes, amendments.
Jim, marbux thanks for this great discussion
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
