Custom Query (2152 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (760 - 762 of 2152)

Ticket Resolution Summary Owner Reporter
#1594 wontfix [super] QA Improvements johnglover johnglover

Reported by johnglover, 2 years ago.

Description

Now that QA has been updated for Celery and CKAN 1.5.1, there are a number of improvements that we should probably implement.

  • Integrate QA into frontend - 1d - #1583
  • QA report improvements - 2.5d - #1584
  • QA - Check license as part of 5 star rating - #1587
  • QA - Give SPARQL endpoints a 4 star rating - #1588
  • QA - Give 5 star rating to datasets with link metadata - #1589

Main pad: http://ckan.okfnpad.org/qa

Some QA discussion (relating to Celery in particular) at http://ckan.okfnpad.org/queue

#1622 fixed Deploy QA on DGU UAT test server - 0.5d johnglover johnglover

Reported by johnglover, 2 years ago.

Description
  • Update CKAN on DGU UAT to 1.5.1
  • Deploy Celery
  • Deploy QA extension
#1651 fixed Explicit link mapper johnglover dread

Reported by dread, 2 years ago.

Description

In this commit https://github.com/okfn/ckan/commit/1772a5c John Glover set map.explicit=True in ckan/config/routing.py.

The reason this was done was to avoid links collecting parameters. e.g. if you were on page /dataset/{id}/resource/{resource_id} then by default all the links on that page generated by url_for (Routes) would include the id and resource_id parameters as well. To avoid this, you had to go through all the links and add id=None and resource_id=None to the url_for parameters.

When map.explicit was changed to True, the value of the controller, action, id and any parameters were no longer automatically carried over into the generated links for the page. So previously links within the same controller didn't need to specify the controller (for example), but now they did. So when we did this we also had to fix up links that weren't explicit:

John made the config change on 5/11/2011 which was merged to master https://github.com/okfn/ckan/commit/5a01e67 21/11/2011. The related fixes mentioned were in within the same week. This all went into release 1.5.1. The requirement

Note: See TracQuery for help on using queries.