[ckan-dev] inconsistency between CKAN website and API results with groups

Rufus Pollock rufus.pollock at okfn.org
Fri Jul 15 12:48:23 UTC 2011


On 15 July 2011 11:09, James Gardner <james at 3aims.com> wrote:
> Hi Rufus,
>
> Just to clarify, this isn't in the current iteration which is described in
> the "ckan-current-sprint" milestone here:

Apologies, In my explanation I confused being in the next major
'release' (ckan-v1.5) with current iteration. Thanks also for detail
on new development methodology which sounds great.

Rufus

> http://trac.ckan.org/query?status=assigned&status=new&status=reopened&group=milestone&max=1000&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&col=component&order=owner
>
> Rather it is currently scheduled in the milestone for the 1.5 release.
>
> The difference is important because in our new working practices we only
> work on the things in the current iteration, not on other features or bugs.
> At the end of an iteration Ira will decide (after discussion) which features
> go into the next iteration. That distinction is important because some of
> these bugs may be best solved with larger scale refactors and will therefore
> have to wait slighlty rather than being implemented immediately at the risk
> of introducing different problems. Search as a whole is an area the team
> need to look at.
>
> Cheers,
>
> James
>
>
>
>
>
> On 14/07/11 00:13, Rufus Pollock wrote:
>>
>> On 13 July 2011 20:43, Sean Hudson<sean.hudson at opencolorado.org>  wrote:
>>>
>>> I am hitting unexpected behavior from the CKAN API that doesn’t make
>>> sense
>>> to me.  I don’t know if something is configured incorrectly or just not
>>> working properly on the server.
>>
>> Fixed :-) Did:
>>
>> paster --plugin ckan search-index rebuild --config us_co.ini
>>
>> Reason for your problem is that (some) changes made to the DB are not
>> getting properly re-indexed into the search index (which is run on
>> SOLR). Specifically I believe what you are describing is an instance
>> of this reported bug (currently owned by David):
>>
>> <http://trac.ckan.org/ticket/1140>
>>
>> As you can see that is scheduled for fixing in the current iteration
>> and which we can then deploy for your instance.
>>
>> Rufus
>>
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>
>



-- 
Co-Founder, Open Knowledge Foundation
Promoting Open Knowledge in a Digital Age
http://www.okfn.org/ - http://blog.okfn.org/




More information about the ckan-dev mailing list