Ticket #1583 (assigned enhancement) — at Version 6
Integrate QA into frontend - 1d
Reported by: | johnglover | Owned by: | zephod |
---|---|---|---|
Priority: | major | Milestone: | ckan-sprint-2012-02-06 |
Component: | ckan | Keywords: | qa |
Cc: | Repository: | ckan | |
Theme: | none |
Description (last modified by zephod) (diff)
Tasks:
On dataset view page, add star rating after each resource view url. Probably similar to current format label after url.Add star rating to resource view page, along with a way of displaying the reason for the rating and tips to improve. Should be unobtrusive.Fix the table at http://thedatahub.org/qa/dataset/broken_resource_links - URLs should be truncated to a fixed not-too-long length and the other fields line up (eg by using a table)~- Handle 404s by showing that 'we think this resource is 404ing'.
- Handle the absence of QA data on a resource (currently nothing is displayed. Maybe that's fine.
- Do we need to integrate the 'reason for rating' string into the UI?
Next Steps:
- Deploy CKAN and then CKANEXT-QA onto thedatahub.org to try out the code changes with real data.
Change History
comment:2 Changed 2 years ago by rgrp
- Owner changed from johnglover to zephod
- Status changed from new to assigned
comment:3 Changed 2 years ago by rgrp
- Milestone changed from ckan-v1.6 to current-ckan-sprint-2012-02-06
comment:4 Changed 2 years ago by zephod
Working on this on branch feature-1583-qa. https://github.com/okfn/ckan/tree/feature-1583-qa
Design work is done, it needs integrating with the live API. That's all in the QA extension.
Suggest all my work should be moved into the ckanext-qa extension and plugged into the API available there. Shouldnt have developed this in core after all.
Note: See
TracTickets for help on using
tickets.
I'm not sure star rating is the key thing I want to know and I also think it will be visually very confusing (I associate stars with ratings now with some automatic quality assessment + (IMO) 5 star isn't that useful). I'm much more interested in things like:
This is an area where referring back to the original user stories (if any) around QA is really useful.
I guess my feeling would be some of this should be about providing e.g. helper methods so that theme designers can incorporate things into their design with some work putting this into default CKAN theme.