Changes between Version 1 and Version 4 of Ticket #2873


Ignore:
Timestamp:
08/16/12 17:01:29 (21 months ago)
Author:
toby
Comment:

This is a problem with the summary data not the resource qa score it is almost certainly due to stale data.

keeping here till resolved

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2873

    • Property Owner set to toby
    • Property Status changed from new to assigned
    • Property Summary changed from ckanext-qa: Incorrect Dataset Openness Scores to ckanext-qa: dataset summary incorrect
    • Property Milestone changed from ckan-backlog to demo phase 4

  • Ticket #2873 – Description

    v1 v4  
    1 QA Extension gives wrong score for Datasets. 
    21 
    3 This was found when testing on s031, but I imagine this is more widely applicable. It was giving a 4 star score to a dataset which contained a CSV file and an HTML link. 
    42 
    5 The way that I understand it is: 
     3For example see:  http://s031.okserver.org:2375/qa/dataset/five_stars 
    64 
    7 * 3 Stars: Suitable for CSV accessible over HTTP 
     5Which has: Example dataset as a score of: 4 After examination of the dataset (  http://s031.okserver.org:2375/dataset/example-dataset ) it is made up of a CSV and an HTML file. 
    86 
    9 * 4 stars: Datasets will have resources which are either RDF files (in any format: XML, Turtle, N3, JSON-LD), or are SPARQL API Endpoints, or are HTML files (either linked or uploaded) which are embedded with RDFa/Microformats/Microdata <-- requires mime-type analysis, and if HTML file then analysis of the doctype 
    10  
    11 * 5 stars: The resources will contain fully dereference-able URIs (i.e. their URIs are accessible over HTTP) <- quite difficult to automate, but certainly possible.