BUG: 4.0cRC3: Unexpected "Tags" and "My Tags" fields in Library panel

JimTowler

I am able to select columns of "Tags" and "My Tags" in the Library Panel, and in making rules in a Collection.

In both cases, the field appears to be a ref. to the same contents.

The updated 4.0c Help only speaks of the MyTag field, and knows nothing of the shorter name.

Expect: Keep one and nuke the other.

Find more posts tagged with

Comments

JimTowler

EDIT: Misleading post deleted.

Also in the above, the bit about Collections is not helpful. Problem limited to column display in Library Panel only.

Rich DeRuiter

I am able to select columns of "Tags" and "My Tags" in the Library Panel, and in making rules in a Collection.

In both cases, the field appears to be a ref. to the same contents.

The updated 4.0c Help only speaks of the MyTag field, and knows nothing of the shorter name.

Expect: Keep one and nuke the other

Jim, I'm digging through my memory a bit here, and I could be thinking of a different feature, but what my dusty memory is telling me is that in the future we may be able to share tags, or that Logos may 'pre-tag' some resources for us. The "My Tags" feature then would discriminate between the two.

I don't know if this is still in the works, or even if I'm remembering correctly here.

Bohuslav Wojnar

https://community.logos.com/discussion/comment/127764#Comment_127764

I don't know if this is still in the works, or even if I'm remembering correctly here.

My memory is as dusty as yours Richard [:)] but that is exactly what I remember also.

JimTowler

https://community.logos.com/discussion/comment/127770#Comment_127770

Thanks Guys.

It would be great if Logos tagged additional information into resources. Maybe what packages a given resource is included in. When we purchased it. All kinds of things are possible ...

However, in the case above, I enabled the display columns for both "Tags" and "My Tags" in the Library Panel. I would NOT expect anything to display in the "Tags" column if nothing has been assigned there yet. In the graphic above, it displays the contents of the "MyTag" field of the database/metadata about my resources. That would seem a bug, if its intended to render a different field from the database!

Rosie Perera

https://community.logos.com/discussion/comment/127775#Comment_127775

The "My Tags" column is for your personal tags. The "Tags" column is reserved for a future feature where users will be able to share tagging with each other. For now it just shows the same as the "My Tags" field, but its future use is not implemented yet, so ignore it for now.

JimTowler

https://community.logos.com/discussion/comment/127791#Comment_127791

Thanks Rosie.

Except it seems a BUG and misleading to display it, yet draw its contents from a different field. It would be better if it was empty, so people don't build saved layouts etc using it.

It caused me to waste a LOT OF TIME attempting to build a new collection, as the "Tags" column appears in the Collection Builder screens, and displays the data that actually is in the "MyTag" field. It was impossible to make the correct rules!!!

FIX: Make the Tags column BLANK, and not the same as MyTags.

steve clark

https://community.logos.com/discussion/comment/127882#Comment_127882

FIX: Make the Tags column BLANK, and not the same as MyTags.

Or simply hide that column. [:)]

Rosie Perera

https://community.logos.com/discussion/comment/127884#Comment_127884

FIX: Make the Tags column BLANK, and not the same as MyTags.

Or simply hide that column.

Yeah, this is what I'd prefer. It confused me at the beginning too.

JimTowler

https://community.logos.com/discussion/comment/127884#Comment_127884

Or simply hide that column

Well, but thats NOT the natural answer. Its only an answer once you know its a bug, and you need to use some kind of workaround to get the results you expect. Not the way a UI should work.

If you go into the Library Panel, or column view while building a Collections rule, you can't tell from the UI which is the correct field.

I stand by my claim: Currently its a BUG to display the "MyTag" content in the "Tags" column/field.

Rosie Perera

https://community.logos.com/discussion/comment/127896#Comment_127896

Or simply hide that column

Well, but thats NOT the natural answer. Its only an answer once you know its a bug, and you need to use some kind of workaround to get the results you expect. Not the way a UI should work.

If you go into the Library Panel, or column view while building a Collections rule, you can't tell from the UI which is the correct field.

I stand by my claim: Currently its a BUG to display the "MyTag" content in the "Tags" column/field.

It's only a bug because they displayed part of an unimplimented feature before it was ready to go live. I stand by Steve's earlier answer. They should keep the column hidden until that feature is implemented.

JimTowler

https://community.logos.com/discussion/comment/127897#Comment_127897

I stand by Steve's earlier answer. They should keep the column hidden until that feature is implemented.

OK - I see we read it two different ways.

I was thinking Steve suggested that I should leave the column hidden. But thats the point of my "BUG" claim. Its confusing if users don't know which is the real one, and the fake only partly works, and will act different later.

If instead, you both are saying Logos should hide the column until it means something, I agree!

Rosie Perera

https://community.logos.com/discussion/comment/127899#Comment_127899

If instead, you both are saying Logos should hide the column until it means something, I agree!

Yes, I read his comment as saying Logos should hide it, because it was a response to your saying they should fix it by making it blank.

I wouldn't expect people to know to hide it if they are confused about what it's for.

steve clark

https://community.logos.com/discussion/comment/127901#Comment_127901

Sorry for my lack of clarity earlier. Thanks Rosie for making the the thought clear.

Was thinking that this is an aggravating bug, but there are many other issues that we all are waiting for Logos to deal with first. And by simply hiding that column from the users would hopefully be simple and free them to proceed with the more critical issues.