Bug 7689

Summary: add possibility to hide my tags in opac
Product: Koha Reporter: Stéphane Delaune <stephane.delaune>
Component: OPACAssignee: Stéphane Delaune <stephane.delaune>
Status: CLOSED INVALID QA Contact: Ian Walls <koha.sekjal>
Severity: enhancement    
Priority: P5 - low CC: ssammons
Version: Main   
Hardware: All   
OS: All   
GIT URL: Change sponsored?: ---
Patch complexity: --- Documentation contact:
Documentation submission: Text to go in the release notes:
Version(s) released in:
Circulation function:
Attachments: proposed patch

Description Stéphane Delaune 2012-03-09 09:33:55 UTC

    
Comment 1 Stéphane Delaune 2012-03-09 11:02:32 UTC
Created attachment 8114 [details] [review]
proposed patch

to reproduce :
with opac'tag sysprefs enable, connect in opac with, search notices, check a few search results, the top search results choose "add to" cart and click save. open the cart, check the appropriate documents click on the tag, enter a name tag and ok. After clic on your borrower name to go to your account and click on my tags. You have a new Hide my tags link
Comment 2 Owen Leonard 2012-03-09 16:55:07 UTC
What is the purpose of this change?
Comment 3 Shane Sammons 2012-03-09 17:17:02 UTC
I have to second the purpose. Considering you can delete a tag, and you are not disabling the tagging feature. What does hiding your tags accomplish?
Comment 4 Stéphane Delaune 2012-03-19 14:15:53 UTC
the purpose is to adding a button to hide/show "my tags" for logged users in opac ...
Comment 5 Shane Sammons 2012-03-19 15:23:36 UTC
I think we are unclear on the purpose of hiding them, they are the users unique tags, they only show up in the "My Tags" link when clicked.

Is this to prevent them from showing in search results, for the individual users "My Tags"? I.E. I tag a book "FUN", and user B tags it "FUNNY", and user C is looking at tags and can see my "FUN" and user B's "FUNNY" tag?

That is what we mean by purpose...what are you accomplishing by hiding these tags?
Comment 6 Stéphane Delaune 2012-03-22 09:40:46 UTC
It was a feature requested by a customer, but it is in fact not pertinent.