I've got experience using Solr, hopefully will have some time to work on that a bit this summer.<br clear="all">--<br>contact info:<br><a href="http://www.johndbritton.com" target="_blank">http://www.johndbritton.com</a><br>
@johndbritton - <a href="http://twitter.com/johndbritton" target="_blank">http://twitter.com/johndbritton</a><br>
<br><br><div class="gmail_quote">On Mon, May 23, 2011 at 12:00 PM, Pippa Buchanan <span dir="ltr"><<a href="mailto:Pippa.Buchanan@gmail.com">Pippa.Buchanan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
+1 for google search in the interim.<div><div></div><div class="h5"><br><br><div class="gmail_quote">On 23 May 2011 15:55, Jessica Ledbetter <span dir="ltr"><<a href="mailto:jessica@jessicaledbetter.com" target="_blank">jessica@jessicaledbetter.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We could start with a google search like Zuzel mentioned and then swap<br>
out for our own down the road. Right now the search results from<br>
Google are not that great but maybe with enough fine tuning it will do<br>
as a stopgap.<br>
<br>
<br>
On Mon, May 23, 2011 at 9:38 AM, Jessy Kate Schingler<br>
<<a href="mailto:jessy@jessykate.com" target="_blank">jessy@jessykate.com</a>> wrote:<br>
> Cool, I'm not familiar with sphinx search. I wonder if Paul has any<br>
> thoughts/experience on sphinx search versus solr? Adding him to cc :)<br>
><br>
> Jessy<br>
><br>
> On Monday, May 23, 2011, zuzel.vp <<a href="mailto:zuzel.vp@gmail.com" target="_blank">zuzel.vp@gmail.com</a>> wrote:<br>
>> On Mon, May 23, 2011 at 7:16 AM, Jessy Kate Schingler<br>
>> <<a href="mailto:jessy@jessykate.com" target="_blank">jessy@jessykate.com</a>> wrote:<br>
>>> re user sign up-- sorry i wasn't clear. i meant signing up for a course, not<br>
>>> an account. he already had an account, but couldn't find where to sign up<br>
>>> for a specific course that was open for sign up. for these courses, could we<br>
>>> have a bigger button(s) near the top of the course homepage?<br>
>><br>
>> <a href="http://p2pu.lighthouseapp.com/projects/71002/tickets/337-move-follow-participate-and-contact-organiser-buttons-above-the-fold" target="_blank">http://p2pu.lighthouseapp.com/projects/71002/tickets/337-move-follow-participate-and-contact-organiser-buttons-above-the-fold</a><br>
>><br>
>>> re search, have you thought about something like<br>
>>> solr? <a href="http://lucene.apache.org/solr/" target="_blank">http://lucene.apache.org/solr/</a><br>
>>> solr indexes along any fields you define (typically multiple), to enable<br>
>>> fast real time search given a large variety of potential parameters/filters.<br>
>>> it trades off space (ie, the indexes can get big) for speed and scalability,<br>
>>> basically. it's used on many "high traffic<br>
>>> websites": <a href="http://wiki.apache.org/solr/PublicServers" target="_blank">http://wiki.apache.org/solr/PublicServers</a>.<br>
>>> i set up solr for one of my projects at sunlight and worked a lot with index<br>
>>> definitions; if there's interest i would be happy to set it up for us. it's<br>
>>> free and open source. index space isn't an issue for us AFAIK, but the main<br>
>>> potential drawback i could imagine is that our dev server probably couldn't<br>
>>> handle the extra load. thoughts?<br>
>><br>
>> Any experiments on implementing search are welcome, and now that we<br>
>> can import course content from the old site it will be easier to test<br>
>> performance in a dev instance. However, I recommend not including it<br>
>> in production until we are sure both search and indexing works for<br>
>> larges amounts of data (at least comparable to what we have in the old<br>
>> site right now), and that it does not cause lock errors.<br>
>><br>
>> The last time we meet with Paul we talked about<br>
>> <a href="http://sphinxsearch.com/" target="_blank">http://sphinxsearch.com/</a> with is used by<br>
>> <a href="https://github.com/jbalogh/zamboni/tree/master/apps/search" target="_blank">https://github.com/jbalogh/zamboni/tree/master/apps/search</a>. That is<br>
>> another one we could experiment with, though it also has its<br>
>> performance issues.<br>
>><br>
>> --<br>
>> Thanks,<br>
>> Zuzel<br>
>><br>
>>> Jessy<br>
>>> --<br>
>>> <a href="http://jessykate.com" target="_blank">http://jessykate.com</a><br>
>>><br>
>>><br>
>>> On Mon, May 23, 2011 at 1:35 AM, Philipp Schmidt <<a href="mailto:phi.schmidt@gmail.com" target="_blank">phi.schmidt@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Search is a problem we hoped batucada would solve.<br>
>>>><br>
>>>> Zuzel: could you check with Paul what the status on that is?<br>
>>>><br>
>>>> To reduce confusion on the courses list page, we could also consider<br>
>>>> listing draft courses on a separate page.<br>
>>>><br>
>>>> P<br>
>>>><br>
>>>> On 23 May 2011 12:17 AM, "zuzel.vp" <<a href="mailto:zuzel.vp@gmail.com" target="_blank">zuzel.vp@gmail.com</a>> wrote:<br>
>>>> > Sign up/Registration of new accounts was temporarily hidden on<br>
>>>> > purpose. Before the migration occurs we need users not to create new<br>
>>>> > accounts unless they had never used the old site so they keep their<br>
>>>> > identities. After the creation of new accounts in the old site is<br>
>>>> > disabled we will migrate all user accounts to the new site. At that<br>
>>>> > point we will not need anymore the current restriction of not allowing<br>
>>>> > any user to register accounts with username/email from the old site<br>
>>>> > (unless they proved that they are the same person by login in with<br>
>>>> > their username and password from the old site). After the migration we<br>
>>>> > can make signup more visible again (either by having all the forms on<br>
>>>> > the same page or by adding a direct link like in drumbeat/batucada).<br>
>>>> ><br>
>>>> > Most of the tickets are not assigned to a milestone now because we had<br>
>>>> > to re-schedule things in order to move the migration to an early date.<br>
>>>> > However even before this, search was assigned I think to milestone 0.9<br>
>>>> > because it is a feature hard to implement in a way that scales. All<br>
>>>> > solutions I have seen including search in a django project tend to<br>
>>>> > become considerable slow when they are setup in a real world scenario.<br>
>>>> > One solution could be to rely google for including search capabilities<br>
>>>> > (<a href="http://www.google.com/cse/" target="_blank">http://www.google.com/cse/</a>).<br>
>>>> ><br>
>>>> > Thoughs?<br>
>>>> ><br>
>>>> > --<br>
>>>> > Thanks,<br>
>>>> > Zuzel<br>
>>>> ><br>
>>>> > On Sun, May 22, 2011 at 5:13 PM, Alison Jean Cole<br>
>>>> > <<a href="mailto:alisonjean.cole@gmail.com" target="_blank">alisonjean.cole@gmail.com</a>> wrote:<br>
>>>> >> Agree with both of Jessy's suggestions.<br>
>>>> >><br>
>>>> >> ALISON<br>
>>>> >> <a href="http://new.p2pu.org/en/alison/" target="_blank">new.p2pu.org/en/alison/</a><br>
>>>> >><br>
>>>> >><br>
>>>> >><br>
>>>> >><br>
>>>> >><br>
>>>> >> On Sat, May 21, 2011 at 10:48 AM, John Britton<br>
>>>> >> <<a href="mailto:public@johndbritton.com" target="_blank">public@johndbritton.com</a>><br>
>>>> >> wrote:<br>
>>>> >>><br>
>>>> >>> I also think we should make the signup/signin box happen on the same<br>
>>>> >>> page<br>
>>>> >>> as opposed to redirecting to a new page, less friction overall.<br>
>>>> >>> --<br>
>>>> >>> contact info:<br>
>>>> >>> <a href="http://www.johndbritton.com" target="_blank">http://www.johndbritton.com</a><br>
>>>> >>> @johndbritton - <a href="http://twitter.com/johndbritton" target="_blank">http://twitter.com/johndbritton</a><br>
>>>> >>><br>
>>>> >>><br>
>>>> >>> On Sat, May 21, 2011 at 1:43 PM, Jessy Kate Schingler<br>
>>>> >>> <<a href="mailto:jessy@jessykate.com" target="_blank">jessy@jessykate.com</a>> wrote:<br>
>>>> >>>><br>
>>>> >>>> 2 pieces of feedback on someone looking at the new.p2pu site.<br>
>>>> >>>> i had recommended they create an account in order to sign up for a<br>
>>>> >>>> specific course. so of course the first thing they looked for was<br>
>>>> >>>> a search<br>
>>>> >>>> box. there's quite a lot of courses now, so i wonder if the "search<br>
>>>> >>>> box"<br>
>>>> >>>> ticket on lighthouse might deserve to be moved up a bit in priority<br>
>>>> >>>> (currently "unscheduled")?<br>
>><br>
><br>
> --<br>
><br>
> Jessy<br>
> --<br>
> <a href="http://jessykate.com" target="_blank">http://jessykate.com</a><br>
> _______________________________________________<br>
> p2pu-dev mailing list<br>
> <a href="mailto:p2pu-dev@lists.p2pu.org" target="_blank">p2pu-dev@lists.p2pu.org</a><br>
> <a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
><br>
<font color="#888888"><br>
<br>
<br>
--<br>
Jessica Ledbetter<br>
<a href="http://jessicaledbetter.com" target="_blank">http://jessicaledbetter.com</a><br>
_______________________________________________<br>
p2pu-dev mailing list<br>
<a href="mailto:p2pu-dev@lists.p2pu.org" target="_blank">p2pu-dev@lists.p2pu.org</a><br>
<a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
</font></blockquote></div><br>
</div></div><br>_______________________________________________<br>
p2pu-dev mailing list<br>
<a href="mailto:p2pu-dev@lists.p2pu.org">p2pu-dev@lists.p2pu.org</a><br>
<a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
<br></blockquote></div><br>