[ckan-dev] dataset urls

Toby Dacre toby.okfn at gmail.com
Fri Apr 20 12:30:04 UTC 2012


On 20 April 2012 13:11, Ross Jones <ross.jones at okfn.org> wrote:

> I'd go for option b.  The id is never going to change and it isn't
> actually going to be displayed anywhere, is it? UUIDs are only ugly if you
> have to look at them :)
>
> they do get displayed in the disqus recent comments like so

-----   Moo
| O |
|( )|   This is a cool dataset ;)
-----   5 mins ago
http://url/of/page


Ross.
>
>
> On 20 Apr 2012, at 13:06, Toby Dacre wrote:
>
> Hi,
>
> I'm sending this again.
>
> I think I wasn't clear enough on the reason for this request.  It is
> mainly for the disqus plugin.  Although the plugin uses a unique id for the
> disqus comments eg dataset::3233-112312-32112 so comments can follow url
> changes. However when the first comment for that id is first created disqus
> saves the url of the page (this url is setable so we can give any url we
> want at this time).  The problem is that the url is used in the recent
> comments part of disqus so that if url changes in ckan all links in the
> recent comments for that dataset will no longer work.  It may be possible
> to change this somewhere in the discus dashboard but I haven't found it
>
> the options
> a) we don't care use the current dataset url
>
> b) use the /dataset/uuid url (ugly but solves the problem)
>
> c) Sean's solution keep old urls (adds extra complexity)
>
> d) Sean's solution don't let people change urls (nasty if spelling
> mistakes in url etc)
>
> e) provide permanent urls that do redirects to the actual url
>
> What should we do?
>
> thanks
>
> Toby
>
> On 19 April 2012 10:39, Sean Hammond <sean.hammond at okfn.org> wrote:
>
>> > With both the disqus and social plugins we have an issue that when the
>> url
>> > for a dataset is changed we loose/break all shares/comment info.
>> >
>> > One option is to use the /dataset/uuid url which already works but this
>> is
>> > ugly.
>> >
>> > A second is to have some redirect url that we can use for this purpose
>> so
>> > that we have permanent urls
>> >
>> > If we where to go for the second option then we could also do our own
>> url
>> > shortening at the same time something like ckan.org/s/rfY6f which would
>> > also be useful for sharing via twitter etc
>> >
>> > Personally I quite like the url shortening redirect
>> >
>> > Thoughts?
>>
>> Initial feeling is that it's bad that people can change dataset URLs.
>> Shouldn't they be permalinks? But I can understand that they might want
>> to change it if they want to change the name of the dataset or make it
>> look nicer or something. Maybe when they change a dataset's URL, that
>> dataset should still remain visible at its old URL(s)?
>>
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20120420/360fafeb/attachment-0001.html>


More information about the ckan-dev mailing list