![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: linking from remote location Topic Summary: Created On: 19-Apr-2004 16:35 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello -
I am at a remote site and need to create links from a lower level doc to a higher level doc. There are other lower-level docs that link up to this high-level doc. My dilemma is this: I do not want to destroy any links at the home site, nor do I want to lock the high-level document. What happens when I restore my lower-level doc and it's link module? The high-level doc will have other links being made to it from different low-level docs.... Does anyone have a procedure for this? And, can I avoid partitioning? Will archiving be enough? Thanks! Vince www.ontargettechnology.com ------------------------- Vince Socci Principle Engineer www.ontargettechnology.com |
|
![]() |
|
![]() |
|
Vince,
In your example I am located as database adminstrator at the higher-level site, where at least one other site links from lower-level docs to our higher-level docs. But the linking is not done remotely, for various reasons. We have a procedure in place where the higher-level docs (also containing links amongst them <higher-level docs, if you follow my drift ...> ![]() Maybe Toni Drexler at Eurocopter wants to elabborate more on this, as what I describe here is his challenge to manage on a routine basis :-). - Pieter ------------------------- Pieter de Waard www.nhindustries.com |
|
![]() |
|
![]() |
|
Archive/Restore of a module destroys all links even inter-module links.
If there is no higher level module COPY at the lower level site (but there is a print-out), the lower level folks can insert their desired links ..err.. desired target AbsNo into some text attribute, perhaps "Link_Parent". When its restored at the master DB they would run "LinkByAttribute" on that attribute and actually restore the links. If there IS a higher level copy then the lower level folks can link to it. Be sure to run "capture5.dxl" or whatever as part of your archive process; then LinkByAttribute at the higher. - Louie |
|
![]() |
|
![]() |
|
louie,
Where does one find the "capture5.dxl" script and what does it do? ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
I think Louie is referring to a script that conserves Link information in an attribute. Thanks to Anton Drexler (Eurocopter) we have updated our baselining script to first update this "Link Store" before actually baselining, thereby ensuring that link information is up to date in any delivery we make. I imagine the same is possible with the archiving process. In our case it is not necessary, as modules are baselined as a matter of procedure before archiving it for delivery.
- Pieter ------------------------- Pieter de Waard www.nhindustries.com |
|
![]() |
|
![]() |
|
... as Pieter now already mentioned me twice, I think it sensible to contribute a little to the discussion.
Indeed, we use a script which allows to store the information about the outlinks of a module in a particular attribute "Linkstore" which contains <Target Module>:<Target Obj ID>:<Link Module>. This is different from "Link by Attribute" as it allows to store outlinks to more than one target. The procedure is adapted for transfer of modules to another site which might have a different database (= folder) structure, as the "Restore Links" utility allows to select different target or link modules if these differ in name or path from those in the "Home" database. The prerequisite is, of course, that the Target Obj IDs are the same in both the "Home" and the "Away" databases. In our case, this is assured as the toplevel targets are maintained in the "Away" database and exist as "read-only" copies in the "Home" database, and vice versa for the dependent documents. By a "Synchronize" mechanism, updates done in the respective databases are transferred to the copies, using module archives. uufff ... now I think the most important aspects are covered: Vince; I hope this is of some value for you? Toni Drexler Consultant for Quality Management and Requirements Management a.s.drexler@gmx.de (at the moment at Eurcopter Germany) |
|
![]() |
|
![]() |
|
Thanks for all your help, you've given me some great information.
Would anyone like to help me develop a "restore Links" script? Thanks ! -V ------------------------- Vince Socci Principle Engineer www.ontargettechnology.com |
|
![]() |
Telelogic DOORS
» General Discussion
»
linking from remote location
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.