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

about vaklidity of dcr-type='iwov'

curiousmaverick

Moving forward as we are planning upgrade our TS version from 6.5 SP3 to 6.7.1, I'd like to know whether we can continue using dcr-type='iwov' in our datacapture templates or is there a need to convert them to dcr-type='xml' format?

Regards,
Mav

Find more posts tagged with

Comments

sasikumarg

You can go with iwov format itself..absolutely no problem..

sara_team

hi... u can sustain with iwov format. But xml format is highly recommended in the later releases. Keep this..

curiousmaverick

I've seen that they recommend xml format. But that means a lot of rework for us.I wanted to know about the risk factor associated with continuing with the 'iwov' format.

Regards,
Mav

Adam Stoller

I've seen that they recommend xml format. But that means a lot of rework for us.I wanted to know about the risk factor associated with continuing with the 'iwov' format.

Regards,
Mav

The risk factor is that you may not be able to take advantage of newer functionality / features and that it's possible (but not too likely) that IWOV might stop supporting the "iwov" format (again, the last is a pretty low risk IMO)

ISCBorisB

I've seen that they recommend xml format. But that means a lot of rework for us.I wanted to know about the risk factor associated with continuing with the 'iwov' format.

Regards,
Mav

Unless you are planning to use LiveSite you can safely ignore this recommendation, probably for many years to come.
IWOV -> XML Conversion "con's" are painful and obvious, "pro's" simply do not exist (not yet, anyway)

JMcNeil

I would suggest using the xml type for any future DCT you create, and continue to use iwov for your existing DCTs until a problem presents itself

chicka

Hey guys,
I am having a query related to this thread. Suppose if I am changing my DCR type to XML from IWOV, is there any CLT to convert the existing DCRs in the store from old format to new format.
Please shed light on this.

ISCBorisB

is there any CLT to convert the existing DCRs in the store from old format to new format

No. There is no such animal, that's the whole point.

Without external (e.g. coming from somewhere outside of TS) IWOV DTD - XML DTD Mapping information this sort of transformation is impossible to do even theoretically.
Note that this *mapping* would have to be provided per Type

nipper

True but that is an interesting point. Using the DCT could one write a general purpose converter ? It should be pretty easy to write a custom 1 off conversion utility, specific for a single type of DCR.

ISCBorisB

True but that is an interesting point. Using the DCT could one write a general purpose converter ? It should be pretty easy to write a custom 1 off conversion utility, specific for a single type of DCR.

Sure we can (you and I Smiley Happy

. Note however that you've made an assumption that seriously simplifies the problem.

Let's spell it out: "Boris, the mapping you are talking about is implied in your datacapture.cfg!" Alas, it is rearly
the case. What you can do with it is something like the following (on the lowest hierarchical level):
[html]
foo

foo

[/html]and that's just about all you can do. Note that even in this simplest example it is an open question if it should be a) or b).
Without extra information Script itself has no way of knowing. Regardless, if that's all we need, we might as well stay with IWOV format IMO.

curiousmaverick

A few questions from my side---

1. There are 1000 plus DCRs. So if I migrate from IWOV to XML, I'll need to create those all over again?
2. Correspondingly, Changes have to be made in PT as well?
3. Will it require update in database schema as well(Datadeploy is in place)?

Regards,
Mav

ISCBorisB

A few questions from my side---

1. There are 1000 plus DCRs. So if I migrate from IWOV to XML, I'll need to create those all over again?
2. Correspondingly, Changes have to be made in PT as well?
3. Will it require update in database schema as well(Datadeploy is in place)?

Regards,
Mav

1. Yes. One way or another (eg, manually and/or with some scripts) you would have to transform IWOV Format into XML.

2. Depends. In any case, you are looking at massive regression testing. That should include pretty much every piece of
non-OOTB code: PTs, FormAPI, CGI, JS, Java/JSP, PMs, Open/Data Deployments and Workflows. That is not to say you would
have to modify all of it (or even any of it!). You would have to test your overall CMS implementation though and fix
what's broken.

3. Depends. If you do not go overboard with your custom DTDs, DB Schema proper can (usually) survive. DB population
mechanisms and stored procedures may be another story, see above.

That's serious resource investment, may I ask what are you planning to gain from all that?

Adam Stoller

1. Yes. One way or another (eg, manually and/or with some scripts) you would have to transform IWOV Format into XML.

2. Depends. In any case, you are looking at massive regression testing. That should include pretty much every piece of
non-OOTB code: PTs, FormAPI, CGI, JS, Java/JSP, PMs, Open/Data Deployments and Workflows. That is not to say you would
have to modify all of it (or even any of it!). You would have to test your overall CMS implementation though and fix
what's broken.

3. Depends. If you do not go overboard with your custom DTDs, DB Schema proper can (usually) survive. DB population
mechanisms and stored procedures may be another story, see above.

That's serious resource investment, may I ask what are you planning to gain from all that?

If the original item names were created "correctly" (i.e. no white-space) than transforming them into "xml" style should (I believe) result in identical "path" references as far as PTs, FormAPI, and DD are concerned and thus not require modifications to those aspects of the overall design.

Custom code using TeamSite::XMLnode and/or other XML parsing modules would probably have to be updated since the names that you would be referencing for the nodes would now be element names instead of attribute names (for the items) and you wouldn't have to find the 'value' element, just the value (CDATA) of the 'item' element.

If your "iwov" style DCTs were written in the often-seen "broken" manner - in which item names were made to be "friendly" instead of using the label element - e.g.:[html][/html]instead of the more correct:[html]
Page Title[/html] - then yes, you'll have to make a bunch of changes to your PTs, FormAPI, and DD code - in addition to any custom code that parses the XML.