#1
|
|||
|
|||
Numbering of references and cross referencing
Hi,
I'm writing a large document. In the end, it will probably be in the order of 300 to 500 pages. Normally, I would write such documents in Framemaker because of its outstanding stability but now I'm unfortunately stuck to WinWord due to company rules. Anyway, in section 2 of the document, I have to list all support documents with the document number and title as indicated below under "Starting format". In total, there will be some 100 - 200 support documents listed. Now I want to number the documents according to the groupe they belong to, i.e. someting like [Ref S1], [Ref S2] and so on, see "Desired fromat" below. In the document itself, I would then like to refer to these documents like "...for details see [Ref S1] and ....." Generally, I think it would be possible to use the SEQ field but and ideally, the abbreviation used in the field "S", "AA", "DA" etc. is automatically taken from the description above, e.g. "System Engineering (S)" before the list of documents. Maybe this has to be formatted in a certain way to allow this. Anybody with any good ideas how this can be done in a robust way. tstrandb Starting format 2. Documents and Abbreviations 2.1 Documents System Engineering (S) BC-ASD-TN-00257 System Mode Definition BC-ASD-TN-00174 Spacecraft Operational Timeline Document BC-ASD-TN-00228 SGM Data Definition BC-ASD-TN-00275 BepiColombo Launcher Separation Sequence BC-ASD-TN-00217 System FDIR Definition BC-ASD-TN-00173 BC Autonomy Functions, BC-ASD-IF-00009 BepiColombo Spacecraft Electrical ICD AOCS Architecture (AA) BC-ASD-SP-00010 AOCS Specification BC-ASD-TN-00167 AOCS Unit Management and FDIR Definition BC-ASD-TN-00168 AOCS Modes, Transitions and Operations BC-ASD-TN-00051 AOCS Study Assumptions for BepiColombo BC-ASD-TN-00332 Guidance Correction Function Definition, DMS Architecture (DA) BC-ASD-XX-nnnnn DMS Doc 1 BC-ASD-XX-nnnnn DMS Doc 2 AOCS Software (ASW) BC-ASF-SP-00028 AOCS SW Requirements Specification BC-ASD-SP-00129 FCE SW SSS and so on Desired format 2. Documents and Abbreviations 2.1 Documents System Engineering (S) [Ref S1] BC-ASD-TN-00257 System Mode Definition [Ref S2] BC-ASD-TN-00174 Spacecraft Operational Timeline Document [Ref S3] BC-ASD-TN-00228 SGM Data Definition [Ref S4] BC-ASD-TN-00275 BepiColombo Launcher Separation Sequence [Ref S5] BC-ASD-TN-00217 System FDIR Definition [Ref S6] BC-ASD-TN-00173 BC Autonomy Functions, [Ref S7] BC-ASD-IF-00009 BepiColombo Spacecraft Electrical ICD AOCS Architecture (AA) [Ref AA1] BC-ASD-SP-00010 AOCS Specification [Ref AA2] BC-ASD-TN-00167 AOCS Unit Management and FDIR Definition [Ref AA3] BC-ASD-TN-00168 AOCS Modes, Transitions and Operations [Ref AA4] BC-ASD-TN-00051 AOCS Study Assumptions for BepiColombo [Ref AA5] BC-ASD-TN-00332 Guidance Correction Function Definition, DMS Architecture (DA) [Ref DA1] BC-ASD-XX-nnnnn DMS Doc 1 [Ref DA2] BC-ASD-XX-nnnnn DMS Doc 2 AOCS Software (ASW) [Ref ASW1] BC-ASF-SP-00028 AOCS SW Requirements Specification [Ref ASW2] BC-ASD-SP-00129 FCE SW SSS Within the document, it shall be possible to reference a particular document as „. . . . . for details see [Ref S2] and [Ref AA5]. . . .“ |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
issues with cross-referencing | khaines | Word | 7 | 03-15-2012 03:25 AM |
Two questions about cross-referencing captions | gib65 | Word | 3 | 09-02-2011 10:45 AM |
Caption Cross-Referencing | b0x4it | Word | 3 | 05-29-2011 03:57 AM |
Equations - Enumeration and cross referencing | hpon | Word | 5 | 12-27-2010 02:27 PM |
Cross referencing | maltesedog | Word | 0 | 02-13-2009 07:43 AM |