The entire DUCk solution consists of various unique pieces:
We'll describe each of those in this section.
The metadata changes for the DUCk solution are fairly simple: a single custom class and a few custom properties. For a production application, you would be likely to create a CE AddOn (described in Chapter 7, Major CM Features), or perhaps one or more XML files that could be imported via FEM. The first step in doing those would be to manually create the metadata changes in a development Object Store, and that's what we'll describe here.
We showed some examples of metadata changes in Chapter 4, Administrative Tools and Tasks ...