RE: CMS vs. Wiki
Dierk Seeburg <dierk_seeburg-E0T7EY2UX4gpIyhaTEd/[email protected]>
| Newsgroups | gmane.comp.cms.cms-forum.general |
|---|---|
| Organization | Choice Hotels International, Inc. |
| Message-ID | <[email protected]> |
[email protected] wrote: > Message: 2 > Date: Thu, 3 Feb 2005 12:27:43 +1100 > From: "Ben Noblet" <[email protected]> > Subject: RE: [CMS] CMS vs. Wiki > To: <[email protected]> > Message-ID: <200502030128.j131S32O023724-fruN6kYK4IGHE5RDhafnnkFrd++jNZG9AL8bYrjMMd8@public.gmane.org> > Content-Type: text/plain; charset="us-ascii" > > >>>I was contemplating the collaborative aspect for our purposes and >>>appreciate your pointers. We need to manage a number of >>>records in a database > > >>It sounds like you already have the database? If so, then I >>think all you need is someone to write a web interface to >>allow you to view and update the records. > > > Some big-end CMS vendors have tools to integrate stuff that is stored in an > existing database. But these tend to be incredibly complex and expensive to > implement. If that's all you need from the product then it would definitely > be overkill. > > A wiki would be no good at dealing with structured data in a database. > > I'd agree with Darrel - get someone to build you some forms and processing > logic. > > Cheers > Ben Right, at the point where a Wiki handles structured data it seems to me to approximate a CMS. Part of my hope was that I could do what's needed myself with a Wiki which would make it faster to implement, and I would have tight control over it, but that appears impossible now. Thanks for your input! Cheerio, Dierk