{23} Trac comments (3729 matches)

Results (3301 - 3400 of 3729)

Ticket Posixtime Author Newvalue
#1168 1325866142000000 thejimmyg Quick update... we now have: * An automated way to build the deb packages * An automated way to install them into a fresh virtual machine We don't currently run them via buildbot or have smoke tests.
#1183 1311181719000000 thejimmyg Hi John, Can you have a look at this one too please? Cheers, James
#1189 1323173227000000 thejimmyg Closing this ticket in line with ticketing policy since it is over 6 months old. If someone would like to develop an extension that uses spideroak as a back end we can look at it again.
#1192 1310135468000000 thejimmyg This is now a child ticket of #1142
#1200 1311180218000000 thejimmyg This is a duplicate of #1108. Let's have the discussion there please.
#1204 1311179980000000 thejimmyg Sorry, is this a CKAN issue or a datacatalogs.org one? If it is datacatalogs.org do you mean a catalog rather than a package? If so, can you give an example of the sort of change you've made? Marking as invalid until we get more information.
#1208 1310124599000000 thejimmyg Rufus and Friedrich are working on this at the moment so putting into the current sprint. I'm considering this as preliminary investigation to inform the wider project that David Raznick is leading on.
#1242 1323173292000000 thejimmyg This text is no longer present on the login page.
#1285 1323173125000000 thejimmyg I could write some middleware to handle this. Can we come up with a list of exceptions not to catch or should I create a base exception called "NoEmailReportTriggeredException()" which exceptions for this purpose have to be derived from or which code has to raise?
#1415 1323167941000000 thejimmyg This is all complete now. We aren't yet allowing multiple options, but we do support proper version numbers and the domain name. Other features will be implemented as different scripts for the timebeing eg ckan-setup-solr.
#1435 1323168783000000 thejimmyg I personally can't see the benefit of switching to a generic paid service when we already have a highly customised and working infrastructure based on buildbot and buildkit - we do testing in VMs as well as continuous integration. What is the advantage? Suggest wont fix?
#1462 1323172211000000 thejimmyg Let's work together to fix the packaging aspect too.
#1464 1323169763000000 thejimmyg As part of the queue upgrade we'll also fix #1064 which explains that the current queue implementation is over-engineered.
#1467 1326104869000000 thejimmyg The publisher issue seems to be resolved now, although during investigation I also found these issues: * 9 of the records don't have a published by and I wondered why * Lots of them are state=deleted (so do we really want to include these?) * We're still showing the deprecated agency field * Many of the departments are blank Pawel is not available to work on these anyway at the moment, so let's pick them up as part of the disintegration work to migrate to CKAN. Marking the main ticket as "worksforme" since it does now.
#1521 1323174618000000 thejimmyg It would be nice if the new UX also made it clearer that a user has to login, before they click the "Add a group" link which currently takes them to the login page with the message "Unauthorized to create a group".
#301 1274832112000000 tim Duplicate of #190, although that ticket has a different implementation. It prefers comments as blog comments.
#1057 1329150236000000 toby fixed in commit 3d7cbf0
#1197 1340010256000000 toby personally I'm against these for 4 reasons a) The site should be self explanatory and if it is not this is a failure of design b) a cookie would be needed to prevent these happening all the time - cookies are bad as they interfere with caching proxies. c) I find stuff like this patronising/annoying for the user d) They are a maintenance burden for ckan as we do not have a single instance Therefore I'd suggest closing this as a won't fix - I agree this is just a personal view point and therefore am not going to actually close the ticket but just record my opinion.
#1197 1340019675000000 toby Thinking horrible thoughts, there was a rumour of a ckan tour, for something like that this would be useful. Not sure where that plan is at? if there is a ticket for it maybe link to this one and close?
#1370 1334674002000000 toby We can supply the following to ShareThis * st_url Specifies URL (can be shortened URL) that you would like shared * st_title Specifies title that you would like shared * st_image Specifies link to image you would like displayed in the shared content * st_summary Specifies summary text/description you wish to share currently we just have the defaults but do we want to set these?
#1370 1334674212000000 toby config options: * social.sharethis_api_key * social.sharethis_style = horizontal | vertical | large | none * social.sharethis_sites = googleplus twitter facebook email sharethis Easy to add new sites we just need the ShareThis name and a description Currently these are all site wide maybe add options for specific templates (via the template not config)
#1370 1334675681000000 toby style & sites can now be passed by individual templates
#1370 1334838259000000 toby The url issue wants resolving when 1.7 released need to * ensure setup.py setting are complete/correct * publish to pypi * check setup instructions work
#1370 1335273643000000 toby I've talked to David and we both feel that this should not be a part of core.
#1653 1328887997000000 toby Initial implementation completed. /en/home - is English /fr/home - is French etc. /home uses site default from development.ini Requests to default will redirected to a language specific url if the browser requests an available language. h.url() and h.url_for() amended to use the new url scheme h.url_for_static() added for none language based urls (css, js) Base templates updated. IMPORTANT: pylons.url() removed from ckan.lib.base.render() as this allowed the language functionality to be ignored. Broken templates should use h.url() instead of url().
#1653 1329215488000000 toby branch feature-1653-i18n_url_rewriting in ckanext-ecportal is part of this fix
#1792 1329483249000000 toby package create update use correct schema in get_action
#1792 1332755148000000 toby closing as done all that I was asked to do as part of this ticket
#1792 1332928847000000 toby This is in the 1.6.1 as far as I'm aware. The branch was deleted after the merge into master
#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 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
#2202 1338204729000000 toby these are available through the pkg_dict
#2202 1338204801000000 toby re-reading this it's slightly different re-opening
#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
#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
#2227 1332843126000000 toby being done in other tickets
#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 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?
#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
#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 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 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
#2261 1332838253000000 toby new config option ckan.root_path = /path/from/root/with/{{LANG}}/substitution
#2261 1332840056000000 toby completed plus documentation updated
#2261 1332840112000000 toby please test logging in/out as the redirect was not testable but should be correct
#2267 1343135541000000 toby this is not important as far as phase 2 is concerned - but you can do if you want
#2289 1340887101000000 toby needs docstrings
#2298 1340285049000000 toby related to http://trac.ckan.org/ticket/2579 move sort functions to helpers
#2302 1342095074000000 toby @ross do you want to give this to aron or me?
#2302 1343636153000000 toby @shevski, please do not try to change the meaning of tickets/add features or they will just get closed as won't fix. featured datasets is nothing whatsoever to do with this ticket so adding it to the ticket just causes me to get upset / demotivated etc. please do not do this. It ruins my day. Also comments like see sams design is of no value without a url in fact it has negative value. :( I have changed the priority of this ticket to account for this but next time i'll just close it.
#2311 1334837867000000 toby most work has been completed comments can be added to templates via ${h.disqus_comments()} recent comments via ${h.disqus_recent()} basic i18n works for languages except norwegian which reverts to english needs ckan 1.7 awaiting clarification re urls changing from under us
#2355 1336731240000000 toby ckan.plugins.toolkit introduced to help control access to ckan for extensions. This should reduce breakage for extensions using this. ITemplateHelpers allows extensions to add helper functions so templates can be less reliant on Genshi filter
#2355 1338212946000000 toby Need to do documentation which is #2362 so has own ticket closing
#2362 1341314244000000 toby first part complete part2 is the auto generation merge that is for 1.9
#2362 1342085420000000 toby need to get the auto-documentation done now
#2371 1338481174000000 toby implementation trial in ckan demo branch #2375
#2371 1340038431000000 toby awaiting release and demo theme merge
#2371 1345209675000000 toby closing as part of 2375 branches
#2375 1338292898000000 toby stealing this ticket
#2375 1340710303000000 toby moving milestone
#2400 1338205947000000 toby In testing this is not replicable due to lack of info so closing
#2406 1337766385000000 toby I installed CKAN yesterday afternoon from source, using the instructions at http://docs.ckan.org/en/ckan-1.7/install-from-source.html Most things worked pretty smoothly and, luckily, when they didn't I was lucky enough to have David Raznick on hand to help sort them out. As a result I've made the following notes on where the doc could be improved. For some ghastly reason I am running Linux Mint, which is some variant of Ubuntu. It's not 10.04, so no package, hence the source install. Sec 2: Not wanting a mysterious file called 'pyenv' in my home directory, I created a directory ~/ckan and typed 'virtualenv pyenv' from there. Everything worked fine. But if I had needed the 'tip' it would have been a little confusing. It would also be worth reminding the user that the dubious package is one they've supposedly just installed, so if that went OK, they won't need to worry about this. The tip also isn't clear about under what circumstances I'd need to do the 'easy_install pip' - I didn't need to (is that also only when python-virtualenv is missing?) Sec 4: This worked, but the example command for installing a particular version is confusing. It says it is for 1.5.1, but replacing '1.5.1' with '1.7' fails because there is a rogue 'c' in the command. Probably it would be better to use the latest version (1.7) as the example anyway. Or is there a way of asking for the latest released version? I understand this checks out the whole Git repository with all history - I can't imagine why I'd need to do this to build a particular version. But David assures me it's very sensible. Sec 6: This worked, but it wasn't very clear what the purpose of the 'List existing databases' step was. Sec 8: So now I had to try to get Solr working using the instructions at http://docs.ckan.org/en/ckan-1.7/solr-setup.html This didn't work at all, in ways I can't now remember, to do with Java. In the end David suggested using Tomcat rather than Jetty (don't ask me what these do, but they have something to do with getting Solr to work ...) and this turned out to be much more straightforward to install and get working, with two caveats (below). David suggested maybe Tomcat should be the default suggested in this doc. - One problem with Jetty was to do with using the wrong version of Java, which seemed to be fixed using "sudo update-alternatives --config java". It didn't fix Jetty - not sure if it would also have been needed with Tomcat. - Soft linking the schema file didn't work - it seems Tomcat doesn't like soft links. We made a copy. After this everything worked, and I now have my very own CKAN. Hurrah! Mark
#2406 1337766413000000 toby The 'post-installation setup' instructions at http://docs.ckan.org/en/ckan-1.7/post-installation.html claim to be for either package or source installations, but only work as stated if you have done a package installation. E.g. after a source install, "paster --plugin=ckan user add admin --config=/etc/ckan/std/std.ini" doesn't work (the ini file is somewhere completely different), but just typing "paster user add admin" from the ckan directory is fine. The instructions should also mention that the virtual environment should be activated. Mark
#2411 1338210872000000 toby This is a long term goal
#2416 1338464207000000 toby commit 37622d5 does this but probably in the wrong place but works for now. Need to revisit at some point.
#2416 1340710252000000 toby moving to phase 2 as not causing problems but still needs proper fix
#2417 1337864155000000 toby fixed in demo-theme branch
#2418 1337875172000000 toby all facets now shown and selected have <li class="active"> @aron styling of active facets with long names breaks. we could make the names shorter in snippet/facet_list.html via truncate or make the selected taggy thing wider
#2419 1337863024000000 toby @aron the reason for this is that controller/package.py renders the form `package/new_package_form.html` as part of it's work and then makes this available a `c.form` to the template. I'm not sure I like this as an approach but it is how it is currently done. If you split your form into a new template `package/new_package_form.html` then you get all the errors etc. I think for now we should do this and then look at if doing it all in one template pass might be more sensible. reassign to me if you want me to do this else I'll leave it with you
#2420 1337950422000000 toby merged into master
#2433 1337960203000000 toby the affected actions =============== package_list package_relationship_create revision_show group_list package_update_validate It would be nice to get this fixed and I'm loathed to suggest adding a version 4 hack. If we make this change it will break things for existing users. This behaviour has existed since the action api was added as far as I'm aware So should we a) leave it forever and document b) break things and fix it - when 1.7.1 or 1.8?
#2433 1338397268000000 toby after discussion it has been agreed to keep the existing behaviour and improve documentation as it is likely to break existing applications etc
#2440 1339423966000000 toby @aron, tags what functionality do we want for this? I can just reuse the facet_list snippet but then we have all sorts of interactivity. Do we want this more a static list of tags (linked to somewhere but no add remove stuff)? seems more sensible I think featured datasets I've no idea I'll try to discover
#2440 1339430956000000 toby you may want to look at your css as the dataset is generated by the package_list snippet I've made all packages popular for now
#2440 1339498655000000 toby dataset descriptions is a data issue but I'll keep this open for now. We can probably do an exclude if needed.
#2440 1339581622000000 toby I am changing this to assigned not accepted as this makes trac easier to use
#2440 1340373461000000 toby i'm closing we can make tickets for specific issues
#2441 1338291362000000 toby @aron, this is now in a snippet (jinja2 allows the selected="selected" more easily) needs some work still eg translation stuff and also maybe completely rewrite the snippet at some point. Anyhow the functionality is there. I added the button for no javascript working. I'm assigning to you for beautification etc on live demo http://s031.okserver.org:2375/dataset?q=&sort=title_string+asc
#2441 1338384362000000 toby popular badges on package list - may make them optional/configurable at some point but good enough for now. see http://trac.ckan.org/ticket/2442 for details With the `order button` this is for none javascript users i'm not sure the magnifying glass looks like the thing to press to reorder the results. I'd hide it when javascript enabled. Do what you will @aron I'm assigning this to you close or reassign to me if you need extras adding
#2442 1338305764000000 toby make readable * Group module needs to display group/publisher title, logo and description if dataset has an associated group. * Popular icon only needs to be displayed if dataset is popular. (say if it has 10+ views for the moment) * Popular icon needs localised text passed in to snippet (See TODO comment above helper https://github.com/okfn/ckan/blob/feature-2375-demo-theme/ckan/templates/package/read.html#L46) * Related module needs to show most recent item or fallback content.
#2442 1338379591000000 toby popular localised need to get live tracking data and fixup (in progress) groups now shown including multiple with link to group page related items I'd like some data for this I'll see if I can add some
#2442 1338381909000000 toby now has actual tracking data to get data install ckanext-googleanalytics from source in analytics package dir run `paster loadanalytics internal 2012-01-01 -c ../ckan/development.ini` you may need to change .ini file name then in ckan dir `paster search-index rebuild -r -c dev.ini` It needs a refactor to make it easier to use
Note: See TracReports for help on using and creating reports.