[ckan-dev] dataset urls

Rufus Pollock rufus.pollock at okfn.org
Tue Apr 24 18:52:16 UTC 2012


On 24 April 2012 15:32, David Raznick <kindly at gmail.com> wrote:
>
>
> On Fri, Apr 20, 2012 at 1:50 PM, Rufus Pollock <rufus.pollock at okfn.org>
>
>
> My take on this is that we should just have a slightly less ugly permanent
> url based off the uuid.  This would look like something base64 encoded and
> have a one to one mapping with the uuid.  I have not worked out the mapping
> yet but as uuids are in hex you could get them shorter and without the
> hyphens. So the url would be /dataset/~afdXZz34rfdsafewrA.

At best you can get from 36 characters to ~20:

<https://github.com/okfn/datautil/blob/master/datautil/id.py#L4>

It's still terrible from a UX point of view [1]. I certainly agree
disqus identifier should run off pure id but don't think disqus_url
should as I have said :-)

rufus

[1]: http://trac.ckan.org/ticket/2321


> The other option in to readd an auto id column to the dataset table and use
> that.  I still think we should keep the uuid though for harvesting purposes.

Looking back I wouldn't use uuid's again unless we had to for some
reason. I would certainly argue that related stuff and anything else
should use auto-increment if at all possible.

@Ross: are we using ints for related stuff table?

Rufus




More information about the ckan-dev mailing list