Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the doc about ckan.featured_groups #999

Closed
formwandler opened this issue Jun 13, 2013 · 5 comments
Closed

Improve the doc about ckan.featured_groups #999

formwandler opened this issue Jun 13, 2013 · 5 comments
Assignees
Milestone

Comments

@formwandler
Copy link

The parameter ckan.featured_groups should be better documented.

My history: I have configured the "title" of the group, e.g. "Group1" or "MySpecialGroup", which did not work. I had to change it to the URL names, which in my case could be e.g. "group1" (case sensitive!) and "my-special" (URL name customized/shortened).

*You need to use the URL name
*The values are case sensitive

@seanh
Copy link
Contributor

seanh commented Jun 13, 2013

I'm not sure this issues is specific to ckan.featured_groups. Throughout CKAN, datasets, groups, organizations, users, etc. have both unique names and "titles" that are display versions of the names. In many places in the CKAN config file and in the API etc. you have to use the names or IDs but not the titles.

@formwandler
Copy link
Author

About title vs. names: But in the groups section of the GUI there is just a "Title:" field and the "URL:" field. No "name" or "id" like mentioned in the docs. So, this should be more precise (e.g. the name is part of the URL). But where is the id (maybe from the database?)?

@tobes
Copy link
Contributor

tobes commented Jun 14, 2013

@formwandler in ckan we can identify a dataset via it's name or id only as these are unique. The title could be the same across many datasets (though this is unlikely/unhelpful)

Maybe the id/name should be more visible in the front-end

@seanh
Copy link
Contributor

seanh commented Jun 14, 2013

Yeah, I'm just wondering where this should go in the docs. See the current table of contents here: http://docs.ckan.org/en/latest/. Maybe we should insert a Domain Model page somewhere in the docs, that goes over the main objects in CKAN (package, resource, group, organization, user...) and explains what they are and what fields they have?

@ghost ghost assigned seanh Sep 9, 2013
@seanh
Copy link
Contributor

seanh commented Apr 7, 2014

Closing due to inactivity. I would like to see the docs improvements mentioned, though

@seanh seanh closed this as completed Apr 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants