Closed GoogleCodeExporter closed 9 years ago
Caterina,
In fact concept "agroforestry" doesn't have any sub concepts. You have deleted
"agroforestry systems" which has two sub concepts and after deleting
'agroforestry systems' the sub concepts remained in the same position.
Original comment by lavanyak...@gmail.com
on 22 Oct 2010 at 5:48
Lavanya and I had a long conversation about this point. Here the interaction
with the user should be better taken care of. In fact, the understanding is
that the WB treats deletion as a deletion of the selected concept only, but the
user is not really informed about that.
The dialog box should be enriched to include the following pieces of
information (dear colleagues, please revise my listing as appropriate):
- deletion will have to be validated and approved, meanwhile... ---btw, what's
the use of "proposed deprecated" things? eg. a web service accessing agrovoc
will retrieve that concept as existing or non existing? Are "concept status"
recognized by the web services and/or other application of agrovoc?
- you are going to delete the selected concept only, ie all its names in all
languages, all relations in- and out- going, all other pieces of information
attached to it. You are not going to delete this concept, but all its
subconcepts will stay. You may want to "move", "link" or "unlink" them by using
the corresponding buttons.
btw, some words could be used to explain what move, link and unlink do.
- what happens if the concept one wants to delete has other subconcepts that
are not shown right underneath it? ie. what happened in case of
polyhierarchies?
Also the help page should contain a detailed description of these cases.
Original comment by caterina...@gmail.com
on 22 Oct 2010 at 7:14
Original comment by ahsan.mo...@gmail.com
on 3 Nov 2010 at 8:08
Warn the user with popup. In future we can make this issue more complex.
Original comment by yjaq...@gmail.com
on 25 Nov 2010 at 12:09
Original comment by yjaq...@gmail.com
on 25 Nov 2010 at 12:09
I have drafted a pop-up message for the deletion of a concept:
ATTENTION! You are about to delete a concept with all its associated terms
................. .
Before deleting this concept, please check sub-concepts and relationships!
In case of existing sub-concept(s), please make sure to move the sub-concept(s)
to a new parent concept!
Original comment by johannsen.gudrun2@gmail.com
on 27 Jan 2011 at 10:12
My suggestion below.
ATTENTION! You are about to delete a concept with all its associated terms in
all languages, all its subconcepts, and all its relations to and from other
concepts.
Before deleting this concept, please make sure that all its subconcepts (if
any) are deleted or moved under a new parent. Also make sure that all its
relations are to be deleted. The new status of the deleted concept will be
"draft deprecated".
Original comment by caterina...@gmail.com
on 27 Jan 2011 at 10:30
Original comment by sachit.r...@gmail.com
on 31 Jan 2011 at 5:47
Original comment by caterina...@gmail.com
on 17 Feb 2011 at 12:37
Original comment by yjaq...@gmail.com
on 10 Mar 2011 at 11:52
Original issue reported on code.google.com by
caterina...@gmail.com
on 21 Oct 2010 at 3:26