{23} Trac comments (3729 matches)

Results (2901 - 3000 of 3729)

Ticket Posixtime Author Newvalue
#1802 1329490081000000 dread I've achieved CKAN running with paster and without SOLR (using simple_search). Running locally on an old XP machine, performance seems fine - no noticeable issues. I installed most things into a pyenv using pip. pyutilib, psycopg2 and lxml were slightly problematic, but I have workarounds. I had problems pip and svn and the Cygwin window, so reverted to DOS prompt. I still had the Cygwin tools installed though, so next step is to try it without these at all - they are a big overhead.
#1802 1329734716000000 dread Spent so far 1.75d
#1802 1329830097000000 dread * Refined install without using Cygwin - this seems a little easier. * Added example Apache & modwsgi deployment. * Documented extensively at: http://wiki.ckan.org/CKAN_install_on_Windows * Have not tried SOLR on Windows - I'm not convinced this is high priority, and normal install should be fine as it is so separate from CKAN. Spent another 0.5d. Total spent 2.25d
#1804 1329491156000000 toby This should be fixed in branch feature-1653-i18n_url_rewriting as we use different logic. However it may affect other return_to calls used elsewhere like adding a new package.
#1804 1330000705000000 dread I'll fix this on release-v1.6 and then reassign to Toby to fix on feature-1653-i18n_url_rewriting too if the same issue crops up there.
#1804 1330037202000000 dread Fixed this on release-v1.6 in cset 557e72330db7. Spent 0.5h. Reassigning for Toby to look at branch feature-1653-i18n_url_rewriting
#1804 1330347185000000 toby This has been fixed in master for a while and was only a 1.6 issue
#1805 1329760795000000 toby this is fixed in branch feature-1653-i18n_url_rewriting
#1806 1330942356000000 toby version one completed
#1806 1331295310000000 toby closing as initial work has been done if we need to amend then create a new ticket
#1807 1330809641000000 seanh Implemented the recently-changed-datasets activity stream on branch feature-1807-recently-changed-datasets in CKAN and merged it into master (but the default templates don't make use of it). Added the recently-changed-datasets activity stream to the front page template on branch master in ckanext-ecportal.
#1809 1330528828000000 johnglover Caught exceptions in QA instead, error message stored as openness_score_reason
#1810 1329918479000000 johnglover Deferred for now, moving to backlog.
#1810 1335874745000000 johnglover Not using eurovoc tags.
#1811 1329918517000000 johnglover Deferred for now, moving to backlog
#1811 1335874765000000 johnglover Not using eurovoc tags.
#1812 1335874864000000 johnglover Ross has fixed this via group authentication.
#1816 1330863079000000 rgrp As per detailed comments in http://wiki.ckan.org/Proposals#Apps_in_CKAN I think Apps is a confusing name. What we are talking about here is the "Related Stuff" item mentioned in that ticket. Rather than update ckanext-apps I suggest we do a rewrite. I've created a detailed super ticket at #2204 and assigned to you Adria for review and thoughts. (While I understand #2204 may involve more work which we maybe cannot do before relaunch I'd still recommend starting on that rather than spending time upgrading this extension -- if we have to disable it for relaunch I don't think that is a big deal ...)
#1816 1331302835000000 amercader +1 to a new, more flexible extension. But in the meantime I've just spent a couple of hours making it work with latest CKAN, which was easier than expected, so we can deploy it with the new version of PDEU.
#1819 1332163324000000 kindly Currently using package_show_rest. Should be moved to just use package_show but that is another ticket.
#1828 1330525412000000 rgrp Fixed in https://github.com/okfn/ckan/commit/e6da48d9337575a83bc6a30896e68d1081b43847
#1829 1330001828000000 dread This was due to https://github.com/okfn/ckan/commit/f07bfdb9#diff-1 - string "Language has been set to: English" shouldn't have been translated. I've put in a patch to make the code intentions clearer and added a test: [release-v1.6 07d3a02]. This only affected the 1.6 beta, and is fixed for the release.
#1830 1330089912000000 dread Now if you set openid_enabled to false, you are not given the option in user settings to associate your account with openid. Cset: [master b295bde] I looked at removing the openid middleware, but we use it for logging out users, whether they logged in or not - it looks like friendly form plugin is not as good as the openid one in this respect! We could hack the logout function into the friendly form to sort this out, but not sure the effort is worth it at the moment.
#1831 1330956631000000 ross Already have a branch for this.
#1831 1331549284000000 ross Email is not currently 'unique' in the user model. Find out if this is intentional or not.
#1831 1331655458000000 ross Decided to delay this until later but code is in feature-1831-login-by-email
#2198 1339771453000000 kindly Already in the docs.
#2201 1330765400000000 rgrp Duplicate of #1171.
#2202 1338204729000000 toby these are available through the pkg_dict
#2202 1338204801000000 toby re-reading this it's slightly different re-opening
#2203 1348568961000000 dominik There is work on this in the dataviewer-iframe branch.
#2204 1332341044000000 toby needs discussion - planned for 23-3-2012
#2204 1332341080000000 toby http://ckan.okfnpad.org/feature-2204-related-stuff
#2204 1332843232000000 toby still awaiting discussion
#2204 1334077936000000 rgrp Important comment: not sure how much we have thought through using this for storing queries / views / visualizations coming from our data viewer. In particular, wonder if this necessitates some kind of support for arbitrary json data ... Also (@icmurray): does this interact with our desire to do embedding?
#2204 1334218735000000 ross I'd be happier adding this to another ticket rather than moving the target for this ticket half way through so have created #2284 Should only be a short ticket in the next sprint.
#2204 1335287636000000 aron.carroll Making some notes of front-end changes that I think need to be implemented sooooon. {{{ Implement better truncation (the expanded text should pop out on hover rather than expand the entire row) Show the type of related item (an icon would be good here) Test in IE Make the form work without JavaScript by accepting x-www-form-urlencoded. Add classes to first item in a row to clear the row (currently uses :nth-child CSS) Touch gestures and re-ordering (David's request) }}}
#2204 1335795665000000 ross Giving this ticket to Aron to fix the front end
#2204 1337582843000000 rgrp Surely this ticket was closed 3w ago? @Ross: can you close ...
#2204 1337594723000000 ross Was waiting for documentation, can close now.
#2206 1331046486000000 johnglover Close enough for now. Still have to restyle language drop-down to match template, but will fix when updating the list of languages. Also still to decide on menu styles/locations (for CKAN login and main menu, and ODP main menu).
#2208 1332251880000000 seanh I've attached a ckan.pot file. To make it, I edited setup.py in CKAN core like this: https://gist.github.com/2135849 and then ran python setup.py extract_messages. (And I had ckanext-ecportal installed at ~/pyenv/src/ckanext-ecportal.) I guess I may need to run this again when the ckanext-ecportal source is finalised, so leaving this ticket open for now.
#2209 1331547639000000 ross Option 4 is the most appealing at this point, although you probably should look at #2209
#2209 1331547674000000 ross Previous comment should read: Option 4 is the most appealing at this point, although you probably should look at #1649
#2209 1331551170000000 ross Current thinking is that option 4 is a default (as per ckanext-rdf) rdf output that is generated not in code (as currently) but using a genshi xml template to read the package into an RDF format (as if it were HTML). This would then be overrideable so that for ecportal where the format of the RDF is different (change of vocabs etc) we can just point the config to a new template. Pros: Easy to implement Easy to use Not hard-coded as currently Fast execution Cons: Requires knowledge of required RDF output if default is not useful RDF and not any of the other formats yet. Only works with package/resource/tags unless more work is done
#2209 1331551393000000 ross Can't edit comments .. so Current thinking is that option 4 is a default (as per ckanext-rdf) rdf output that is generated not in code (as currently) but using a genshi xml template to read the package into an RDF format (as if it were HTML). This would then be overrideable so that for ecportal where the format of the RDF is different (change of vocabs etc) we can just point the config to a new template. Pros: Easy to implement Easy to use Not hard-coded as currently Fast execution Cons: Requires knowledge of required RDF output if default is not useful RDF and not any of the other formats yet. Only works with package/resource/tags unless more work is done
#2210 1331549350000000 ross This is now done through the logic layer member_create/member_list/member_delete
#2212 1331719868000000 johnglover Added as a new paster command in ckanext-ecportal (run 'paster ecportal' for a list of commands and arguments).
#2212 1331720191000000 johnglover Deployed on test server, where it imported 4087 datasets. A small number of datasets were not created as they failed CKAN validation - most of which had strange values such as 9999 and 0 for date fields (some also didn't have unique names).
#2220 1331291241000000 toby issues: 1) want to cache static files long term - need to add a ?ver=xxx to allow changes - this will need a change to all templates etc - could be seen as a good thing 2) we can only purge specific pages not whole cache so we need to know all the urls which want to be invalidated - including language variants 3) urls should be consistent so we should use id not name for datasets etc 4) for now we can just use short expiry times as this prevents some of these problems
#2220 1332950550000000 toby Implementation of this has been carried out at the page level. ckan.page_cache_enabled is config option to enable it requires redis need to document it somewhere
#2221 1331561095000000 ross Fixed in https://github.com/okfn/ckan/compare/1eeda11...ad2358a
#2223 1331558791000000 rgrp Have introduced boostrap js and css on merge of #1797 https://github.com/okfn/ckan/commit/476a5bd32a3fac5d2dd85614f5d86c79f4ff6547 However need to remove blueprint and make sure we keep our original theme.
#2223 1332246030000000 zephod I have been working overtime to try and get this change straightened out as it's suddenly on the critical path for something. Have a look here: https://github.com/okfn/ckan/tree/feature-2223-bootstrap It's 80% of the way there; some form CSS needs overriding because Bootstrap tends to make things very large so they spill over. But on the whole the markup is in a steady state, which is what we need.
#2223 1332842692000000 zephod Merged into master here: https://github.com/okfn/ckan/commit/0bf4b33955df3806785f9b42a55acaeb45596e25
#2224 1332475944000000 rgrp Autocomplete based on bootstrap looks pretty non-trivial ...
#2224 1338205358000000 ross Being done by Aron
#2225 1343220502000000 aron.carroll There is a jshint.json config file that all JS in the new base theme conforms to.
#2226 1332159640000000 seanh These deployment docs seem worth moving into sphinx as well: http://wiki.ckan.org/Deployment
#2226 1332475468000000 rgrp All done (as of Tuesday in fact!). No doubt further work to do but that's a new ticket!
#2227 1332843126000000 toby being done in other tickets
#2232 1332331660000000 amercader Fixed in 6b4c6c9 This was due to some characters not being supported by XML. We now strip them before indexing.
#2234 1337237687000000 rgrp This looks interesting but is this a priority :-) (also no estimate as yet :-) )
#2234 1337239588000000 ross Yes, definitely need a replacement for wordpresser and sooner rather than later. Doing some experimental noodling to work out an estimate.
#2236 1332153688000000 rgrp Done. See https://github.com/okfn/ckan/commit/0d970d3a0e523a1695830e8c8c28c0ba10a8d8b9
#2238 1343392681000000 seanh Ticket #2771 encompasses this and related changes. Vocabs probably won't be deployed to test.ckan.net but a working example extension using vocabs will be added to core instead. Closing this ticket as a dup
#2239 1334581838000000 ross Changes to schema/rdf output
#2240 1332408769000000 ross Distributed to ckan-coord
#2242 1333375436000000 seanh Conclusion: jenkins should work, may need some jenkins plugin magic to get it to show what branch each build was run on.
#2250 1332680690000000 rgrp Is this now how we are doing it? I thought we were integrating with RDF store (so it was more about sorting out the data viewer / recline stuff)?
#2251 1332331650000000 rgrp Big +1: everyone wants to know page views. Would like detail of how this goes into interface. Downloads already being tracked. Also isn't this just an extension to ckanext-googleanalytics.
#2251 1332332390000000 toby not really part of ckanext-ga as we need to sit first in the middleware for speed reasons. I'm looking at recording the details and will do a summary page like ga extension. As far as other uses like showing popular resources etc then we need to decide where the data will live - on the resource or separate. Downloads tracked? where is this done in the code/data stored
#2251 1332340874000000 toby notes from meeting 21-3-2012 US1 As a Site Admin / Visitor (?) I want to see how often a page has been viewed (every page) and how often resources have been downloaded. US1a Next to a resource or a dataset see how often it has been downloaded / viewed US1b I want to see datasets or resources ranked by most downloaded or viewed US1c See a trend graph for a dataset (and resources) Adminstrative Dashboard (?) * I want to see the traffic breakdown by country to my site ... * Ditto for browser type, language, etc etc * I want to see it graphed over time ... == Implementation Details == 1. How do we store this data in CKAN? 2. How do we track (and store)? 3. How do we display * Config option ckan.status.enabled = False (by default) === Storing Data === How does ckanext-googleanalytics do this? Current table: package_id | count_recent | count_total Move to a new stats_summary table id | item_id | object_type | stats_type (total, month_yyyy_mm, ...) | value Do we store this data into the search (solr) so we can search by it? === Displaying Data === * Helper functions / dictize: * Helper function: h.stats_get(object_type, id, stats_type) * h.stats_top_ranked(object_type, number) -> returns object_dicts or just labels or ... * Change to dictize * Location in the default theme (do we show for example in search results too!) * Support for ranking by most popular in search? === Tracking Data === * Our own solution (just write to site_tracking) * Google analytics (plus extension for retrieving data) <- would need a refactor * Piwiki ==== Own Solution ==== site_tracking table id | url | timestamp | action (page_view, resource_download) | * Make javascript to make request to ckan to store clicks and page views. * Add middleware so these requests do not go through pylons and just store data quickly.
#2251 1332340947000000 toby TODO look at 1. How do we store this data in CKAN? 3. How do we display * Config option ckan.status.enabled = False (by default)
#2251 1332524123000000 rgrp Update description in great detail.
#2251 1332776926000000 toby we want resource show downloaded/viewed on resources show on the dataset total/recent
#2251 1333535572000000 toby we have various options on tracking unique users seems the sane approach. * unique daily view - needed for nice graphing * unique total views * total unique daily views - higher numbers and feels more right - easier to calculate if original data is lost/or archived for now will collect all and then decide which to use for display as gives us flexibility if needed display ------- why is group listing of datasets inconsistent with main search (TDH at least)? should we make these consistent? group listing allows downloading of resource without tracking (this should be fixed) if we make listings uniform do we want the download links or not? I don't like the term download when it is just a link (maybe that's just me - what would be better?)
#2251 1333644538000000 toby most work completed: outstanding issues * add a prune tracking_raw data to cli * add indexes to tracking_raw * add summary page for new data format * add api counter 1) do we record the url or action etc (action seems more sensible) 2) add in __call__ or in action?
#2251 1334074772000000 toby api counter moved to ticket #2282 as needs better specification
#2251 1334144999000000 toby For meeting today with Adria * How to add tracking to solr index. Can the data live in tracking_summary? Do we need any extra indexes on table to help indexing? * How will we add order by popularity to search? * Can we add resources too? * Will search be best way to find most popular packages/resources or should we get that pages data from tracking_summary?
#2252 1333108787000000 amercader There is a new ticket for the same schema as forms issue: #2268 The exception was fixed on [https://github.com/okfn/ckanext-inspire/commit/0dff1f6 0dff1f6]
#2252 1333374836000000 amercader This needs more work on ckanext-dgu and testing.
#2252 1334567495000000 amercader Fixed on 0dff1f6c2e
#2253 1340038490000000 toby closing as nothing has ever happened with this ticket
#2254 1332343198000000 toby What do we want to be able to do? what do we use the stream stuff for at the moment? la la la
#2254 1332950678000000 toby plan of attack a) get removal of TDH from core - this will give a better idea of the issues involved b) have a think
#2254 1338210316000000 toby closing. we have fanstatic integration in ckan.demo work tdh is it's own extension h.snippet is in 1.7 ITemplateHelpers in 1.7 This allows most of the issues resolved. Full removal of the IGenshiStream filter still neads some form of in template hooks but this is being looked at as a possiblity in ckan demo and can be considered out of scope for this ticket closing
#2255 1332752936000000 rgrp I would say Public is default for Organization with Private being an option (or do we make this a config option?). What about ownership by users? > New datasets can be created from the organization form, in which case the organization will be set in the dataset form dropdown (with privacy set to private - see below) Does this mean like the setup on groups on the datahub (i.e. forward to new dataset but with some things hard-coded, organization/group?)? Or does it mean actual new dataset form on organization page.
#2255 1332772340000000 ross > What about ownership by users? Good question. WIll add to description. > > New datasets can be created from the organization form, in which case the organization will be set in the dataset form dropdown (with privacy set to private - see below) > Does this mean like the setup on groups on the datahub (i.e. forward to new dataset but with some things hard-coded, organization/group?)? Or does it mean actual new dataset form on organization page. The former, although currently we will have a slightly different form in the organizations extension, until such a time as we're ready to replace the existing one. Tried merging the two forms but it ended up with such a mess of logic that it was unmanageable.
#2255 1332934041000000 ross Changed description based on docs of stuff to verify.
#2255 1334582784000000 ross Review + restrict resource access (when private)
#2256 1333620795000000 toby I'd like to remove all 'custom' icons and just use bootstrap ones - is this reasonable? they are added in different ways but h.icon() could be easily adapted for this. minimal .sj .css files
#2256 1333720237000000 rgrp Not sure what ticket means (remove TDH from core?). Also agree that we should glyphicons from bootstrap where possible going forward - though that would seem to fit more naturally with #2224 (Simplify javascript and css dependencies and add minified version) and have little to do with TDH versus core :-)
#2256 1334051526000000 toby @Rufus, The idea of this ticket is to separate TDH into an extension rather than it being incorporated into core. This should help TDH by making it possible to push fixes without needing to do a new release of core. It should also help make core more stable and as slim line as possible. New features can be tested in TDH and then if they have a wider appeal they can be merged into core. There is a strong desire for this within the dev team.
#2256 1334051733000000 rgrp @toby: indeed and I'm strongly in favour of the basic idea too (and largely a dev question so up to you guys though feature / functionality implications would need to be talked through). My point was that custom icon stuff was #2224 :-)
#2256 1334052087000000 toby @Rufus, Thanks, I think there is overlap and I'm happy to leave that bit of work to you (or future ticket owner) I was just adding some brief notes to this ticket on some of the outcomes I'd like to see and hence why I'd be happy to simplify the icons.
#2256 1336046098000000 toby I'm closing this ticket now ckanext-datahub exists and is live - the other work is included in other tickets
#2257 1332950416000000 toby pushed first round of changes into master
#2257 1336731023000000 toby ckan.restrict_template_vars defaults to true for 1.8 release
#2260 1333373978000000 johnglover Still some work to do on this, template needs to be finalised.
Note: See TracReports for help on using and creating reports.