I'm working on a project with a typical scenario where authors are maintaining content on internal network (let's call it InAuthoring) and uses "content deployment" feature to flush the content to internet facing network (let's call it InProduction).
The twist is, a part of our application lets "end user" change/add content of a list InProduction.
The challenge is to keep this list InAuthoring syncronized with InProduction. And remember that there is a content deployment that is scheduled to run let's say every day.
One of the scenarios for this list is: 1. A particular listItem (say id=3) is changed InProduction. Same listItem (id=3) has been changed InAuthoring. On content deployment, changes InProduction will be overwritten.
My first thought was to have a webservice running InProduction, get the changed data InAuthoring and update the list (sync.). But following are the drawbacks of the solution:
- I saw this as a manual process, but content deployment is scheduled.
- If there is a long time span between sync. and content deployment, you might endup overwriting some data InProduction anyway.
- If there are new items added InProduction, then after sync. and content deployment you will endup having duplicates InProduction.
Is there a way to exclude specific list from content deployment?
I really hope someone has already been through this situation will guide me to be able to find a stable solution. Anyone out there with bright ideas?