[ckan-discuss] CKAN 2.2 and persistence of URI for static file needing update

Mon Feb 17 14:19:03 UTC 2014

>From what I saw, the real change was between 2.2a and 2.2b.

In 2.2a, the file was stored with the following url:
http://donnees.ville.montreal.qc.ca/storage/f/*2013-12-06T18%3A52%3A46.322Z*
/electiongene-2009-posteselectifs-ancien.csv

There is a timestamp in the URL.

In 2.2b
http://localhost/dataset/
*43d6328d-e289-4553-982e-c4801dbfca0a/resource/746f65a3-c8a5-4a9a-b6ae-6e860405b56b*
/download/availabilityoffacilitiesthatofferservices.csv

The timestamp has been replaced by a concatenation of the dataset id and
the resource id.

Steph

On Mon, Feb 17, 2014 at 4:05 AM, David Raznick <david.raznick at okfn.org>wrote:

> Hello
>
> I am not sure this is the case.  In fact version 2.2 made the URLs of
> uploaded files to the filestore much more permanent. In the past any
> new uploaded data caused a new URL to be created.  Now all URLs are
> always of the form
>
> http://HOST/dataset/
> <dataset_id>/resource/<resource_id>/download/filename.ext
>
> Even if the filename of the new file you uploads name has changed you
> are able to get at it using the old filename. i.e
>
> http://HOST/dataset/
> <dataset_id>/resource/<resource_id>/download/oldfilename.ext
>
> Not only that
>
> http://HOST/dataset/<dataset_id>/resource/<resource_id>/download
>
> is always a permanent link for any resource even for ones that have
> not been uploaded as it will redirect to the correct location.
>
> So I am confused as to why this is thought to be the case.  Clear
> examples of where this is happening would be very appreciated.
>
> Thanks
>
> David
>
> On 14 February 2014 15:56, Diane Mercier <diane.mercier at gmail.com> wrote:
> > Hi,
> >
> > Our sysadmin tells us that version 2.2 of CKAN has changed the management
> > method of the URL of resources: a file in the fileStore can no longer be
> > replaced by a new one without a new URL  ... This has significant
> impacts on
> > the persistence of URIs for static files needing corrections (not
> version)
> > and, so on the reuse of updated data. In this case, the user must
> navigate
> > through the catalogue to get the right URL for each reuse! URL of static
> > files are not useful in applications.
> >
> > Do you have solutions to propose, for example, using the API or method of
> > redirection (handle) of the URL?
> >
> > I am very concerned by the persistence of URIs
> >
> > Thank you for help and suggestion, and apologize my english ;-)
> >
> > Regards,
> >
> > --
> > Dre Diane Mercier
> > Ph.D. Sciences de l'information
> >
> > Chargée de projet principale des données ouvertes
> > @MTL_DO | donnees.ville.montreal.qc.ca
> > dmercier at ville.montreal.qc.ca
> > donneesouvertes at ville.montreal.qc.ca
> > 514 872-9702
> >
> > « Pas de données ouvertes, sans logiciel libre ni formats ouverts »
> >
> >
> >
> > _______________________________________________
> > ckan-discuss mailing list
> > ckan-discuss at lists.okfn.org
> > https://lists.okfn.org/mailman/listinfo/ckan-discuss
> > Unsubscribe: https://lists.okfn.org/mailman/options/ckan-discuss
> _______________________________________________
> ckan-discuss mailing list
> ckan-discuss at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-discuss
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-discuss
>

-- 
Stéphane Guidoin
Director, Transportation
Open North
514-862-0084
http://opennorth.ca
Twitter: @opennorth / @hoedic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/pipermail/ckan-discuss/attachments/20140217/62d2b7a4/attachment.html>