Ticket #2347 (new enhancement) — at Initial Version
Related stuff dashboard and changes
| Reported by: | ross | Owned by: | ross |
|---|---|---|---|
| Priority: | awaiting merge | Milestone: | ckan-v1.8 |
| Component: | ckan | Keywords: | [6d][r:2d] ui |
| Cc: | aron.carroll | Repository: | ckan |
| Theme: | none |
Description
Some additions to the related stuff functionality to make it more useful post the 1.7 release.
[ ] My related things on my user page
[ ] Show user created related things on the users' page with links direct to the related page of that dataset.
[ ] Related stuff usage counts
Record the number of times the link for a related item is clicked. This is likely to mean that the link fires to call CKAN and then redirects to the actual URL.
[ ] Investigate ratings for related stuff.
Record the number of times the link for a related item is clicked. This is likely to mean that the link fires to call CKAN and then redirects to the actual URL.
[ ] Un-attached related items
Allow related items to be created without being attached to datasets. This may mean that the dataset field is optional in the API.
[ ] Dashboard for related
A dashboard for related items, site-wide (not package specific) and orderable by date, views, {rating}, popularity of the dataset. Would be useful (possibly) for site-admin to mark one or more as 'featured'
[ ] Dashboard + Controller (Related)
[ ] Ordering at logic layer (date, views, rating, popularity of package, featured)
[ ] 'Featured' related item with mechanism to fetch it.
[ ] UI within dashboard for sysadmins to check/uncheck feature status
[ ] Changing auth for related.
Currently auth is based on deletion being possible by dataset owner and the related owner but it may be that a lot of the auth for related items should be configured to have more restrictive auth.
[ ] Document auth changes, allow for simple auth or this more complex auth in related. This might be on by default for publisher auth?
[ ] Implement auth changes as per doc.
