Ticket #2347 (new enhancement) — at Version 9

Opened 2 years ago

Last modified 22 months ago

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 (last modified by ross) (diff)

Some additions to the related stuff functionality to make it more useful post the 1.7 release.

[\] My related things on my user page

[x] Show user created related things on the users' page with links direct to the related page of that dataset. {0.5d}

Now makes the information available, but only the count is shown until we can get Aron /Sam to take a look at this page

[x] Related stuff usage counts { 1d }

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.

[x] Un-attached related items {0.25d}

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'

[x] Dashboard + Controller (Related) {1d}

[x] Ordering at logic layer (date, views, rating, popularity of package, featured) {1d}

[x] date [x] views [x] featured

[x] 'Featured' related item with mechanism to fetch it. {0.5d}

[ ] UI within dashboard for sysadmins to check/uncheck feature status {0.5d}

[ ] 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? { 0.5d }

[ ] Implement auth changes as per doc. { 0.5d }

[ ] UI Changes

[ ] General tidy up, fix form etc

[ ] Highlight featured items py:if="related.featured"

[ ] Show either view count or popularity ${ related.view_count }

Change History

comment:1 Changed 2 years ago by ross

  • Keywords [6d] added
  • Description modified (diff)

comment:2 Changed 2 years ago by ross

[ ] Check that dataset privacy can be taken into account.

comment:3 Changed 2 years ago by ross

  • Description modified (diff)

comment:4 Changed 2 years ago by ross

  • Description modified (diff)

comment:5 Changed 2 years ago by ross

  • Description modified (diff)

comment:6 Changed 2 years ago by ross

  • Description modified (diff)

comment:7 Changed 2 years ago by ross

  • Description modified (diff)

comment:8 Changed 2 years ago by ross

  • Cc aron.carroll added
  • Description modified (diff)

Keeping track of UI changes required, and copied Aron

comment:9 Changed 2 years ago by ross

  • Description modified (diff)
Note: See TracTickets for help on using tickets.