CKAN: Ticket Query

#404: Make registries pluggable

pudo — Mon, 09 Aug 2010 09:38:10 GMT

Allow using different indexes, including ckan, file, dcat, ...

#405: Retrieval options for package resources

rgrp — Mon, 09 Aug 2010 09:40:06 GMT

Download Command (was install command) should support the following modes:

Download only the first listed resource (current behaviour, slightly arbitrary)
Download resources by interactive selection
Download resources by MIME type (cf #235)
Download all resources.

#406: Download sub-system

rgrp — Mon, 09 Aug 2010 09:40:22 GMT

Factor out current downloader into dedicated download subpackage, abstract interface and make it pluggable so we can have downloaders loaded as per type of resource to download.

Also rename InstallCommand? -> DownloadCommand?

And we should support interactive retrieving of resources ...

Implementation Ideas

for resources in pkg.resources:
    # datapkg/hg
    load_storage_handler(resource.format)

#409: Refactor cli to be more 'pluggable'

rgrp — Mon, 09 Aug 2010 10:10:59 GMT

~~(Load cli commands from setuptools entry point name datapkg.cli)~~
Document how other can write new commands
Refactor base Command class to support this pluggability (if necessary)

#433: Data package metadata in the Egg

wwaites — Tue, 17 Aug 2010 20:57:40 GMT

Still not sure if we shouldn't use the existing setuptools machinery to manage this -- there is already a way to get at the metadata. In any event, I've just made an addition to datapkg that makes it possible to put datapkg_sources as a dictionary in your package's setup.py. Afterwards it is possible to pull the metadata out of the egg. Of course this could easily be changed to save the information in whatever form, indeed if you pass it a string instead of a dictionary it will just write whatever you gave it into the datapkg_sources.spec. The point is, I think that the egg is a good place to stuff this information.

For non-python users, it is always possible to simply put up the datapkg_sources.spec somewhere on the web so they can directly retrieve the data files.

From the docstring::

    This is the implementation for an [egg_info.writers] entrypoint.
    Datapkg adds an argument to setuptools's setup() function called
    datapkg_sources. The argument should be a dictionary of the form:
    .. code-block:: python
        setup(
            ...,
            datapkg_sources = {
                "cra2009" : "http://www.hm-treasury.gov.uk/d/cra_2009_db.csv"
            }
        )
    The result of this is that there will be a file in the egg called
    datapkg_sources.spec that looks like this::
        [sources]
        cra2009=http://www.hm-treasury.gov.uk/d/cra_2009_db.csv
    How do you get at this data? Simple::
    .. code-block:: python
        import pkg_resources
        dist = pkg_resources.get_distribution("ukgov_treasury_cra")
        spec = dist.get_metadata("datapkg_sources.spec")
    and 'spec' will be the contents of the file as a string.

#964: Create Resource Downloader and make it pluggable

rgrp — Wed, 09 Feb 2011 00:23:24 GMT

In downloading packages we need to download resources and we need a ResourceDownloader? object for this. these should be pluggable so that we can add support for different types of resources.