parameter &norefer=1 not preserved at catalog link at tag/foo&norefer=1 page

Hi! I found an minor issue: At combined tags one can click on whatever tags are combined together.

For the tag chess I can click on ŝako

a) I can see You use: ŝako (5) .

b) The page continues with:
Using the tag ŝako
gangleri (5), Bibliotekisto (1)

The links there are using &tag=%C5%9Dako&alias=1. This is exactly the opposite.

Well, what do you want? Should the subpage link to sako alone, or sako and its aliases (eg., chess)?

Please use either &alias=0 (my preference) or no parameter because all listed users are using this variant tag.

----

BTW: I realised that for the tag ŝako it does not make any difference if &alias=0, &alias=1 or no parameter is used.

My assumption was that &alias=1 will return all works / books regardless if the tag is the "dominant" tag or not. Not shure if this behaviour is exactly was was intended; if al users understand it the same way.

I don't see an alias parameter in any of the links on that page. What I do see is a norefer parameter to get the tag page without combining it with its parent tag (although it does still show it with its sub-tags if it has any). And I like the way it works, although a multiple-layer hierarchy of tags is a but confusing.

>3 gangleri:

Right. I understand what the feature does, but is it exposed anywhere?

I "experienced" a small stoke last week but typing abilities are 80% back today.

There are many other examples of tag combinations:
Please look at
http://www.librarything.com/tag/Nietzsche and
http://www.librarything.com/tag/friedrich+nietzsche&norefer=1
Such tag combinations are exceptions: Kafka, Camus, Bartok, Shakespeare, (also tag Eliade); Hitler, Stalin, Mussolini
http://www.librarything.com/tag/Mikhail+Botvinnik
http://www.librarything.com/tag/Spassky

http://www.librarything.com/tag/friedrich+nietzsche&norefer=1 is a link accessible via LT GUI; Also http://www.librarything.com/catalog/ThomasMann&tag=friedrich+nietzsche&a... is accessible via LT GUI. These are not "constructed" examples.

So &alias=1 / 0 etc. are part of LT GUI. The question is how to get the most benefit and a high fexibility at reasonable (implementation and performance) costs.

On the tag page, in the "Using the tag tag" section, the count in parentheses after each member name has the &alias=1 parameter.

Edited to add: I had a friend who had a stroke a few years back; I'm very glad that yours was a small one, and hope you make a full recovery.

> Thanks!

6> So &alias=1 / 0 etc. are part of LT GUI. The question is how to get the most benefit and a high fexibility at reasonable (implementation and performance) costs.

I think you're mistaking the URL location as being part of the UI. It's not, it's part of the implementation. It's kind of a gray area, sometimes, because I might tell you to go to a URL like this:
http://www.librarything.com/work/5403381

But really, when you start getting URLs that have a lot of URL parameters and such and them, you're much more in the territory of implementation rather than exposed UI. In much the same way, in your catalog you click on the "permalink" to get an "official" supported URL. You can't always just grab the URL you're seeing in the location bar and expect it to do what you want.

(Hope you're back to 100% soon!)

This is related to the discussion on http://www.librarything.com/topic/100161, where it was questioned whether there was any way in the UI to get a link with &alias=1. The bug could be rephrased without reference to the implementation detail that caused the problem, but gangleri did the investigation to identify the cause of the problem. He just wasn't clear enough on how to reproduce it from the UI.

10> True - good point.

Closing.