http://wayuvato.t35.com/
___
General mailing list
General@developer.marklogic.com
http://developer.marklogic.com/mailman/listinfo/general
We have a system that needs to deal with articles going through staging stage
and production stage. Basically when article comes in, it stays in staging
stage. After a lot of operations and verifications the article gets published,
then at this time it will be moved to production stage. The
At some point I may have this situation: the article that is in production
stage, but there may be some very minor fix, and they don't want to pull it out
from production, so they just load another version into staging, after
verification, it will move to production again to replace the old
I would recommend a naming convention that indicates production vs. staging
articles. You could do this in conjunction with, or without, the use of
collections.
Clark D. Richey, Jr.
Principal Technologist, Federal
Mark Logic Corporation
1600 Tysons Blvd
Suite 835
McLean, VA 22102
Phone:
You already had one good use case where it won't be possible to do consolidated
search. Additionally, you are complicating the process of promoting an article
from staging to production as you now need to copy the article to a new
database. Having separate databases is a great tool when you
Hi Clark,
I got it. Thanks.
Helen
On Oct 11, 2010, at 3:21 PM, Clark Richey wrote:
You already had one good use case where it won't be possible to do
consolidated search. Additionally, you are complicating the process of
promoting an article from staging to production as you now need to
Rather than use different URIs,
Comomshttp://developer.marklogic.com/blog/introducing-comoms uses DLS to
maintain version history of a single URI and points collections at individual
versions on a URI.
This enables you to have the production site say always pointed at one
collection and a
This is an interesting way. I'll look and see how it can fit.
Thanks, Helen
On Oct 11, 2010, at 3:46 PM, Eric Bloch wrote:
Rather than use different URIs, Comoms uses DLS to maintain version history
of a single URI and points collections at individual versions on a URI.
This
