Not Considering

Modify Pub Manager so it does not try and resolve xrefs that are conditionalized out of the pub

Publication Manager (version 11.1.2) tries to resolve all xrefs when releasing the publication, even if the content containing the xref is conditionalized out of the publication. If there is content that contains xrefs, but the content is conditinalized out of the pub, the pub publishes fine, and if everything is released, it results in a Release Candidate. But if I attempt to release the pub, it throws an error, saying that it contains hypertext links that cannot be resolved.

The use case: we produce HTML-based output that contains many maps. We want to include xrefs that link the reader to content in other maps when they are using the HTML output. But we also produce PDFs for each of the individual maps. Therefore, in each location where we reference content in another map, want to include two paragraphs: one that includes an xref to the other content, and one that includes a citation to the other content. Both of the paragraphs are conditionalized (HTML and PDF). When we produce the HTML output, we include the paragraph with the xref. When we produce the PDF output, we include the paragraph with the citation. This all works great. We can produce the output with no problem. But it falls apart when we try and release the publication that contains the individual map for which we produce the PDF output. Pub Manager will not release it. It says there are unresolved cross references. There really aren't because they are conditionalized out of the publication. Pub Manager needs to be changed to NOT try and resolve xrefs during the release phase that are conditionalized out.

Parents
  • Thank you for your response, Frank. I fully agree with your first point that if the pub is a Release Candidate, it should be able to be released without any further validation.  And I agree that if a topic in a Release Candidate is changed, the pub status should change to "Out of date." I also like the idea of an Admin being able to "unrelease" a pub.  I also agree with your third point about just releasing outputs. We don't explicitly freeze baselines. We simply release the output. The baseline is frozen automatically. Thanks for looking into this.

Comment
  • Thank you for your response, Frank. I fully agree with your first point that if the pub is a Release Candidate, it should be able to be released without any further validation.  And I agree that if a topic in a Release Candidate is changed, the pub status should change to "Out of date." I also like the idea of an Admin being able to "unrelease" a pub.  I also agree with your third point about just releasing outputs. We don't explicitly freeze baselines. We simply release the output. The baseline is frozen automatically. Thanks for looking into this.

Children
No Data