Support for "user" variables

Comments

5 comments

  • Avatar
    K15t Support Team

    Hi Brian,

    thanks for that feature request. Are you thinking about the Metadata 2 Plugin by Andy Armstrong or do you want a solution independent of other plugins?

    I created an issue for our development team and your reference here: http://k15t.jira.com/browse/OFCE-58

    -Stefan

  • Avatar
    Brian Wallis

    I had a look at the ticket and yes, that is pretty much what I would want. Then I can add metadata to the document hierarchy and reference it in the template to fill in the details I require in the formatted word document. Could you leverage the metadata 2 plugin for this? ie: parse that plugin's macros and allow them to appear in the document. Then I can use the features of the Metadata 2 plugin *and* reference the same metadata in the template (I realise you may not want the dependency but it would be nice to just specify the metadata once in a single form).

    thanks.

  • Avatar
    K15t Support Team

    I think I didn't make clear myself: We do want build a generic solution, which uses metadata 2 properties as a source for metadata.  I was wondering whether you also use metadata 2 or something else.

    We don't want to reinvent the wheel.  :)

    Thanks,

    -Stefan

  • Avatar
    Brian Wallis

    Hi Stefan,

      Understood and I am installing the metadata 2 plugin now to have a look at what it does.

    This is the top feature requirement for me as I am in the process of working out how to pull a very disjoint and scatted document set into the wiki. We have a load of old word documents (and many diverging versions of the same document) scattered across file shares and a couple of sharepoint servers that are in desperate need of consolidation. We seem to have ended up with a separate version of each document per customer with no hope of updating them all so they are consistent across all our customers. I hope to use Confluence to manage these documents in a single version controlled space and then generate customer specific versions from there.

    The approach that I think might work is to have a child page for each customer that contains the customer specific metadata and then I can use that metadata to populate fields in the template. I am assuming that this will work by adding a customer name as a label to each of the customer specific pages and including only the one customer label in the word file generate.

    I've just realized, though, that I want to include some of this customer specific metadata into the body of the document text that comes from the confluence pages. Will this be possible?

    When you have a version of this for testing I would love to try it out.

    brian...

    P.S. I am going to buy a license as well, just have to get the budget approved.

  • Avatar
    K15t Support Team

    Hi Brian,

    These are two different things for us: For one, will be making metadata available from Confluence using the $scroll.xyz syntax for title pages, page headers, footers, etc. (that is http://k15t.jira.com/browse/OFCE-58). As a workaround, it is possible to create a word template per customer. This should be implemented before 2.1.

    On the other hand, replacing customer-specific content in the body of the text document is something different. We want to do this with what we call "annotation" which are used to mark text elements in Confluence to be handled during export -  i.e. replace it with other data, display/hide depending on the target group.

    To be open: Although we have implemented annotations in a client project (based on Scroll Wiki Exporter) and will add annotations to Scroll Office in soon, I cannot give a certain date when replacements will be available in Scroll Office.

    -Stefan

Please sign in to leave a comment.

Powered by Zendesk