Skip to main content
P
ptc-22689331-Visitor
1-Visitor
June 21, 2012
Question

Bursting Configuration

  • June 21, 2012
  • 15 replies
  • 6345 views

Hello All, new to the board, so any advice would be appreciated.


I'm trying to recreate our parent company's approach to our PTC solution, however our communication with them is limited.


In doing so, I can begin to revise their approach and procedures for our needs and build our Windchill ditabase. We receive their XML files for our manuals, and I obtained a copy of their custom folders with their stylesheets. I also received their bursting rules. When I try to burst a book from the map level, it comes back with an error saying, "Cannot modify the following attributes: lang, because they are not defined. I'm still a novice, although I have gone through all the AE and WC PTC courses I can go through, but I'm not sure where to fix this issue. The attributes are defined in the bursting rules, I see language under the attribute root in the Type and Attribute Mgr in WC, and it is a valid element attribute in the dcf. Where shouldI look, or should I post this in a better suited forum?


Thanks


Another question. If you're realtively new to the PTC family, and you have gone through AE, WC and Styler courses from PTC and read through a lot of their manuals, where would you look next for additional training and understanding? A lot of these courses teach basic application, but not understanding of what to do.


Thanks again!

    15 replies

    Show previous replies
    G
    GarethOakes16-Pearl
    16-Pearl
    June 22, 2012
    You didn't direct this email at me, but it occurs to me that you may have a simple way to load the content into Windchill. Just take each XML book, load it into Arbortext Editor and (assuming doctypes/bursting/etc. is good) do a "Save as Server Object" from the File menu. That will create an object for the document (and related objects for graphics, burst chapters, etc.). Those would then all be at A.1 revision.

    AFAIK Windchill does not ship with any translation management capability so the difference between a Japanese master and English variant would be irrelevant?

    -G
    P
    ptc-22689331-VisitorAuthor
    1-Visitor
    June 22, 2012

    I'll have to keep playing, rather than ask a question and keep trying.


    I added an elemename to the locnrule to operatormanualmap, and every document that did come up appeared as operatormanualmap in WC. I was only trying to have the map burst as a map. I'm still unsure how to burst the rest into their respective types (reference, etc.). Right now, my locnrules graphic and text have no elementname associated. That seemed to be the way they came in.


    My current issue is "checkin failed 1 conflict: K03_UWGM_NEVER_BEEN_UPLOADED:null" has me stumped. I will update if I figure out what that means.

    P
    ptc-22689331-VisitorAuthor
    1-Visitor
    June 22, 2012

    Gareth,


    During this whole test, I have a copy of the xml book and it's files all in one folder on my client. Everytime I make a test after changing the burst rules, I connect to my WC, and save as server object. That's where I keep getting different errors, like the one concerning language attribute, and the one concerning the revision levels. Every once in awhile, WC will upload a small bit of the files into my workspace, but they aren't in the library (although all attempts made every file an operatormanualmap). That's when i removed the operatormanualmap elementname from the locnrule. Now I get the error I just posted before this one.


    This is a doozy for me!

    P
    ptc-22689331-VisitorAuthor
    1-Visitor
    July 2, 2012

    Update:


    PTC and I were able to modify the bursting docs enough to get the books to burst to windchill. The files have the correct softype, although that's really as far as we have gotten.


    I'm wanting to understand and possibly undo a lot of the id referencing the parent company did. I'm still not experienced in understanding metadata rules well enough. Can someone tell me in general what these metadata rules are saying? For instance, I know that they're saying within elementname reference there is an expression listed, but I still don't understand what they are doing with them in WC. Just listing them as WC attributes, maybe? In the test with PTC, we had to remove these rules to get the book to burst, which makes me think to use them I'd have to add info in the Type manager, but I need to see if I need them in the first place. Thanks


    <dmsmetadata><metadatarule elementname="reference" expr="child::title"metadata="WC_NAME_ATTR" sourcetype="text"/"><metadatarule elementname="task" expr="@outputclass"metadata="positioncode" sourcetype="text"/"><metadatarule elementname="reference"expr="/reference/titlealts/navtitle/partnum" metadata="dmc"sourcetype="text"/"><metadatarule elementname="reference"expr="/reference/titlealts/navtitle/term" metadata="category"sourcetype="text"/"><metadatarule elementname="reference"expr="/reference/titlealts/navtitle/ph" metadata="variant"sourcetype="text"/"><metadatarule elementname="reference"expr="/reference/titlealts/navtitle/tt" metadata="situation"sourcetype="text"/"><metadatarule elementname="reference" expr="@xml:lang" metadata="lang"sourcetype="text"/"></dmsmetadata>

    S
    SirkoRudolph5-Regular Member
    5-Regular Member
    July 2, 2012
    Bryon,

    Basically what the metadata rules are about is to define how content of particular elements or attributes from XML is stored as metadata on the corresponding Windchill object. There they can be used for Search etc. The key in your sample data below is the "metadata" attribute in the metadatarule elements. This attribute defines the Windchill attribute where this particular content will be written to. And if that particular attribute is not defined in the Windchill Typemanager bursting will not work.
    For short the explanation of the attributes in the metadatarule element:
    elementname = when bursting encounters this XML element that particular rule will be evaluated
    expr = this is an xpath expression relative to the XML element given in "elementname". The result of that expression will be saved to the Windchill attribute
    metadata = the name of an attribute in Windchill. The attribute must be defined and attached to the soft type used for storing your XML file
    sourcetype = can be either "text" or "graphic", defining whether metadata shall be stored from a text document (XML) or a graphic which is referenced inside the XML

    That said your set of rules below gathers information from different elements/attributes in a reference topic when that topic is stored to Windchill and tries to write that information to different Windchill attributes on the object that represents the reference topic in Windchill.

    I hope that sheds a little more light on how the metadatarules in the burstspec are working.

    You can find more information in the Arbortext Helpcenter in the Content Management Guide/PTC Server connection document bursting/Assigning PTC Server properties

    Kind regards

    Sirko





    [Description:
    Terms & ConditionsAccessibility statement