Using metadata in scroll templates

Comments

10 comments

  • Avatar
    K15t Support Team

    Hi Panos,

    thanks for the heads up. I have opened an issue to build a {scroll-metadata} plugin: http://k15t.jira.com/browse/OFCE-273

    As a workaround: Have you tried installing the metadata2 plugin on Confluence 3.5. I think you have a good chance that is will just work. (Trying this on a test installation is highly recommended!)

    -Stefan

  • Avatar
    Panos Athanasiou

    Thanks for the tip Stefan. I'll try it and let you know.

  • Avatar
    Panos Athanasiou

    Hi again. It seems that the workaround performs as expected. Still, I cannot tell right now if using the metadata2 plugin is completely stable but up to now my experience is positive.

    Please also keep in mind that the solution you propose for overriding page titles (found under http://k15t.com/display/OFCE/Overwriting+Confluence+Page+Title) is also affected by the Metadata plug-in and perhaps it would be interesting to update it accordingly (or open a new JIRA for that?)

    In any case, thank you for the swift reply.

  • Avatar
    K15t Support Team

    From what I can tell, the Metadata2 Plugin code hasn't change much over the last few confluence releases. 

    Anyhow, we will be tackling this soon.

  • Avatar
    Pascal Levier

    Hi all !

    I'm writting documentation templates for my company, both for content (Confluence) & export (Scroll-Office).

    The goal is to define all the content within the Confluence pages in order to avoid modifying the Word files after exportation.

    I've planned to use the $scroll.metadata.(YOUR_METADATA_KEY) placeholder, but the metadata plugin doesn't seem to be maintained.

    Since I have to provide a sustainable solution for the hundreds of users, would you have please an advice on the best strategy ?

    Thank you in advance,

    Pascal

  • Avatar
    Nils Bier

    Hi Pascal,

    we've already started on developing an own solution based on the Page Properties Macro (see https://confluence.atlassian.com/display/DOC/Page+Properties+Macro): https://k15t.jira.com/browse/EXP-522

    Once the feature is merged (in the next version of our Scroll Exporters), it will be possible to define page properties and use those page properties in your template. So there will be no need for the metadata plugin.

    I hope that information helps.

    Best,Nils

  • Avatar
    Pascal Levier

    Hi Nils,

    Good news !

    So we'll use the Page Propertie Macro we have already installed on our server.

    Have you an idea of a date / milestone for the next version of the Scroll Exporter delivery ?

    Thank you for your support

    Cheers,

    Pascal

  • Avatar
    Pascal Levier

    Hi Nils,

    I come back to you to know if you have a date for the next version of the Scroll Exporter delivery including the 'Page properties' plugin support ?

    Indeed, I have to provide my developers with a Word export solution using properties within the 4 next weeks.

    It's simply to know if I have to manage with the metadata plugin first.

    Thanks a lot for your anwser.

    Pascal

     

  • Avatar
    Steve Meiers

    Has anything new happened with this issue?

  • Avatar
    Nils Bier

    Hi Steve,

    We've shipped the mentioned functionality a while ago and have documented it in our Scroll Office documentation.

    Please have a look at the following page to find further information about how to use page properties as placeholder in your template: https://help.k15t.com/scroll-office/using-page-properties-as-placeholder-101157272.html

    I hope that helps. Please let us know if you have any additional questions.

    Best,
    Nils

Please sign in to leave a comment.

Powered by Zendesk