[ckan-dev] harvesting and ckan geo extensions

[james@3aims.com]

OK, that's the first I've heard of a demo to the EC. Let's discuss it offline.

James

----- Reply message -----
From: "William Waites" <ww at styx.org>
Date: Wed, Apr 6, 2011 11:14
Subject: [ckan-dev] harvesting and ckan geo extensions
To: "James Gardner" <james at 3aims.com>
Cc: "CKAN Development Discussions" <ckan-dev at lists.okfn.org>, "David Read" <david.read at okfn.org>, "Adrià Mercader" <amercadero at gmail.com>


Sorry really spaces - odd that itseemed to work n the test environment.

Re API URL I'll pull where i saw that out later when I'm at a computer.

Re relative URLs this is actually an error. But if you need it to avoid fines...


Re other improvements I'm looking at this from the pov of a demo to the ec so priorities are slightly different. I would rather build on Adria 's work but if you are now saying wait a month then we'll have to think of something new to do. No problem I'm good at thinking of things to do.

Anyways these were comments on how the system could be improved not dictats of what must be done now


James Gardner <james at 3aims.com> a écrit :

>Hi all,
>
>On 06/04/11 10:21, David Read wrote:
>> 2011/4/6 Adrià Mercader<amercadero at gmail.com>:
>>> Hi William and others,
>>>
>>> El 5 d’abril de 2011 23:14, William Waites<ww at styx.org>  ha escrit:
>>>> So far so good, I added some tweaks to the documentation for how to
>>>> configure the plugins, and reminders to actually install the package
>>>> and put the requirements in the setup.py so that they get installed
>>>> comme il faut.
>>> Aren't plugins supposed to be separated by spaces in the ini file, not commas?
>>>     ckan.plugins = cswserver dgu_form_api harvest
>>> instead of
>>>     ckan.plugins = cswserver,dgu_form_api,harvest
>
>Yes, we use spaces Will.
>
>>>> In the instructions for the API URL, I may be wrong but I believe that
>>>> the convention for ckanclient is to put http://exmaple.org/api not
>>>> just http://example.org/ if I am not wrong about this it should
>>>> probably be changed for consistency's sake.
>>> Not exactly sure what you mean. Do you mean the default value in ckan.api_url?
>>> In any case, this will probably get removed in the current refactoring
>>> as we won't need
>>> to query the api
>> Hmm the docs have an example:
>>
>> ckan.api_url=http://scotdata.ckan.net/api
>>
>> So maybe Will is talking about a different setting than ckan.api_url?
>
>We want relative URLs here to support DGU temporarily. Please, please, 
>please don't go changing things like this at this stage. Once the code 
>is stable and deployed for DGU we can look at improvements for wider 
>use, but that certainly isn't our main concern 4 weeks before a major 
>deadline.
>
>>>> I notice the harvester is adding resources with relative URLs, this
>>>> seems to be a pre-existing bug not least because it prevents the
>>>> package from being edited because those fields fail validation.
>>>> The authentication arrangement in view.py should probably be slackened
>>>> a bit, since I don't think we need admin privileges to be able to just
>>>> look at a map.
>>> Agreed. I think it's made this way in the current context of DGU, but
>>> when this gets
>>> moved to a new ckanext-georelatedstuff I don't think it will be necessary
>> I don't know much about harvesting and its direction, but I put the
>> sysadmin authz requirement on all the harvest view interface and
>> matching API calls purely because it was easy, it works for DGU right
>> now, and it prompts someone to properly plan what authz we do need.
>> This might well be a protection object for a harvest source or doc,
>> along the lines of everything else. So I think rather than make a
>> piecemeal change to remove completely authz on one particular call,
>> someone should argue the whole harvesting/geo/csw thing together, in
>> light of where it's going.
>
>Again, Adria has implemented exactly what I've asked which is what we 
>need to support at the moment, sysadmin privileges are correct. We can 
>look at changing after the deadline.
>
>>>> Also if there is a viewable resource, probably we
>>>> should have a smaller map without controls on the main package page,
ms
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20110406/4588cf80/attachment-0001.html>