Auto-report page metadata?

Question

Links require access to Live Live Content.

We can select the default scheme (and the required parameter) in the folder properties . New components in these folders will have the selected scheme with the corresponding fields filled in.

We can select the default page template for structural group (SG) properties . A new page template will be selected on the new pages of these SGs.

Do we have a similar option for page metadata, so in this SG the author receives both the page template and the predefined page metadata (fields) for:

• page creation
• page template selection

We can do this easily with Inline Editing (SiteEdit) and page prototypes. But how to configure or implement this type of requirements in Content Manager Explorer?

Answer 1

I would say that there are several ways to achieve this:

1) Using the UI "Page Types" - if the page that you use as the page type should contain the same metadata. * I have not tested this !!! maybe you can confirm?

2) GUI extension - when choosing a page template, page metadata is selected based on the page template.

3) Event system. I'm not sure how much this will work, since it probably should be related to creating a page (checking the use of the default template) or saving if the template is used, and no metadata scheme is selected. but then if there is mandatory metadata, etc. etc.

4) Page template. This will set metadata (when publishing or previewing) - or alert the user that certain metadata must be set for this page template.

Hope this helps.

thanks

John

Answer 2

A very interesting question, and I see the benefits of this feature for editors. I have no answer for you. But AFAIK, even the event system may not be relevant here, since there are no events triggered when the page was created if we did not save the page. Is a GUI extension possible?

Answer 3

When you create a new item, this happens using the GetNewitem () method in the API (or GetNewObject () with old money). I always thought that for this operation there should be separate bindings for event systems, and not for modifying an existing element. I once suggested this on .sdltridion.com ideas regarding Components, however someone linked me to the OnSchemaGetInstanceDataPost event event, and the discussion ended.

Thus, in the case of a new component, the circuit is automatically requested, and through the hook you can interfere with the default data. So far, so good, but I still think that it would be generally useful to be able to change the default data for any type of element when first created.