Limit possible operation tags

[forman]

Expected behavior

Operations should only use tags from a limited and agreed-on set.

• aggregate
• anomaly
• arithmetics
• coregistration
• correlation
• index
• io
• outliers
• pandas
• plot
• resampling
• select
• subset
• timeseries
• utility

Actual behavior

We have 20+ op tags. See dropdown list in GUI.

Specifications

0.9.0.dev3

[JanisGailis]

@forman, can you provide the initial input to such a set? As in, which tags it makes sense to have from user's perspective when using the GUI?

[forman]

When I was young, I wrote https://github.com/CCI-Tools/cate-core/wiki/Operation-Tags

[JanisGailis]

That's a good initial set. I'll use those tags and raise the question if there is an operation that doesn't fit well within that set. So, according to that list 'pearson_correlation_*' would only have the utility tag.

[forman]

Plus the correlation tag, because it is its module name.

[forman]

Ah, but we could add that automatically - right?

[JanisGailis]

It could be done automatically, and if it's done it should be done automatically. I'm just wondering if we actually want to put module names as tags. I mean, it makes sense to have them. But then, there are currently 16 operation modules in cate/ops. Add 7 tags mentioned in the wiki and we're back to 20+.

[forman]

You're right. So let's not auto-tag.

[JanisGailis]

I'm going over all operations to check if the tags used are not too extensive. E.g. each operation might have a module tag (not necessarily), and maybe a tag from the list in the wiki.

[forman]

@JanisGailis any news here?

[JanisGailis]

@forman Moving it to paused must have been done by mistake. As far as I'm concerned, this is done. I've gone over all operations and limited the tags to what we have in wiki + (maybe) module name.

[forman]

Looks ok now: