<div dir="ltr">I, for one, am hoping that faceted_search shows up in the redesign. <br><br>I have worked with it, and would say that it is, by far, the best way I have seen to search through copious amount of content. I am uncertain how it performs however, and I am sure that will be a concern.<br>
<br>Also, can not Robert Douglass' Apache Solr integration work with faceted_search, giving a fairly powerful overall search?<br><br>Another thing to keep in mind is that faceted_search works WITH taxonomy terms, so a mix of being able to free-tag something, and use a faceted search to retrieve it could be pretty useful.<br>
<br>Thanks,<br> <br clear="all">Patrick Teglia<br>
CrashTest_<br><br><div class="gmail_quote">On Mon, Sep 8, 2008 at 12:47 PM, Alan Palazzolo <span dir="ltr"><<a href="mailto:me@alanpalazzolo.com">me@alanpalazzolo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
My two cents on this. I would propose two structures in unison.<br>
<br>
1) Formal tagging hierarchal structure, specific categories<br>
2) Free tagging<br>
<br>
This allows for both ways of finding information. It creates a<br>
structure that is necessary for such a large amount of information while<br>
also giving opportunity for organic growth.<br>
<font color="#888888"><br>
--<br>
Alan<br>
<a href="http://alanpalazzolo.com/" target="_blank">http://alanpalazzolo.com/</a><br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
<br>
On 9/8/08 1:23 PM, Addison Berry wrote:<br>
> Yep, I agree that the way the docs are organized/categorized/found<br>
> needs to change in the redesign. I'd love a flexible way for people to<br>
> get to the docs they need in different ways. This is a major thing<br>
> that I want us to work with Mark Boulton Design (MBD) on. I am<br>
> gathering together a list of features/dream requests with regards to<br>
> docs and hope to post a mail to this list by the end of the week so we<br>
> can be a bit organized about brainstorming, prioritizing and giving<br>
> feedback to MBD. I'm so frickin excited we have not just design, but<br>
> actual IA and UX work going into the redesign.<br>
><br>
> Faceted search is awesome stuff as well and I dare say that is<br>
> something that the redesign search team will be looking at. Their<br>
> first hurdle is to figure out how to have robust search across<br>
> multiple <a href="http://drupal.org" target="_blank">drupal.org</a> sites and I have no idea where something like<br>
> faceted search is on their radar. Would be awesome if it makes it into<br>
> the redesign, but I'll leave that to those experts. Doesn't hurt to<br>
> say that docs team thinks it would be neat-o-keen, though. :-)<br>
><br>
> - Addi<br>
><br>
> On Sep 8, 2008, at 1:58 PM, Lee Hunter wrote:<br>
><br>
>> I don't think there's any way it could be worse than the utterly<br>
>> inscrutable architecture we have now.<br>
>><br>
>> :)<br>
>><br>
>> Using the Cake example, one click gets you all the database articles.<br>
>> On the current Drupal.org you would probably have to click *hundreds*<br>
>> of times (quite literally) before you rounded up everything on<br>
>> databases (and personally I'd get lost and give up long before I got<br>
>> there).<br>
>><br>
>> The Cake example, does show one of the limitations in that you might<br>
>> get an overwhelming number of results, however this is still<br>
>> preferable to not even knowing where to start.<br>
>><br>
>> To solve the issue of too many results, one approach I really like is<br>
>> the guided search or faceted search, which is used on quite a few<br>
>> large and complex sites. In fact, there's a module here:<br>
>><br>
>> <a href="http://drupal.org/project/faceted_search" target="_blank">http://drupal.org/project/faceted_search</a><br>
>><br>
>> Faceted search has several advantages, one of which is that you can<br>
>> see at a glance how your search could be broadened or narrowed by<br>
>> choosing from a list of options. Using the "database" example, there<br>
>> might well be too many results to be useful, but the faceted search<br>
>> would allow me to easily narrow it down by clicking on the "facets" or<br>
>> related tags (and I'd also see how many articles can be found in each<br>
>> related tag).<br>
>><br>
>> Re. the redesign project, that's one reason I'm raising this issue<br>
>> again now, because I think it would be just tragic if the current<br>
>> non-architecture gets baked into the redesign. To my mind, the total<br>
>> lack of navigability in the documentation is by far the most pressing<br>
>> problem with Drupal.org.<br>
>><br>
>> A while back, I'd actually proposed an alternative architecture for<br>
>> the documentation (<a href="http://drupal.org/node/199388" target="_blank">http://drupal.org/node/199388</a>) but I'm now thinking<br>
>> that some kind of organic tagging scheme would work better for this<br>
>> kind of site.<br>
>><br>
>> Lee Hunter<br>
>> Technical Editor<br>
>><br>
>><br>
>> On Mon, Sep 8, 2008 at 1:37 PM, Steven Peck <<a href="mailto:sepeck@gmail.com">sepeck@gmail.com</a>> wrote:<br>
>>> Other than saying 'tags will help' do you have a better hierarchy<br>
>>> suggestion?<br>
>>><br>
>>> My experience with tags in general on many other sites has been that<br>
>>> they also pollute search results into rabbit warrens of unrelated<br>
>>> pages. I am not against tags, just not seeing them as a magic bullet<br>
>>> currently. I am loathe to just 'tack things on' while we have a<br>
>>> redesign project starting up.<br>
>> --<br>
>> Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank">http://drupal.org/project/issues/documentation/</a><br>
>> List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank">http://lists.drupal.org/pipermail/documentation/</a><br>
><br>
> --<br>
> Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank">http://drupal.org/project/issues/documentation/</a><br>
> List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank">http://lists.drupal.org/pipermail/documentation/</a><br>
--<br>
Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank">http://drupal.org/project/issues/documentation/</a><br>
List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank">http://lists.drupal.org/pipermail/documentation/</a><br>
</div></div></blockquote></div><br></div>