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

Import bulk htmls

Bhargav Coca

I am on TS6.5 sp3, i know this has been asked ziliontimes now. Is there a simple way of impoting bulk htmls(2500) and create a DCR corresponding to each html?

Thank you

Find more posts tagged with

Comments

gzevin

I am on TS6.5 sp3, i know this has been asked ziliontimes now. Is there a simple way of impoting bulk htmls(2500) and create a DCR corresponding to each html?

Thank you

I'd rather get them over samba drive/FTP, etc. As far as the script is concerned - I've just written such a script - it reads HTML tree, and dumps HTML into a DCR field (and also sets file name and location in the DCR as well). It's pretty simple.

Adam Stoller

I am on TS6.5 sp3, i know this has been asked ziliontimes now. Is there a simple way of impoting bulk htmls(2500) and create a DCR corresponding to each html?

Thank you

The complexity of transforming HTML into DCR depends on the degree to which the HTML is structured or commented and the degree to which you want the DCR to be structured.

If you just want to create a DCR with a big WYSIWYG textarea - then it should be pretty trivial.

If you want to create a DCR with distinct titles, headings, sub-headings, paragraphs, pictures, links, etc - then it is generally more complicated.

Bhargav Coca

I agree with you all. We had implemented this in the usual way of creating xmls from the htmls and then attach extended attribs to them and dump em in data folders. Its simple. Well i am confused on how to create xmls from htmls, there were no requirements given for stucturing our DCT, so i guess i will create a huge textarea which basically sucks in the entire html content.

Is this good way?, for me personally i do not like to do it this way. Looking for some alternatives.

Thank You

Adam Stoller

...
Is this good way?, for me personally i do not like to do it this way. Looking for some alternatives.

Thank You

"good" here is a subjective term - and thus can only be answered by the users of the system both in the short term (in which case they might not care as long as they can get their work done) and the long term (in which case their response may differ).

Personally, I agree - it is not the way I'd like to do things - in fact, I generally like to eliminate (as much as possible) WYSIWYG textareas in DCTs because I feel they tend to blur the separation of content and presentation and are all too often abused in that manner.

The alternative, if the HTML source is not well / uniformly structured is to either: (a) impose some structure on the HTML that you can programmatically use to extract and create structured DCRs, or more likely (b) go through copy/paste exercises where you get a bunch of folks (hopefully) to view the HTML in one window and the DCT in another and begin transcribing (either just typing or, more usually copying/pasting) the content from the HTML into the DCT to create well-structured DCRs from which you can then generate HTML from when all is said and done.

Bhargav Coca

Thank you adam, I had the copy/paste excercise from day 1, but to convert 2000 files by 2 people will take atleast 2 weeks. Highly not my Manger friendly approach. I have one and only option of writing a script which will generate xml from html some how and its piece of cake from there on.

Thanks

Adam Stoller

Thank you adam, I had the copy/paste excercise from day 1, but to convert 2000 files by 2 people will take atleast 2 weeks. Highly not my Manger friendly approach. I have one and only option of writing a script which will generate xml from html some how and its piece of cake from there on.

Thanks

Good luck - trying to impose structure onto otherwise un-structured HTML is a non-trivial operation. Start with one file, try to figure out how you'd do it, test it, then take another file and try using the same code - after you get about twenty+ files to work through your code and/or spit out diagnostics about files that were unable to be deconstructed / reconstructed - you can probably do a full run and then handle the odd cases with copy/paste (unless you can find another algorithm to handle most of those cases too)

As with most such projects - you're looking for the 80/20 rule - and making sure you have good diagnostics to supplement the 20% that don't conform.