Tags are Sorted but...

[BetterRed]

I create a custom column like tags - fandom/Fandom

When I enter Tags they are sorted in the Book List and in Book Details

When I enter Fandoms they are sorted in the Book List but they are not sorted Book Details

If I use the template {tags:sublist(0,1,\,)} I get the first Tag in an alpha sorted list.

If I use the template {#fandom:sublist(0,1,\,)} I get the first Fandom I entered.

Is there any way I can get a list of Tags in the order I entered them?

BR

[BookJunkieLI]

Any of these three options will keep them in the order that you enter the information:

Column like tags with Contains Names checked
Text, column shown in the tag browser
Long Text like comments

I'm currently using all three in my import library for pairings because I can't decide which method I prefer.

[davidfor]

BR: This was raised earlier in the year. Kovid said no because of problems with templates and, from memory, he thought that alphabetical was more logical. Plus he thought the metadata sources were sorting them. Personally, I enter them in order of importance, so I would like to display them that way. I did have as look at what was needed to change it and add a tweak. There wasn't that much, but there was one spot the tags were displayed that I couldn't find.

[chaley]

Originally Posted by BetterRed

Is there any way I can get a list of Tags in the order I entered them?

BR

I have submitted code to Kovid for a new formatter function "raw_list", an analog of the existing raw_field function. It returns the list in the order found in the db. Example:

{tags:'sublist(raw_list($, ','), 0, 1, ',')'}

The code is in source now.

[BetterRed]

@Bookjunkie - Tags is a built in column I cannot change its type.

@davidfor - thanks, no secret list_unsort function then

Can you recall if the opposite solution was considered, i.e a custom column with Column Type of "Comma separated text, like tags, shown in the tag browser" was be sorted like tags are always sorted. Yes they are sorted in the Book List, but not in Book Details and hence not when used in a template.

If a '!' was prepended to the Tag that I want first, that would force it to the top if the list.

Can someone furnish me with a template that will examine the first character of the first tag and if it is '!' then return the substring of first tag from position 1 to end, otherwise return the first tag. I tried but it didn't work

So !Underpass would return Underpass and Crossover would return Crossover.

Originally Posted by chaley

I have submitted code to Kovid for a new formatter function "raw_list", an analog of the existing raw_field function. It returns the list in the order found in the db..

Added : @chaley - yet again

BR

[chaley]

Originally Posted by BetterRed

Can someone furnish me with a template that will examine the first character of the first tag and if it is '!' then return the substring of first tag from position 1 to end, otherwise return the first tag. I tried but it didn't work

So !Underpass would return Underpass and Crossover would return Crossover.

{tags:'re(sublist($, 0, 1, ','), '^!', '')'}

[Irian]

Originally Posted by chaley

{tags:'sublist(raw_list($, ','), 0, 1, ',')'}

Tried this, but unfortunately, it only returns the alphabetically sorted tag list, not the original one that is also displayed in the metadata.

[chaley]

Originally Posted by Irian

Tried this, but unfortunately, it only returns the alphabetically sorted tag list, not the original one that is also displayed in the metadata.

Actually it returns incorrect information. The raw_list function requires a field name, not a value.

Try

{:'sublist(raw_list('tags', ','), 0, 1, ',')'}

However, I must note that depending on the order of entry of tags is problematic. If *anything* happens to that first tag, for example a case change operation, then the order will change. The order can change for other reasons as well. If the "first" tag is as important as it appears to be then you should create a text custom column (not like tags) and enter it there.

[BetterRed]

@chaley - I must have overlooked your 'mistake', I probably went to the manual when the change was released and worked from there.

But in the main, to force an item to be first, second and third in a sorted list, I use the time honoured fudge of pre-pending values with a bang (!), a crunch (#), and a hat (^).

BR

[Irian]

Thanks chaley, works fine. I would prefer using tags, but I understand the danger there. Anyway, at least I know have the choice.