Bug 18410 - Koha should use cool URIs
Summary: Koha should use cool URIs
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Galen Charlton
QA Contact: Testopia
Depends on:
Reported: 2017-04-10 14:29 UTC by Pablo AB
Modified: 2017-05-29 05:45 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Who signed the patch off:
Text to go in the release notes:
Version(s) released in:


Note You need to log in before you can comment on or make changes to this bug.
Description Pablo AB 2017-04-10 14:29:16 UTC
Right now Koha use a very volatile URI scheme. If we seek having not ephemeral URIs they should be completely different. Take a look to this article from 1998 of a guy called Tim Berners-Lee:

"Cool URIs don't change" https://www.w3.org/Provider/Style/URI

A normal Koha URI looks like this: 


This URI is doomed to die in the short term, is not designed thinking in long-term. We have a lot of information about the tools and technical things used to put it there, like "cgi-bin", "koha" and "pl".

Is not even consistent about using always en_US (american English): "/cgi-bin/koha/cataloguing/addbooks.pl" (cataloguing !=  cataloging).

As the article say we shouldn't forget about domain name. We could encourage the use of more permanent words like "catalog" for the host part of the FQDN.

PS: This may be related to the robust RESTful URI.
Comment 1 Owen Leonard 2017-04-10 15:47:15 UTC
I have always been bothered by the fact that I can't go to a URL like


...and get to the home page for that module. I agree that even better would be 

Comment 2 Pablo AB 2017-05-29 02:07:13 UTC
This could be done with some URI rewrite (Apache mod_rewrite) directives. Someone give an example on wiki: https://wiki.koha-community.org/wiki/Linked_Data_RFC#Canonical_URL.2FURI_for_records