What is the best way to store the Title on Page Settings level OR Metadata level?

Hi,

ENV: TeamSite 7.3.1 SP2

Thru the Page Settings interface of a .page file, I can add/update the "Title, Keywords, Description".

Also using TAGGING, I can add/update the "Title, Keywords, Description" as Metadata of the same file which is stored as external attribute of the file in TeamSite/Metadata/Title , TeamSite/Metadata/Keywords &
TeamSite/Metadata/Description.

What is the best approach to get these values? What is the difference? Is there anyway that I can match both the values same?

Please guide.

Thanks in advance.
John

Find more posts tagged with

Comments

Rick Poulin

The page's properties and its EAs are generally mutually exclusive -- you either use one or the other, but typically not both. The choice depends on two things:
* which one your users find most intuitive
* whether you want to execute additional functionality, such as reporting or workflow validation of metadata (in which case EAs is the only real option)

Consider also that the TagUI is customizable, whereas the page properties are not, so if you may have additional metadata to capture now or in the future, you probably wouldn't want separate screens for it.

Note that if you do use EAs, you'll need some kind of storage for them on the runtime (LSCS/DB/XML/etc) and you'll want to write a site-level precontroller to fetch those values at request time.

Migrateduser

The page properties and metadata are separate entities.

The question is, where do you wish to fetch this information. You can get the steps ahead accordingly. As already mentioned by Rick, if you wish to go by the EA route and you wish to fetch these attributes at runtime, you need to make use of LSCS or a custom storate like a DB.

jstephan

Thanks for the responses.

Lets say, If I only want to store the TITLE, KEYWORD, DESCRIPTION and no other additional information then is it better to use the PAGE PROPERTIES rather than METADATA TAGGING?

Is there any way to update the PAGE PROPERTIES during the deployment time using PLC workflow? I know the .page file is a XML format and we can update it., but looking for any better solutions.

Cheers
John

Rick Poulin

Is there any way to update the PAGE PROPERTIES during the deployment time using PLC workflow?

There is no *supported* way, as you're not supposed to modify the .page XML directly and there are no APIs to do so. The only *supported* option is to use EAs, which do have a supported API. However, that does mean you need a repository for your metadata on the runtime and if you have no additional requirements to go this route, then modifying the .page XML is a legitimate option. As far as hacks go, I'd call this one pretty minor.

jstephan

There is no *supported* way, as you're not supposed to modify the .page XML directly and there are no APIs to do so. The only *supported* option is to use EAs, which do have a supported API. However, that does mean you need a repository for your metadata on the runtime and if you have no additional requirements to go this route, then modifying the .page XML is a legitimate option. As far as hacks go, I'd call this one pretty minor.

Thanks again Rick for the response.