Column name conflict: XY Tags vs. standard file Tags

[JLoftus]

I love XY's Tags feature, and use it extensively. Unfortunately, the name "Tags" is already used as a standard file property, and the use of both is ambiguous. Even if both are not used in the same view, switching views and seeing the column named "Tags" is confusing... Which "Tags" is it? One good solution would be to name XY's Tags as "XYTags" (and thus, using XY's Tags as a column in a view would be named "XYTags" and eliminate the confusion).

Alternatively, a somewhat reasonable mitigation could be to allow modifying the name of the column.
See below, I am using both Tags columns in the same view, but there's no telling which is which.

@Don, maybe this needs to be in the Wishes section, but is there any chance you might consider renaming XY's Tags feature or, could we get the ability to rename the column header?

tags.png

[jupe]

You can rename the Property column already, just add it to the list, right click the column header, select "Rename Column".

[JLoftus]

Thanks, I thought I'd looked for that, but I guess I was clicking on the other Tags column. This helps, but, it's not ideal, as that is renaming the standard Property "Tags", when in fact it's really the XY proprietary implementation of Tags that I would prefer to be able to rename. There doesn't appear to be any way to do this, right?

It's kind of a philosophy conflict, or in programming terms, it's an override. There's already a Tags property, yet here we have our own implementation of Tags, would make a lot more sense to be able to call our own implementation something else, rather than change (override) the default name of the standard Tags.

[jupe]

Well I assume you could use the English reference translation file and replace Tags in it with what you wanted, but I haven't tried personally.

I very much doubt Don will rename this feature.

[JLoftus]

Worked brilliantly, thank you!

XYTags.png

[admin]

Hacker!