Raymond,
IMO, this is one of the flaws of Spectra. The scenario Paul spells out is a
common, real world scenario that is poorly addressed in Spectra. The COAPI
will certainly support building tools to support this scenario, but a better
methodology should have been supported within Spectra itself. We wrestled
with this same issue ourselves for some time. I assumed that we simply
didn't understand the application and framework well enough to solve our
problems. Over time, however, we have determined that the combination of
containers, publishing rules and versioning implemented in the WebTop
offered a lot but, in some ways, it was too complex for the end users. The
underlying handlers didn't offer enough flexibility to minimize the
complexity.
Spectra seems to have approached the issue of staging and deploying content
changes on a monolithic level: everything changes all at once. It seems to
be geared toward content changing fairly infrequently, like weekly or
monthly. In my experience, change happens daily, hourly maybe, and is very
granular. Again, I'm talking Spectra and the WebTop as it comes out of the
box and not as it can be made to perform. That granular approach to
previewing content and then deploying is difficult to implement with the
tools provided.
Ed McLaughlin
SVMedia
940 South Ave West
Suite D
Westfield, NJ 07090
ph 908.789.4200
fax 908.789.4266
http://www.svmedia.com/
Strategic Internet Business Solutions
>>-----Original Message-----
>>From: Raymond Camden [mailto:[EMAIL PROTECTED]]
>>Sent: Tuesday, May 15, 2001 11:27 AM
>>To: Spectra-Talk
>>Subject: RE: Spectra Content Management?
>>
>>
>>Spectra does do versioning. It's not automatic, it's
>>something you have to
>>enable (which makes sense, you wouldn't want to version stuff
>>that doesn't
>>need versioning). As for staging, that is possible as well.
>>If you want to
>>stage a new version of content that is already live, you
>>could easily store
>>your edits in a temporary object and then copy the data over
>>when it is
>>approved.
>>
>>==============================================================
>>=========
>>Raymond Camden, Principal Spectra Compliance Engineer for Macromedia
>>
>>Email : [EMAIL PROTECTED]
>>ICQ UIN : 3679482
>>
>>"My ally is the Force, and a powerful ally it is." - Yoda
>>
>>> -----Original Message-----
>>> From: Paul Horos [mailto:[EMAIL PROTECTED]]
>>> Sent: Sunday, April 15, 2001 1:21 PM
>>> To: Spectra-Talk
>>> Subject: Spectra Content Management?
>>>
>>>
>>> I'm in the process of trying to set up an article
>>publication system and
>>> have run into this problem: We need to be able to edit
>>content that is
>>> already live on the system, but not make it live until
>>after editorial
>>> approval. Added into this is the need to have all of these articles
>>> versioned. Apparently I was mistaken in thinking that
>>Spectra would handle
>>> most of these things automatically, but it now appears that this
>>> all must be
>>> designed from the ground up. Is this correct? If it is, does
>>> anyone have any
>>> suggestions about how to implement this in the best way? Also,
>>> are there any
>>> improvements concerning this in 1.5.1? Thanks in advance.
>>>
>>
>>
>>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
