{"action":"created","issue":{"url":"https://api.github.com/repos/ckan/ideas-and-roadmap/issues/161","labels_url":"https://api.github.com/repos/ckan/ideas-and-roadmap/issues/161/labels{/name}","comments_url":"https://api.github.com/repos/ckan/ideas-and-roadmap/issues/161/comments","events_url":"https://api.github.com/repos/ckan/ideas-and-roadmap/issues/161/events","html_url":"https://github.com/ckan/ideas-and-roadmap/issues/161","id":118532316,"number":161,"title":"Make it easier for users to determine package id of a record","user":{"login":"ageara","id":9634036,"avatar_url":"https://avatars.githubusercontent.com/u/9634036?v=3","gravatar_id":"","url":"https://api.github.com/users/ageara","html_url":"https://github.com/ageara","followers_url":"https://api.github.com/users/ageara/followers","following_url":"https://api.github.com/users/ageara/following{/other_user}","gists_url":"https://api.github.com/users/ageara/gists{/gist_id}","starred_url":"https://api.github.com/users/ageara/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ageara/subscriptions","organizations_url":"https://api.github.com/users/ageara/orgs","repos_url":"https://api.github.com/users/ageara/repos","events_url":"https://api.github.com/users/ageara/events{/privacy}","received_events_url":"https://api.github.com/users/ageara/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-11-24T05:04:19Z","updated_at":"2015-11-25T03:56:03Z","closed_at":null,"body":"**Issue:**\r\nAs a data catalogue user, I want to easily discover the immutable, system generated Package ID \r\n*e.g. [http://catalogue.data.gov.bc.ca/dataset/42f7ca99-e7f3-40f7-93d7-f2500cccc315](http://catalogue.data.gov.bc.ca/dataset/42f7ca99-e7f3-40f7-93d7-f2500cccc315)\r\n\r\nso that I can use it to embed or bookmark a record - that will not be broken by alteration of the record's Semantic URL (SLUG)\r\n*e.g. [http://catalogue.data.gov.bc.ca/Dataset/bc-data-catalogue-content](http://catalogue.data.gov.bc.ca/Dataset/bc-data-catalogue-content)\r\n\r\n**Proposed solution:**\r\nProviding a hyperlink reference to the Package ID as a permalink in the package header.module-content.page-header to make it easier for users to find and reference the Package ID.\r\n\r\n![image](https://cloud.githubusercontent.com/assets/9634036/11358000/99d0af36-9222-11e5-9e85-776d5e93c570.png)"},"comment":{"url":"https://api.github.com/repos/ckan/ideas-and-roadmap/issues/comments/159484590","html_url":"https://github.com/ckan/ideas-and-roadmap/issues/161#issuecomment-159484590","issue_url":"https://api.github.com/repos/ckan/ideas-and-roadmap/issues/161","id":159484590,"user":{"login":"ageara","id":9634036,"avatar_url":"https://avatars.githubusercontent.com/u/9634036?v=3","gravatar_id":"","url":"https://api.github.com/users/ageara","html_url":"https://github.com/ageara","followers_url":"https://api.github.com/users/ageara/followers","following_url":"https://api.github.com/users/ageara/following{/other_user}","gists_url":"https://api.github.com/users/ageara/gists{/gist_id}","starred_url":"https://api.github.com/users/ageara/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ageara/subscriptions","organizations_url":"https://api.github.com/users/ageara/orgs","repos_url":"https://api.github.com/users/ageara/repos","events_url":"https://api.github.com/users/ageara/events{/privacy}","received_events_url":"https://api.github.com/users/ageara/received_events","type":"User","site_admin":false},"created_at":"2015-11-25T03:56:03Z","updated_at":"2015-11-25T03:56:03Z","body":"@davidread unfortunately we have had more than a few instances where datasets have changed names - most commonly because they had originally included a date in a dataset name - and have removed it as they built the dataset into a time series.  This presented issues where the SLUG was embedded in other systems - so not actually humans trafficking in gobbledygook directly ;).\r\n\r\nIs there any formal system within CKAN for managing 301s - or are people just managing these adhoc within their reverse proxies? \r\n\r\nHow do maintainers watch for SLUG changes - or is this an on request basis."}}