![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Partitions Topic Summary: Created On: 2-Aug-2004 19:30 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I am working with subset of documents within a larger project. What I would like to do, is use the modulesI am working with remotely from the project itself, then eventually return the modules to the project. With the modules, I will be editing, linking, etc. Is the way to do this use partitions? It is imperitive that the links between the modules I am working with are maintained between the two locations.
|
|
![]() |
|
![]() |
|
My experience with remote sessions on an away database: I sometinmes go to a partner company to work on modules (same scenario you sketched: links between modules to be conserved). First time around I used partitioning, and it worked fine, with the following side-remarks.
In the away session, it is not possible to add something to an enumerated type (logical, but still a drag) Upon my return, the rejoining with home database went without trouble Second time aroud, similar experience as above, except the rejoining did not work. So in fact I lost all changes made in the away database. Fortunately, I kept the partitioned (away) database. Via importing/exporting to/from Excel I was able to recover this data. This was a hair-raising experience I did not want to repeat. It was under 5.2, but I need some good arguments before trying that again with 7.1. The third time, I created a mirror of the modules required, including link modules and links to use in the away session, making the home modules read-only. In the away session, mainly one module was updated (attribute content), and some lout-going inks modified. Upon return, the modified module (also containing a link-store conserving all link information), replaced the original copy, and links were regenerated using the content of the link-store attribute. This works fine, except that the links from baselines are not conserved (new feature under DOORS 7). From all this I concluded:
upon return, synchronise the home module with changes in the away module (haven't figure out how just yet) to conserve links from baselines in this way, you maintain full control of the modules during the away session, including history If anybody has better experience with partitioning I would sure like to hear about it. Mine was a bit scary. ------------------------- Pieter de Waard www.nhindustries.com |
|
![]() |
Telelogic DOORS
» General Discussion
»
Partitions
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.