Archiving Links

I am in a position where we need to share 10 or so modules with another group so they can use them as a reference for their requirements. The problem is while they do have DOORS, they do not have access to our DOORS server. Archiving seems to be the ideal way to achieve this. However, we need the links to be intact on the other side. Archiving the project is not an option since we are dealing with maybe 1/8 of our project. One of my co-workers made a comment about how she used throw modules back and forth with another group a while back and there was a utility that she vaguely remembered using. This utility would preserve the links and you could restore the modules with links on the other side.

I wanted to know: Does anyone know of a utility that will do this, or is there a better alternative (other than recreating with scripts)?
SystemAdmin - Wed Sep 07 14:18:02 EDT 2011

Re: Archiving Links
OurGuest - Wed Sep 07 14:39:30 EDT 2011

Perhaps she was thinking of partioning.

Re: Archiving Links
llandale - Wed Sep 07 15:10:10 EDT 2011

This sounds like the classic need for "partitioning", you create a read-only partition with yout 10 modules and all their link modules, send it to them, then immediately "rejoin" or whatever that verb is and go about your merry way. They restore the partition and can see your stuff but cannot change it; and cannot send it back but you don't want it anyway. Next month they reject or whatever the partition before you send them another with updated modules.

Basically the same thing would be for you to archive your project, restore it right away into a sibling project, remove all the modules you do NOT want them to see, (delete then purge them all), then archive that project and send it to them.

  • Louie

Paritioning is really for sending them modules that they will edit, locked down in your database until they send the partition back and you reclaim it.

Re: Archiving Links
SystemAdmin - Wed Sep 07 15:32:46 EDT 2011

It sounds like partitioning is not the utility she was talking about. It has been a long time since she has used it and its possible that its no longer supported, but I am hoping that its still around.

Re: Archiving Links
llandale - Thu Sep 08 10:27:55 EDT 2011

SystemAdmin - Wed Sep 07 15:32:46 EDT 2011
It sounds like partitioning is not the utility she was talking about. It has been a long time since she has used it and its possible that its no longer supported, but I am hoping that its still around.

The primary use of Partitioning is for the Home database to package up a sub-set of modules and send them to the Away database. the Away folks edit them. When done, the Away folks package them up again, send them back, and the Home folks restore. While the partition is Away the Home folks cannot edit anything, and after its sent back the Away folks cannot edit those modules.

The Home Folks can and should include read-only modules in the partition that the Away folks can see but cannot change. e.g. the Home Folks send a Read only 'System' spec and and read-write 'SubSystem' spec and link modules Away, and those folks enhance their sub-system spec and create links to the System spec.

Note that only one database at a time can edit a particular module. There is some awkwardness vis-a-vis the links, e.g. SubSystem to System, when the Home is editing the System spec while the Away is editing the SubSystem, but IIRC that situation can be overcome but I don't recall how.

I have a nagging memory that years ago you could send Individual sections of a shared module to another database (i.e. partition part of the module), but that same nagging memory tells me that was a disaster, but its possible they have fixed that now.

I don't recall the correct Partition verbs, but if the Home folks 'send' the partition and immediately 'recall' or 'rejoin' it, then the Away folks cannot send it back. That's desirable if you want to send the Away database some read-only modules and their links, which is I believe your original desire.