Summary: | Koha should use cool URIs | ||
---|---|---|---|
Product: | Koha | Reporter: | Pablo AB <pablo.bianchi> |
Component: | Architecture, internals, and plumbing | Assignee: | Galen Charlton <gmcharlt> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | dcook, veron |
Version: | master | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Pablo AB
2017-04-10 14:29:16 UTC
I have always been bothered by the fact that I can't go to a URL like https://intranet.bywatersolutions.com/cgi-bin/koha/circ/ ...and get to the home page for that module. I agree that even better would be https://intranet.bywatersolutions.com/circ/ 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 URIs are a tough one. If you really wanted non-ephemeral URLs, you'd want to use a link resolver like Handle.net to have "permanent identifiers". If/when we move to a framework like Mojolicious which has a router to map URIs to controller actions, it'll be easier to create nicer looking URIs. I don't think it would be particularly sustainable to hack this using Apache rewrite. (In reply to Pablo AB from comment #2) > 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 I think that was the product of a conversation Magnus and I had together a long time ago. It never really took off... |