#15 Assign keywords to objects

[Jeffrey Robble]

The ability to assign an arbitrary number of keywords to an object can be considered for future development. I can foresee a complication where you must ensure that no two objects share the same keywords.

This is how I (Gregor) implemented it in the past somewhat, adding a new resource to the resource list would give a unique number.
However, a user will have some "favourite resources" so being able to put em into the numbers 0-9 woudl be good. Think about it like telephone number shorcuts.

so de default behavior could be the numbers that a user assigns, its simply a second label or maybe we should use keywords, the other number is assigned as you say. problem is that user a may not have the same resources as user b. we could set up a service where a resource gets a numbe, but considering that we may have 100 and thausends of them haveing a keyword list may be better.

maybe we need

login -n black set keyword "black, b, 1, schwarz"

tan I could say

login 1
login schwarz
login black
login b

which will login to the same resource

Thinking about this futher, one could generalize the keywod concept as an object so other commands can simply use it also

Thus I could do

cp black white filename

[Jeffrey Robble]

Logged In: YES
user_id=1951185
Originator: YES

I looked at your object, why not immediately add a hashtable with the name keywords to it.
If they are unique or not, can be done a different time. When we have arrays of objects and look for one with a keyword, we may get actually multiple back, so we can do groups. This would be a great feature.

[Nobody/Anonymous]

Logged In: NO

keywords can also be used to provide object grouping, one could implement a keyword that spawns different objects, thus the keyword for a machine could be used to augment a compute or file resource. We can than issue simple queries that return objects with that group.