Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
DCT Meta data Design Decision
v_sawant20
We are having Meta data fields in DCT, of which many are common across DCTs. To have common code I have 2 alternatives that I know off.
1. For common attributes across the DCTs we have made inline ipl file which generates DCT item tags based on which are required within a given DCT.
2. We added the attributes in Meta tag window and plan to disable fields from all the fields which are not required on a given DCT using FormAPI.
The presentation we are using Live Site and plan to store content in DB and access it by components.
Given the above scenario is it better to store meta data using Meta Tag window? Or is it better to store the meta data using the common ipl. I couldn’t find much advantage doing it with Meta data window. But I wanted to know if I am missing something by not using the OOTB feature of meta data window.
Please let me know the pro and cons of these. Any suggestion apart from these 2 alternatives would also be welcome. What is the best practice I mean.
Find more posts tagged with
Comments
Trey
Both should work. Option 1 requires more resources and will probably take longer to run. Keep in mind any time you do an inline it will be called whenever a datacapture screen comes up even if it is not used for that particular asset.
HTH