Chris;
This problem is exactly what we have built a solution for in publishing
Spank! Youth Culture Online (http://www.spankmag.com). We are also beginning
to market the engine as a product called Lopedia.
There are several fields for each entry - but importantly, we strip out all
HTML and ASCII for submitted material (security reasons) and replace with a
pseudo-code that we parse back with each story (submit a response to a
thread - there's a link that shows all the pseudo-code). This way, we can
change the parser to modify the look and feel of the text. This is also how
we have the first word of each paragraph in the Spankopedia section (not the
forums) Bold and +1 size.
We are slowly moving over 350 old, full length features into the database
from raw HTML files. Let's just say - If I had these in a database to begin
with (OK - we started back in 1995), I would be a much happier boy.
One thing though - I don't use fusebox and don't like the methodology all
that well (OK - let the flames begin - you people do seem a little religious
about dissenting voices), but it's a matter of personal choice. Do though DB
it all. Right now. From the beginning.
Stephen R. Cassady
Publisher & Cofounder, Spank! Youth Culture Online
wb. http://www.spankmag.com
em. [EMAIL PROTECTED]
About Spankmag.com!
---------------------------------------------------------
Launched 01 November 1995, Spank! Youth Culture Online is a flagship quality
youth online-lifestyle magazine (<http://www.spankmag.com>), and the very
first-ever of it's kind. Spank!s online services offer users cool reviews,
informative features, opinions, contests, cartoons and areas to express
their own thoughts and ideas.
At the heart of Spank!s services is original, fresh, content built by a team
of editors from North America and around the world. True to it's nature,
Spank! leverages this talent into a peer to peer meeting of youth (14 - 26)
from around the world. Free of censorship, open to ideas, Spank! weeds out
the parental guidance side found in most youth journals designed by adults.
Spank! is the playground and stepping stone for youth.
For more information please contact us directly @ Stephen Cassady,
[EMAIL PROTECTED]
Date: Sat, 16 Sep 2000 12:08:23 -0800
From: "Chris Lott" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Re: Upload and retrieval of stories?
Message-ID: <024e01c02019$de0a92c0$6401a8c0@S003817>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
My new site is related to this thread, so I would like to hear
suggestions about the following issues. The site is largely dedicated
to serving out a selection of poems, essays, stories, etc. I am
trying to bridge the gap between relatively easy contributions and
adequate performance when serving the file (aren't we all?).
1) Should I store the text with HTML formatting? Most of the items
will have formatting needs (bold, italic, explicit line breaks, and
of course paragraph breaks) and short of some kind of custom
shorthand, HTML seems like the best way.
2) How should I deal with the input and splitting of longer stories:
should the user submit the html/text file and then I will have CF
split the file into different database entries using some algorithm
for a word count and then split at the nearest sentence or paragraph
break or ??
3) Could someone explain how I might create tables to handle the
split text? Should I just have a single table with
title, partnum, text and then when displaying check if there is more
than one partnum, or should I have a couple of tables?
I'm starting to wonder if I should do this with a db-driven site at
all :) But I've already been tied to doing a CF site with Fusebox,
though the methodology is largely irrelevant.
c
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
