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; } } }

migrating dcrs in "iwov" format to "xml" format

Nityanada

we had dcrs which were of iwov type but now we want to have dcr type xml. Is there any Interwoven defined path for this

Find more posts tagged with

Comments

Adam Stoller

we had dcrs which were of iwov type but now we want to have dcr type xml. Is there any Interwoven defined path for this

There's no OOTB utility that will provide a simple means to do this. You'll have to revised the DCT and then change the PT and all of the pre-existing DCRs.

It's probably best to do this as a phased-in approach where you create a new data-type for the "xml" style of DCT (e.g.: "iwov" -> article, "xml" -> new_article) and then train the users to use the new_article data type and over time work on transferring the content from article DCRs into new_article DCRs of the same name, set to create generated files of the same name in the same location - as you do this, you can delete the old DCRs.

Otherwise you need to use something like XSLT or TeamSite::XMLnode (or various other things) to convert the old DCRs to the new format and hope your conversion works correctly and you don't accidently lose any original data.

Chirag Korde

Just on the same note do anyone have a sample XSLT to do this or a perl file?

Thanks

TroyP

There's no OOTB utility that will provide a simple means to do this. You'll have to revised the DCT and then change the PT and all of the pre-existing DCRs.

It's probably best to do this as a phased-in approach where you create a new data-type for the "xml" style of DCT (e.g.: "iwov" -> article, "xml" -> new_article) and then train the users to use the new_article data type and over time work on transferring the content from article DCRs into new_article DCRs of the same name, set to create generated files of the same name in the same location - as you do this, you can delete the old DCRs.

Otherwise you need to use something like XSLT or TeamSite::XMLnode (or various other things) to convert the old DCRs to the new format and hope your conversion works correctly and you don't accidently lose any original data.

I think we should be able to create a checklist to at least be able to change a DCT type from IWOV to xml. I the TS 6.7.1 sp1 developer guide there is a note that says when a dct is of xml type then the iw_value name attribute should be the dct item's id and not the name. I think that if you made all the id and name attribtes the same for every item in your DCT then you would be at least almost ready to change your DCT type to XML.

Another concern is if you have any containers that don't have a location. I am not sure if this is a valid concern. but would like to have other opinions.

A third consern is the fact that there is no garantee that replicants will be stored in order when a dcr is saved with an xml type.

I think this is an important topic so I am trying to stimulate the discussion more. Are there any other things to consider before changing a DCR type? I wold like to be able to change the type and then simpily re-save all my DCRs.

When I get back to my office I will upload a simple xsl that will let you test if there are items in your DCT whose name and id are not the same.