Skip to content
This repository

add author/origin info to search results' HTML representation #941

Closed
FND opened this Issue · 8 comments

4 participants

FND Chris Dent Mario Pietsch Ben Paddock
FND
FND commented

search results can be somewhat confusing because there's no obvious hint as to the respective tiddlers' origin

e.g. http://tiddlyspace.com/search?q=Manifesto%20Review%20201206 currently results in the following:

20120629
Manifesto Review 201206
Manifesto Review 201206
Manifesto Review 201206

I reckon it would be useful if the space/creator/modifier was displayed alongside each tiddler title. Maybe the respective date too. And toys!

Chris Dent
Owner
cdent commented

In the past this wasn't done because search results are driven by the same code that lists tiddlers from bags and recipes. In those latter context listing space/creator/modifier is fairly redundant.

However, there's no reason why we can't use a different template for showing search results from the one used for generic tiddlers.

Mario Pietsch
pmario commented

However, there's no reason why we can't use a different template for showing search results from the one used for generic tiddlers.

+1

Chris Dent cdent referenced this issue from a commit
Chris Dent cdent Return search results in their own template
If tiddlers.is_search set template to search.html
otherwise use tiddlers.html

This starts, but does not finish, #941. To finish somebody
needs to cook the template to display the data that should
already be available on the objects in the tiddlers array.
83dfa05
Ben Paddock
Owner
pads commented

What would you want to show (or not) if the tiddler does not belong to a space (i.e a system-wide one)? At the moment it will just show "None".

FND
FND commented

I suppose the bag would make sense - so instead of "MyTiddler (@MySpace)" it might say "MyTiddler (MyBag)".

Ben Paddock pads referenced this issue from a commit
Ben Paddock pads Fix #941, using tiddler modifier instead of creator and link to bag t…
…iddlers rather than the bag itself.
3911276
Ben Paddock pads closed this issue from a commit
Ben Paddock pads Fix #941, using tiddler modifier instead of creator and link to bag t…
…iddlers rather than the bag itself.
3911276
Ben Paddock pads closed this in 3911276
Chris Dent cdent reopened this
FND
FND commented

@cdent's adjustments (e1eecdd) seem a like a nice improvement. It essentially looks like this now:

[[TITLE|FRIENDLY_URI]] modified DATE by [[@AUTHOR]] in [[SPACE_OR_BAG]]

However, dates currently look like this: Sun, 22 Jul 2012 11:36:03 GMT - that pretty much ruins it (noise!), though @cdent already mentioned as much.

Not sure whether using relative times is a great idea though, as it might suggest content is stale when it's merely stable (i.e. don't twitterize it).

As for the "extra verbiage", I don't like the pseudo-sentence structure, preferring "TITLE by AUTHOR in SPACE (DATE)" instead - but I suppose Regular Folks and hipster companies might disagree.

Ben Paddock
Owner
pads commented

I like the structure that FND recommends. I also think the timeago date format is good for reducing noise. Maybe hovering over the date brings up a tool tip with the extra noise if the user wants (i.e. the dd/mm/yyyy hh:mm:ss z).

I also think, as cdent says, the site icons in place of bullet points would make it look nicer.

It would be good to get some agreement on this, I'm quite happy to make the changes.

Chris Dent
Owner

There's some stuff written up here http://searchdesign.tiddlyspace.com that Jon Lister and his chums may spend some time looking at and thinking about.

Ben Paddock pads referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
Ben Paddock pads referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
Chris Dent
Owner

For further work in this vein see http://searchdesign.tiddlyspace.com/

Chris Dent cdent closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.