Virtual directories

[sargasso]

Now that EA links to external documents in a neat way, I'd like to see the introduction of some virtual directories to let me shortcut access.

Let me explain.  Lets consider Element File Links - say a link to something trivial like a requirements doc.  Now, being just a test monkey, I am at the whim of the Project Office comedians when it comes to the location of a) the "latest" version, b) the current release version and c) the latest "approved" version (plus occassionally the variious "obsolete" versions).  Now, currently these versions lie at the end of a 7+ level directory structure with a path string like "G:\GROUPS\CountryLink Reform Program\TravelLink Upgrade (ORION)\SPECIFICATIONS\3.1.14 Quote Fare Module - OrionV5v2.0.pdf".  They are comedians because every now and then (approx monthy) just to justify their existence they restructure the directories.  This generates several days effort updatinng the models so the links are correct.


As an aside, could we have the Notes instead of the path displayed in the Files tab list? or better still a short title for the doc would be even better.


It would be extremely cool if I could associate external documents with a virtual or logical location - like %CurrSpec%, then I wouldn't have to go through this pain every time they have another good idea!

I am sure others have the same type of problem.  Any support?

bruce

[Bruno.Cossi]

Count me in!

Simple as it seems, this would be a huge step for some of the larger companies that have tons of external documentation (that no one ever opens, but that is besides the point) in folders that sometimes are even MEANT to change as part of the regular SDLC.

In short: I second this!

Bruno

Now that EA links to external documents in a neat way, I'd like to see the introduction of some virtual directories to let me shortcut access.

Let me explain.  Lets consider Element File Links - say a link to something trivial like a requirements doc.  Now, being just a test monkey, I am at the whim of the Project Office comedians when it comes to the location of a) the "latest" version, b) the current release version and c) the latest "approved" version (plus occassionally the variious "obsolete" versions).  Now, currently these versions lie at the end of a 7+ level directory structure with a path string like "G:\GROUPS\CountryLink Reform Program\TravelLink Upgrade (ORION)\SPECIFICATIONS\3.1.14 Quote Fare Module - OrionV5v2.0.pdf".  They are comedians because every now and then (approx monthy) just to justify their existence they restructure the directories.  This generates several days effort updatinng the models so the links are correct.

As an aside, could we have the Notes instead of the path displayed in the Files tab list? or better still a short title for the doc would be even better.

It would be extremely cool if I could associate external documents with a virtual or logical location - like %CurrSpec%, then I wouldn't have to go through this pain every time they have another good idea!

I am sure others have the same type of problem.  Any support?

bruce

[thomaskilian]

Yes. A similar approach as in Local Paths as used in code engineering would be very useful.

P.S.: Bruce, will it be possible to buy a ticket to Orion from Australia soon?