Changing a non-preferred term to a preferred term without changing the status of the existing preferred term

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I want to change the term 'retail prices' which is a non-preferred term of 
'consumer prices' to a preferred term and make it a child of 'consumer prices'
2. I edited the term 'retail prices' by checking the box 'preferred term', and 
then validated the change. 
3. After validation the term 'consumer prices' is now a non-preferred term

What is the expected output? What do you see instead?
I would like to have the possibility to keep the previous preferred term 
'consumer prices' as well, and make it a parent of 'retail prices'. The problem 
is that we still have quite a lot of non-preferred terms which have to be 
changed to preferred terms. The ICRISAT team has currently an Excel table with 
around 600 non-preferred terms (of course not all of them will have to be 
changed!). Any suggestion how to proceed?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by johannsen.gudrun2@gmail.com on 12 Jul 2010 at 1:30

[GoogleCodeExporter]

Original comment by ahsan.mo...@gmail.com on 13 Jul 2010 at 6:19

• Changed state: Accepted

[GoogleCodeExporter]

Here are the steps:

1. Create a new concept with label 'retail prices' as a child of 'consumer 
prices' and mark it as preferred term.
2. Delete term 'retail prices' from the concept 'consumer prices'. Term 'retail 
prices' will still remain under concept 'consumer prices' but as deprecated.
3. Validate both actions.

Original comment by sachit.r...@gmail.com on 14 Jul 2010 at 8:20

• Changed state: Fixed

[GoogleCodeExporter]

Thanks for explaning the procedure, this we discussed already some time ago. I 
don't think that this procedure is ideal as I have serious concerns about 
deleting terms. Users might forget to delete non-preferred terms which are 
created as new concepts, and then we might have a lot of duplicate terms. 
Besides, this also means that users have to make sure to create also the other 
language labels!

Original comment by gudrun.j...@fao.org on 14 Jul 2010 at 8:37

[GoogleCodeExporter]

The above steps are just quick solution available with current WB which is 
quite cubersome and may be not complete. As we discussed in our last skype 
session, we first need to prepare the requirement documents for this issue with 
all the necessary features and then will start working on it.

Original comment by sachit.r...@gmail.com on 14 Jul 2010 at 9:18

• Changed state: New

[GoogleCodeExporter]

It's really helpful if we have 'link' 'unlink' and 'moving' concept functions 
at term level also. May be this solution can solve the above problem.

But another important issue here is we should have 'validation' for all these 
functions both at term and concept level.

Currently we don't have validation for all these functions at concept level. 
Please include this in the current version.

Original comment by lavanyak...@gmail.com on 15 Jul 2010 at 10:25

[GoogleCodeExporter]

See issue 467

Original comment by gudrun.j...@fao.org on 22 Nov 2010 at 1:30

[GoogleCodeExporter]

This is a complex issue which we should save for a later version. Perhaps 
Sachit or Prashanta can write a script to bulk fix these 600 terms and we will 
see in future how to address the problem

Original comment by yjaq...@gmail.com on 26 Nov 2010 at 1:24

• Added labels: Component-Logic, Milestone-2.1, Priority-Medium, Type-Enhancement, Usability

[GoogleCodeExporter]

Issue 422 has been merged into this issue.

Original comment by yjaq...@gmail.com on 26 Nov 2010 at 1:28

[GoogleCodeExporter]

Original comment by yjaq...@gmail.com on 26 Nov 2010 at 1:39

• Added labels: Milestone-2.2

[GoogleCodeExporter]

Original comment by yjaq...@gmail.com on 26 Nov 2010 at 3:39

• Added labels: AssignedTo-Prashanta, AssignedTo-Sachit

[GoogleCodeExporter]

Original comment by yjaq...@gmail.com on 26 Nov 2010 at 3:40

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by yjaq...@gmail.com on 10 Mar 2011 at 11:52

• Added labels: Type-Improvement