• State Verified Answer
  • Replies 2 replies
  • Subscribers 139 subscribers
  • Views 1973 views
  • Users 0 members are here
Options
Related

Publishing Issue with a specialized DITA Topic - did we miss something?

Scott Farrar

Hi,

We are trying to introduce a specialized topic type into our content for the first time (our own, not from the DITA standards).   The root element is "unitTopic".   We've provided the specializations in the DocTypes directory and everything is working on the authoring side in Oxygen.

But, when we publish, any of these specialized topics get replaced with:

    <topic id="ERRORMAP"> <title>Object Missing</title> <body> <section> <p>This object is not available in the repository.</p> </section> </body> </topic>

I've poked around in the files that get pulled down and published, and found that these specialized topics are not actually making it into the workset for publishing.  

Also, in the .report.xml file that is within the workset directory, the GUID in question has a status of "object-not-saved":

<object-report ishtype="ISHModule" ishlogicalref="2644943" ishversionref="2644944" ishlngref="2644945" ishref="GUID-A04E7EC0-A608-4AAD-8FC1-5D2539582414" object-title="TestUnitTopic" lng="en" status="object-not-saved" defined-in-baseline="no" version="1" objectstatus="Prep"/>

Anyone else go through this and encounter this issue?   Is there a configuration step that might have been missed in providing this new specialization? Or can this be traced to a problem elsewhere in the specialization?   (If relevant, we're still on LiveContent Architect 2016)

Thanks,
Scott
Rate translation
×
Suggest better translation
×
Parents
  • +1

    Hi Scott,

    You are definitely missing configuration steps. The system can handle other Doc types, proprietary and other standards. This does however require some extensive analysis of that DocType on how link management is done, configure it in Publication Manager, etc to just name few.

    I'm afraid this is not something we can clear out in a forum thread, so my advice would be to reach out to Profesional Services (PS).

    -Dave

    PS: Don't get me started on the renames...but to my knowledge we never released LiveContent Architect 2016, so it is either LiveContent Architect 2014 or Knowledge Center 2016 :-)
Reply
  • +1

    Hi Scott,

    You are definitely missing configuration steps. The system can handle other Doc types, proprietary and other standards. This does however require some extensive analysis of that DocType on how link management is done, configure it in Publication Manager, etc to just name few.

    I'm afraid this is not something we can clear out in a forum thread, so my advice would be to reach out to Profesional Services (PS).

    -Dave

    PS: Don't get me started on the renames...but to my knowledge we never released LiveContent Architect 2016, so it is either LiveContent Architect 2014 or Knowledge Center 2016 :-)
Children
No Data