It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×5,894
×4,710
×1,390
×864

question asked: Mar 25, 9:59 a.m.
question was seen: 400 times
last updated: Mar 25, 12:18 p.m.

Related questions

Unique URIs in each project for artifacts/attributes/links etc?

0
John-Paul Coetzee (13●1●4) | asked Mar 25, 9:59 a.m.
edited Mar 25, 10:00 a.m.

For new projects in DOORS NG I create a new schema by importing properties from an older project.


After the import the URIs for artifacts, attributes, data types etc are of the form
so I go through them and update them to
which takes quite a while.

Last week I thought to myself "why am I doing this?". The reason we created unique URIs in the first place was because Report Builder was failing to link duplicate-named data types (created for historical reasons).

Surely it is only necessary to create company-wide unique URIs per artifact type (or attribute, data type etc)? So it should be sufficient to to name them as 
across ALL projects?

Thoughts?

Comments
Ralph Schoon commented Mar 25, 10:53 a.m. | edited Mar 25, 10:56 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

What were the URI you chose in the older project area? 
My understanding is that it is your choice, what URI you want. If you want them to be different, you make them different. If you want them the same, you use the same. Because for your reporting they are the same thing, even if the names are different.
I would assume if you chose: http://my.company.uribase/rm/at#ArchitectureRequirement, the imported URI should be http://my.company.uribase/rm/at#ArchitectureRequirement unless you change it. Not sure about that however.

John-Paul Coetzee commented Mar 25, 11:36 a.m.

Sorry, I didn't make myself clear. 


The URIs in the older project are of the form

I suspect that I'm wasting my time with the /[OLDER_PROJECT_NAME] bit of the URI.

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ralph Schoon (63.3k●3●36●46) | answered Mar 25, 12:18 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

 I tried to say it, it is your choice but it is an important choice. I expected that you chose the form 

 http://xxxxx.xxx/[OLDER_PROJECT_NAME]/rm/at#ArchitectureRequirement

which is a rather poor choice, if this is actually something that you want to define the URIs globally. You should have  may be chosen http://xxxxx.xxx/rm/at#ArchitectureRequirement . You can keep the chosen URI. I do not know what happens if you change the URI in the old project area, if you want to consolidate. You might what to open a case with support, if that is feasible. As far as I can tell, the URI is already used in the report data and will not go away. 

So, if you consolidate the URI's in new project areas, you can replace them with the general ones in newer reports. I am not sure about the impact. 

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.