lesson search page
1 view
Skip to first unread message
Laurent Savaëte
Aug 13, 2012, 9:25:22 AM8/13/12
to ductus-d...@googlegroups.com
I started looking at the wire frames we put together back in December.
They're not actually that detailed, so I started by putting together an
updated mock-up based on what we have at the moment (attached).
It's focused on tag search, since that's all we have.
I'll leave the problem of full text search aside for now, it wouldn't
tremendously amend the way the search page works (but definitely the
backend).
Some comments:
- words input in the search box would turn into tags listed under
"results for:"
- the tags/types to the right will add extra tags to the "results for"
list (which would have delete buttons on each item to expand the
search), each action updating the results shown
- how do we figure out the "type/template" of a lesson after building
it? We could do this with a hidden tag (like "lesson-type:podcast" that
the editor UI doesn't show but records in the lesson). I can't really
think of another clean solution.
- I threw in a "summary of the lesson", but we don't have a way to do
this yet. For FCDs, it could be the first text element found, for text
pages, the first N characters. Ideas welcome.
- the above works under the assumption that we come to the page by
clicking a "learn French" type of link, so that the target language is
defined.
- we need to build a page listing all target languages that we can link
to from the front page via a "see all languages" link (as they won't all
fit on the current tag cloud), which in turn will send the user to the
search page.
- besides the lesson type options, we could list more commonly used
tags/search criteria. I just can't think of anything yet, but the
workings of these would be similar.
Below is a link to the Stockholm library search page, that allows
finding a library near you or by a number of criteria. I find it well made.
https://biblioteket.stockholm.se/en/bibliotek
and pretty much the same design for searching books.
https://biblioteket.stockholm.se/en/sok?freetext=bradbury
I guess the mock-up is cross-inspiration from it and the old wire frames
from December.
They're not actually that detailed, so I started by putting together an
updated mock-up based on what we have at the moment (attached).
It's focused on tag search, since that's all we have.
I'll leave the problem of full text search aside for now, it wouldn't
tremendously amend the way the search page works (but definitely the
backend).
Some comments:
- words input in the search box would turn into tags listed under
"results for:"
- the tags/types to the right will add extra tags to the "results for"
list (which would have delete buttons on each item to expand the
search), each action updating the results shown
- how do we figure out the "type/template" of a lesson after building
it? We could do this with a hidden tag (like "lesson-type:podcast" that
the editor UI doesn't show but records in the lesson). I can't really
think of another clean solution.
- I threw in a "summary of the lesson", but we don't have a way to do
this yet. For FCDs, it could be the first text element found, for text
pages, the first N characters. Ideas welcome.
- the above works under the assumption that we come to the page by
clicking a "learn French" type of link, so that the target language is
defined.
- we need to build a page listing all target languages that we can link
to from the front page via a "see all languages" link (as they won't all
fit on the current tag cloud), which in turn will send the user to the
search page.
- besides the lesson type options, we could list more commonly used
tags/search criteria. I just can't think of anything yet, but the
workings of these would be similar.
Below is a link to the Stockholm library search page, that allows
finding a library near you or by a number of criteria. I find it well made.
https://biblioteket.stockholm.se/en/bibliotek
and pretty much the same design for searching books.
https://biblioteket.stockholm.se/en/sok?freetext=bradbury
I guess the mock-up is cross-inspiration from it and the old wire frames
from December.
Ian Sullivan
Aug 13, 2012, 11:34:36 AM8/13/12
to ductus-d...@googlegroups.com
On 08/13/2012 09:25 AM, Laurent Sava�te wrote:
> I started looking at the wire frames we put together back in December.
> They're not actually that detailed, so I started by putting together an
> updated mock-up based on what we have at the moment (attached).
> It's focused on tag search, since that's all we have.
>
> I started looking at the wire frames we put together back in December.
> They're not actually that detailed, so I started by putting together an
> updated mock-up based on what we have at the moment (attached).
> It's focused on tag search, since that's all we have.
>
> Some comments:
> - words input in the search box would turn into tags listed under
> "results for:"
> - the tags/types to the right will add extra tags to the "results for"
> list (which would have delete buttons on each item to expand the
> search), each action updating the results shown
I tinkered with the layout a bit and added the result to the fluidui
> - words input in the search box would turn into tags listed under
> "results for:"
> - the tags/types to the right will add extra tags to the "results for"
> list (which would have delete buttons on each item to expand the
> search), each action updating the results shown
account page with a screenshot attached here. I like the look of your
design but got stuck trying to figure out details like whether selecting
specific lesson types added them in to the search or excluded them from
it, how to clear the selections, etc.
What do you think? I like the top row a lot but I am still not sure
about the right column.
-Ian
Jim Garrison
Sep 6, 2012, 1:19:19 AM9/6/12
to ductus-d...@googlegroups.com
On 08/13/12 06:25 (long ago, I realize), Laurent Savaëte wrote:
> - how do we figure out the "type/template" of a lesson after building
> it? We could do this with a hidden tag (like "lesson-type:podcast" that
> the editor UI doesn't show but records in the lesson). I can't really
> think of another clean solution.
I would say the original lesson template is irrelevant. What matters is
> - how do we figure out the "type/template" of a lesson after building
> it? We could do this with a hidden tag (like "lesson-type:podcast" that
> the editor UI doesn't show but records in the lesson). I can't really
> think of another clean solution.
the interactions available, and the types in the columns of those
interactions. From this information, we can infer whether it is a
picture-choice lesson or podcast or both, etc.
Ian
Oct 4, 2012, 4:13:57 PM10/4/12
to ductus-d...@googlegroups.com
Prototype available here:
http://laurent.dev.wikiotics.net/special/search?tag=target-language:en
A couple of issues we discussed briefly on the phone call this week.
- The "source-language" and "target-language" tags should ideally be
treated separately from the rest of the tags. See attached mockup for
one possible way we could do that.
- We also talked about refreshing the tag list when people run new
searches but, the more I think about, the more I wonder if we would be
better off dropping the tag list entirely. I worry that seeing the list
of all tags associated with the lessons in your search results will get
very large very quickly and end up occupying more screen space than the
actual search results.
- We need some sort of tag searching. I added that as part of the mockup
by just making the search button say it is searching both names and
tags. Given the number of lessons we currently plan, I think that would
work fine but we could also add a drop-down selection or add something
like a tag/name toggle or slider.
What do you think?
-Ian
http://laurent.dev.wikiotics.net/special/search?tag=target-language:en
A couple of issues we discussed briefly on the phone call this week.
- The "source-language" and "target-language" tags should ideally be
treated separately from the rest of the tags. See attached mockup for
one possible way we could do that.
- We also talked about refreshing the tag list when people run new
searches but, the more I think about, the more I wonder if we would be
better off dropping the tag list entirely. I worry that seeing the list
of all tags associated with the lessons in your search results will get
very large very quickly and end up occupying more screen space than the
actual search results.
- We need some sort of tag searching. I added that as part of the mockup
by just making the search button say it is searching both names and
tags. Given the number of lessons we currently plan, I think that would
work fine but we could also add a drop-down selection or add something
like a tag/name toggle or slider.
What do you think?
-Ian
Reply all
Reply to author
Forward
0 new messages