Option for Alternative behaviour for selecting 1000+ terms

Backgorund:
It is very difficult to make multiple selections on big heirachical term branches/trees which span thousands of related terms,
e.g. we loose site easily of what is selected and what is not, also one mistake could be very costly.

Proposed feature 1
* enable drag&drop of terms into an optional selection basket/tray/list
* Also, create a tiny trash icon, where we can drop non-required term(s)

Proposed Feature 2
Will, for simplicity and to avoind confusion to users, this feature can be implemented as a separate co-module which is mapped to its own unique content-block apart.

It is around to features which work with each other in synergy:
1) User is able to define query criteria, or selection rules OR directly utilize the rules of the views module which are assumed to be predifined there in the views db-schema.
2) Display the tree of terms in a nice visual way somehow, but, the terms which are part of reference view to be highlited in different color or background-color, as an indication that this very term has already been designiated somewhere in the website (that depened of the views filter which is preset especially by the user for this purpose.)

Usage Scenario

- Let us suppose that I have 3000+ taxonomy terms under one/several vocabularies...
- These 3000+ are mirroring a book of Bible / Physics / Chemistry / Encyclopedia ...etc... just think of researchers point of view. (that Vocabulary is not allowing free tagging)(Must Select one)
- The Taxonomy is made to be a mirror of the Table of Contents for any of the above references.
- I am a member of a team/class, and we are assigned a project where we have to collaboratively describe and summarize any of the above volumes.
- Plan is that for every taxonomy (TOC Node) which exists as a term, we are asked to create a matching book page (mirroring the same hiearachy in terms of parent/child as in the hiearachy of the relevent taxonoy terms - as we said earlier)
- Accondingly, we are going to tag that book-page with that relevant taxonomy term as a must. (essential tag)
- Additionaly, we are having other special vocabuly which serve as a different name space for free tagging (optional tags), i.e. that vocabulary is configered to allow free tagging.
- So far, things look nice, neet, organized, but we miss one more important element.......................
- At this level, we might be able to install the views module and then create a filter that would display the list of the pages which belong to book X, ...
- ... and since we know that every page which was created in that book must have been at least on term from our essential TOC vocabulry; then we can take the same query result as an array which hold the ids if the fetched taxonomy terms and then pass that array to the custom module as mentioned above to cater for the masking/highligting functionality which is all about.

.............. We wanted that feautre - which is all about here - To be able to look into that custom block, and by reazling which taxonomy terms are highlighted; the whole working group knows how much progress is being done, and the terms which are NOT hightligted tell us that we still need to work on summarazing these terms into the new relavent book pages/blogs/polls/..etc.

I hope this is clear enough to communicate the need of having to be able to take control with volumteric taxonomy implementaitons.