Bug 807906 - RFE: Have topic section id's automatically set to the topicid to provide stable xref linkends
Summary: RFE: Have topic section id's automatically set to the topicid to provide stab...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Web-UI
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Matthew Casperson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-29 06:06 UTC by Tim Hildred
Modified: 2014-08-04 22:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-10 03:40:22 UTC


Attachments (Terms of Use)

Description Tim Hildred 2012-03-29 06:06:53 UTC
Is it possible that the <section> tag for a topic could automatically have an id inserted into it by Skynet in the form of <section id="TopicID1234"> where 1234 is the topic ID number? 

This will provide a stable xref linkend to a given topic no matter where it gets used.

Comment 1 Joshua Wulf 2012-03-29 23:55:19 UTC
A consideration: using the topic ID as an xml element id works when there is only one instance of the topic in the output namespace (like a website or topic cloud), but doesn't work when more than one instance of a topic can exist in the output namespace (like a "book")

ref: https://bugzilla.redhat.com/show_bug.cgi?id=767000

Comment 2 Matthew Casperson 2012-07-10 03:40:22 UTC
Topics can be listed multiple times in a book, so there will never be any such thing as a "fixed id". Currently the topic title is used as the basis for the ID, but this is not guaranteed to be stable.

xrefs should not be used anyway - all links between topics should be handled by the CSP or other processor.


Note You need to log in before you can comment on or make changes to this bug.