Q on converting to very different content type

ddalquist's Avatar


07 Aug, 2014 07:14 PM

Situation = Converting pages from an old, what-was-supposed-to-be-temporary
site that lasted several years, to an entirely new structure based on

My understanding is that, if you keep the original data def. and metadata,
you can apply a new content type (based on Bootstrap with new config set,
etc.) to an old page.

Q: Can the metadata exist in a different configuration for two content
types, e.g.,
"Teaser >> *Hidden* >> No"
"Teaser >> *Inline* >> No"
and still work for both the old and new pages?

Q: Does the data def. need to have the same Cascade path, e.g., "Data
Definitions/IntranetPage," for it to work with different content types?

Additional background -- The new page data def. is laid out quite
differently than the old, and perhaps only half of the new data def.
utilizes the same xml as the old. As those that do not match are not often
used, I was hoping, for a period of transition time, to incorporate the
non-matching data def. fields into the new data def., allowing users time
to copy/paste from an old data def. field into a new one. After the
transition time has expired, I'd remove the "old" data def. fields
(assuming there's no data populating them anymore).

In my attempt to test this, none of the data transferred, even the matching
fields. I've searched the knowledge base and help forums, and have not
found good guides/best practices for converting and old site to a new
layout, and I'm developing more questions than answers. Any help would be
BTW, I do not have direct access to the database to either figure things
out or to make changes.

Dave Dalquist
[email blocked]
Intranet Coordinator
Learning Resources & Technologies
Northwestern Michigan College

  1. 1 Posted by Ryan Griffith on 07 Aug, 2014 07:55 PM

    Ryan Griffith's Avatar

    Hi Dave,

    As soon as you change the identifier or location of a field (Metadata or Data Definition), you will lose the existing values when you switch over to the new data definition. That being said, the existing values will remain until you edit the page. Once the page has been updated, the new structured data will be saved. I suspect this is what you experienced when you tested things out.

    Your best bet would be to use Web Services to essentially map the old structured data to the new data definition/metadata fields. If you don't mind, I would like to move your discussion into a public category as I have heard of clients writing scripts to migrate data. If no one responds I can certainly have someone from our Services team get in touch with you to see what your options may be.

    Please let me know if you have any questions.


  2. 2 Posted by Wing Ming Chan on 07 Aug, 2014 10:31 PM

    Wing Ming Chan's Avatar

    Hi Dave,

    I talked about this on Creation of data definition blocks. Using my library, this is a very easy job, provided you have a one-one mapping from the old data definition to the new data definition, or from the old metadata set to the new metadata set. And with the Cascade class, you can even create data definitions and data definition blocks, etc, on the fly. For details, see my Web Services Tutorial.


  3. 3 Posted by Wing Ming Chan on 08 Aug, 2014 06:28 PM

    Wing Ming Chan's Avatar

    I have just added a new section to my site, discussing how to switch data definition, with a complete program, taking care of textual data, asset choosers, and multiple fields. See Working With Data Blocks for details.


  4. Ryan Griffith closed this discussion on 20 Aug, 2014 02:19 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac