We use metadata far more than pages and containers. Does FarCry have an
equivalent idea of metadata?
Geoff Bowers <[EMAIL PROTECTED]>
03/29/2005 04:40 AM
Please respond to spectra-talk
To: Spectra-Talk <[email protected]>
cc:
Subject: Re: Continuing on Spectra?
On Wed, 16 Mar 2005 15:34:25 -0500, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Part of our decision with my employer is a political one. Others in our
> system have been trying to force an Interwoven agenda for several years
> and only grudgingly accepted Spectra because it went OS and it is CF
> based. It will be a tough road for me to try to get them to accept
FarCry
> after the previous battles. If the migration is relatively easy that
would
> help.
I'm coming a bit late to this thread but I'm only an occasional
watcher of spectra-talk these days. For what its worth we've migrated
*many* clients from Spectra to FarCry. Spectra and FarCry have very
different underlying code bases but the theoretical approach in
several areas is the same. For example, FarCry has the concept of a
Content Object API, uses concepts like content types, publishing rules
and containers, PLPs and more.
The FarCry technical whitepaper is a good general overview:
http://farcry.daemon.com.au/index.cfm?objectid=83030D6E-D0B7-4CD6-F93F95E4A5FC429E
(I keep meaning to finalise this document :)
Migrating data from the Spectra COAPI is actually very straightforward
-- you create an equivalent content type and then write a script that
uses the FarCry API to create FarCry content objects for each Spectra
content object. The only real complication in data migration is
hierarchical information as there were several different approaches to
this in the Spectra world -- that said we've not encountered anything
too difficult in this area.
Unlike Spectra, FarCry is a solution out of the box that allows for
extensive customisation. Where Spectra was simply a toolbox, FarCry
offers a much clearer methodology for solving common CMS requirements.
This makes it relatively easy to pick up a working model and modify
rather than having to build everything from scratch.
If you are serious about considering FarCry as an option I'd be happy
to give any team an online Breeze presentation to run through the
various facets of the project and answer any burning questions. I've
got considerable experience in Spectra development so I'm happy to
field detailed migration questions. I'd also suggest you check out
the FarCry developer community and poll them for their thoughts on
FarCry and how its been used to meet their requirements:
http://farcry.daemon.com.au/go/support/mailing-lists
-- geoff
http://www.daemon.com.au/
PS. Did I mention Daemon offers commercial support for FarCry CMS from
instructor based training, annual support and priority support
agreements, mentoring and full scale development?!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Find out how CFTicket can increase your company's customer support
efficiency by 100%
http://www.houseoffusion.com/banners/view.cfm?bannerid=49
Message: http://www.houseoffusion.com/lists.cfm/link=i:17:5661
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/17
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:17
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.17
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
