nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Content Migration VCM 7.6 -how to deal stale content

Prakash_Chaudhary

We are migrating content from current CMS on OS AIX onto a newly build CMS on Linux OS - version 7.6

There is a special case we want to cater to and that is "migrating Stale" content.

Problem : "Stale" content in the management stage .
Since the vgnexport/vgnimport is run against the management stage DB. This utility also brings in the stale content (which it should anyways)

However we want the version of the content which is live (which is sitting in the delivery stage schema's)
SO my Question:
1) Identify the stale content - we can with some success using SQL/programatic

2) Once identified How do we get the "content version" which is in the live stage into the CMS .

We cannot publish any content which is stale.

Please also note there is no version/audit for the system.Cannot use Vignette Transfer Tool as the OS is different.
Please let me know if you need more clarification.

Cheers

Prak

Find more posts tagged with

Comments

William_Thayer

There are several solutions to this. Whenever dealing with migration and export/ import there are always issues. I'd approach this publish issue in phases. Initially, try to export/import all of the content from the old system to the new system. The exports you take should be date stamped. Ideally you run a full export on a quiet day like the weekend (example 1/5/13). Then those exports are imported successfully after a few days or a week into the new system. It's important to get a date stamp because you'll use this to get any content that changes while people use the old system (update, delete, added).

Now identify all of the stale content from the 1/5/13 export. You can do this via SQL, as well as compare content to delivery. Hopefully the items identified have "versions", which you can fall back to but I've never seen vgnexport handle versions of content. I believe vgnexport only exports the current version, no history. Depending the scale of "stale" content you could write an API script that makes the "published" version current then export that version into the new system. You could try to just update the content via sql on the new via the delivery DB, but I'd be careful with that (backups).

Finally, you could approach this from a management perspective. Before live, the business MUST publish all content associated to channels. This way, there isn't any misunderstanding. You could even provide them a list of content that needs to be published. They might push back a little - but you could even make it easier for them by saving their updates/ as well as presenting a list of all the stale content. This way, you have a clean new system - with all content published - and you have a backup of all the stale content. With this scenario - you'd just run an import of the stale content after the new system is live, published, approved. Then the users have their stale content when they go back to work on the new system.

On Thu, Dec 6, 2012 at 11:14 PM, eLink Entry: Discussion Group - Web Experience Management <v7webcontentmanagement@elinkkc.opentext.com> wrote:

Content Migration VCM 7.6 -how to deal stale content Posted byprakash_chaudhary_2@amp.com.au (C, Prakash)On 12-07-2012 01:11

Hi We are migrating content from current CMS on OS AIX onto a newly build CMS on Linux OS - version 7.6

There is a special case we want to cater to and that is "migrating Stale" content.

Problem : "Stale" content in the management stage .
Since the vgnexport/vgnimport is run against the management stage DB. This utility also brings in the stale content (which it should anyways) However we want the version of the content which is live (which is sitting in the delivery stage schema's)
SO my Question:
1) Identify the stale content - we can with some success using SQL/programatic 2) Once identified How do we get the "content version" which is in the live stage into the CMS .

We cannot publish any content which is stale.

Please also note there is no version/audit for the system.Cannot use Vign! ette Transfer Tool as the OS is different.
Please let me know if you need more clarification. Cheers Prak
[To post a comment, use the normal reply function]
Forum: Discussion Group - Web Experience Management
Content Server: Knowledge Center

--
Will Thayer
Senior Consultant | Avalon Consulting, LLC
P: 720 480 2163 | M: 720 480 2163

William_Thayer

On Thu, Dec 6, 2012 at 11:14 PM, eLink Entry: Discussion Group - Web Experience Management <v7webcontentmanagement@elinkkc.opentext.com> wrote:

Content Migration VCM 7.6 -how to deal stale content Posted byprakash_chaudhary_2@amp.com.au (C, Prakash)On 12-07-2012 01:11

Hi We are migrating content from current CMS on OS AIX onto a newly build CMS on Linux OS - version 7.6

There is a special case we want to cater to and that is "migrating Stale" content.

Problem : "Stale" content in the management stage .
Since the vgnexport/vgnimport is run against the management stage DB. This utility also brings in the stale content (which it should anyways) However we want the version of the content which is live (which is sitting in the delivery stage schema's)
SO my Question:
1) Identify the stale content - we can with some success using SQL/programatic 2) Once identified How do we get the "content version" which is in the live stage into the CMS .

We cannot publish any content which is stale.

Please also note there is no version/audit for the system.Cannot use Vign! ette Transfer Tool as the OS is different.
Please let me know if you need more clarification. Cheers Prak
[To post a comment, use the normal reply function]
Forum: Discussion Group - Web Experience Management
Content Server: Knowledge Center

--
Will Thayer
Senior Consultant | Avalon Consulting, LLC
P: 720 480 2163 | M: 720 480 2163

Prakash_Chaudhary

Thanks Will

We have had success in identifying the Stale content SQL/API's, we are in the process of export import.

The real challenge is in restoring the published version .

As mentioned earlier we don't have any versioning system not through the listeners or in other ways.

In this case vgnexport only gets the stale content from the management stage DB how do we get the published version from the delivery stage DB and still import it into the cms and maintain all the relations .

Cheers

didier_alves

Hi,

Indeed, vgnexport won't let you export contents from a delivery stage. However, I have had this problem several times as I have participated in several content migration projects since V6 to V8. We have found a solution though.

I work at VILT (www.vilt-group.com). VILT is a specialized VCM company and OpenText partner and we have worked on migration projects world-wide.

We have developped a tool called VILT Motion (http://www.opentext.com/2/global/partnersolutionscatalog?sys_action=details&solutionid=a10D0000000lEKnIAM) that is able to recover contents from a delivery stage and import them into a management stage. The tool also supports several other use cases like getting the last modified objects since a specific date. This is very useful to synchronize VCM platforms.

Also, we have setup delivery stage synchronization procedures. They allow us to publish only the contents/channels that were published in the source environment.

Please let me know if you are interested. We could set a call and discuss this.

Regards,

Didier (didier.alves@vilt-group.com)

William_Thayer

HI,

I think SQL is the answer, and comparing delivery DBs. I know OT has a versioning package - that does you little good at this point though. Have you opened a ticket with OT? Usually when you start a migration / upgrade process OT recommends opening a ticket to keep them in the loop - also with any gotchas they are there to help. In the past, I've done a lot with SQL to get around issues like this.

Alternatively, you could hire professional services or another OT partner (my company is a partner too).

Let me know if you want to touch base, I can be reached at thayerw@avalonconsult.com

Will

On Mon, Dec 10, 2012 at 9:22 PM, eLink Entry: Discussion Group - Web Experience Management <v7webcontentmanagement@elinkkc.opentext.com> wrote:

Re Content Migration VCM 7.6 -how to deal stale content 2 Posted byprakash_chaudhary_2@amp.com.au (C, Prakash)On 12-10-2012 23:16

Thanks Will We have had success in identifying the Stale content SQL/API's, we are in the process of export import. The real challenge is in restoring the published version . As mentioned earlier we don't have any versioning system not through the listeners or in other ways. In this case vgnexport only gets the stale content from the management stage DB how do we get the published version from the delivery stage DB and still import it into the cms and maintain all the relations . Cheers P
[To post a comment, use the normal reply function]
Topic: Content Migration VCM 7.6 -how to deal stale content
Forum: Discussion Group - Web Experience Management
Content Server: Knowledge Center

--
Will Thayer
Senior Consultant | Avalon Consulting, LLC
P: 720 480 2163 | M: 720 480 2163

Prakash_Chaudhary

Thanks we are in the final stages we have managed to identify most of the content which are stale.

Tricky part was restoring the version from Delivery DB and probably we may go for a manual change /restore process.

Cheers