{23} Trac comments (3729 matches)

Results (2901 - 3000 of 3729)

← 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 →
Ticket Posixtime Author Newvalue
#256 1290463475000000 dread This is a test
#1091 1303746408000000 rgrp This is a well known issue (see some discussoin in #142). There is nothing directly we can do about it (this is what google gives us) but we could make usernames editable (this has been discussed but not ticketed I believe). Given our general "downer" on openids I'm not sure this is a big priority.
#829 1303838115000000 rgrp This is a wontfix for the present.
#2331 1337782689000000 kindly This is a wontfix. I think terms should be ored by default. All modern search engines work like this. If there is an issue due to relevancy (i.e if you type mulitple words and your result not coming near the top) then we should use this examples so we can tweak the results.
#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.
#1735 1328531105000000 zephod This is an edge case, and there's no simple fix -- you can't detect *why* the tags box has lost focus -- so I think let's not waste time inventing something complicated.
#954 1320142744000000 kindly This is basically the complete now with documentation. The child tickets no longer seem to fit and are not essential for completion.
#1447 1340726283000000 nils.toedtmann This is becoming painful for the sysadmins. Please fix.
#402 1281373707000000 pudo This is beginning to go somewhere: * http://bitbucket.org/pudo/ckanextarchive
#2863 1345122876000000 ross This is changeable in config. The default permissions are specified in there I believe.
#480 1300281551000000 thejimmyg This is complete (albeit with a different architecture).
#1116 1304358664000000 dread This is complete in branch defect-1116-boolean-search-options for release-1.3.5
#1112 1304358643000000 dread This is complete in the branch feature-1112-allow-search-all for release 1.3.5
#43 1214244140000000 rgrp This is currently low priority and should only happen after move to vdm 0.2 (sqlalchemy etc).
#1563 1324314806000000 rgrp This is done and invalid to add this again.
#353 1280756379000000 pudo This is done as of cset:8 (of ckanext!)
#184 1266837414000000 dread This is done in cset:d2026bcf43f5 cset:ac7cf572cbf9 cset:51c6de2dc390 cset:58c660932fcf cset:dd9761591ffb
#164 1271251422000000 rgrp This is done in semantic.ckan.net. Docs at http://wiki.okfn.org/ckan/doc/rdf/
#427 1299164063000000 thejimmyg This is done in the latest release to test.
#806 1290071159000000 dread This is done now I think? Please list changesets, time taken vs estimate and close ticket.
#1252 1317315135000000 dread This is done now?
#1477 1328016209000000 kindly This is done pending new superticket publihser_profile. (#1669)
#887 1300196600000000 thejimmyg This is done. See https://bitbucket.org/okfn/ckanext-harvest At the moment we are not adding migrations to remove the harvesting tables. We are designing a harvesting refactor and will write migrations once the refactor is complete so that instances that use harvesting get upgraded, and those that don't get their harvesting tables removed. Also, see this #1030 for the moving harvesting out of the REST API.
#695 1287677169000000 ollyc This is down to blinker not persisting the signal objects. Although the docs claim: "Every call to signal('name') returns the same signal object, allowing unconnected parts of code (different modules, plugins, anything) to all use the same signal without requiring any code sharing or special imports" This isn't true unless you maintain a reference to the signal object. To demonstrate this: {{{ >>> import gc >>> from blinker import signal >>> signal_id = id(signal('Package')) >>> gc.collect() 0 >>> id(signal('Package')) == signal_id False }}} The synchronous notifications code connects to signals without storing the signal objects, which are subsequently garbage collected and hence never fire. The async notifications stores references to all signals as a class attribute, so this problem is not seen when async notifications are enabled.
#109 1291829457000000 thejimmyg This is effectively implemented by the util API; http://knowledgeforge.net/ckan/hg/file/tip/doc/api/version2.rst John has a separate proposal to move the util API into the REST API but that is a different discussion. Here's how you can now search on tags: /api/2/util/tag/autocomplete?incomplete=ru
#1012 1300352334000000 kindly This is entirely not trivial at the moment. Hopefully after the dictization it will become more so. Simply putting in the package revision object in place of the package does not work. It will obviously work for changes to the package object itself. However, there are no mappers on that object for getting out the related package_tags, resources and extras at that revision. You will have to construct a fake pkg object with some messy and painful queries using dates.
#1729 1328537269000000 johnglover This is essentially a duplicate of #1720. We do not really need helper functions for this (as it's trivial to get the default schema and add 1 extra key), but I have added a converter for tag string (with vocab) to tag and vice versa.
#1496 1326736298000000 seanh This is finished, but I think that before closing this ticket a little more thought needs to go into what the activity streams and the user page should look like, where on the page they should go, what else should go on the page, etc. Also maybe add a simple test that the activity stream is being rendered into the page.
#1633 1326736502000000 seanh This is finished, see the activity streams branch: https://github.com/okfn/ckan/tree/feature-1515-activity-streams but I think that before closing this ticket a little more thought needs to go into what the activity streams and the dataset page should look like, where on the page they should go, what else should go on the page, etc. Also maybe add a simple test that the activity stream is being rendered into the page.
#1632 1326736455000000 seanh This is finished, see the activity streams branch: https://github.com/okfn/ckan/tree/feature-1515-activity-streams but I think that before closing this ticket a little more thought needs to go into what the activity streams and the group page should look like, where on the page they should go, what else should go on the page, etc. Also maybe add a simple test that the activity stream is being rendered into the page.
#672 1291715338000000 pudo This is fixed for Solr now, plus a decision not to support postgres facets has been made.
#925 1323168588000000 thejimmyg This is fixed in CKAN 1.5
#1374 1319648726000000 dread This is fixed in branch defect-1418-i18n for release 1.5
#2937 1348157780000000 seanh This is fixed on master (commit e97b5c70e9325a1095778fef8e0d27c84e881b30) needs to be cherry-picked into 1.8
#930 1296062391000000 wwaites This is for HMG to prove to them that requests are being serviced in a timely manner * move this functionality to a plugin * make it use rrdtool instead of lots of itty bitty files
#1127 1305128000000000 thejimmyg This is great idea and it has taken on well. +1 from me. We can update/create new CREP policies as needed.
#404 1294415965000000 rgrp This is in datapkg, not a duplicate. Partly done in fact but not complete (Indexes are now pluggable).
#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
#2409 1337688965000000 ross This is in the Package controller and may be related to upcoming ticket on removal of autoneg.
#274 1279890237000000 pudo This is included in the Solr indexing engine and will become available as Solr is adopted.
#2559 1340617445000000 aron.carroll This is looking good. A couple of things to do. 1. Added resources should be displayed in the sidebar. See https://github.com/okfn/ckan/blob/feature-2375-demo-theme/ckan/templates/package/pages/form_page.html#L36 2. Clicking "previous" needs to take you back to the add dataset action not the edit dataset action. 3. Clicking "previous" should take you back to stage one of the add dataset form but stage two should be active (green). 4. Clicking "previous" should take you back to stage one of the add dataset form then clicking next should take you to the last resource you were editing.
#1236 1311699843000000 dread This is merged to default (for rel 1.2.5) but isn't brilliant yet because of bug #1238.
#1379 1319306665000000 rgrp This is minor but a real bug (seen now in several datasets). As easy to fix suggest bumping and trying to get into v1.5 (?).
#691 1294412765000000 thejimmyg This is more a long term idea, taking ownership for the timebeing but happy for someone else to take this on.
#165 1311181391000000 thejimmyg This is more than 6 months old so closing.
#460 1311176868000000 thejimmyg This is most likely fixed in the new logic layer refactor but is more than 6 months old anyway so closing in line with our new ticketing policy.
#1469 1329760150000000 amercader This is mostly done (current form is http://i.imgur.com/zmfc5.png). Still some tests missing and a little bit of cleanup and documentation required.
#1295 1315820564000000 rgrp This is mostly done but some final tweaks and name disabling to be done. See work in feature-1294-ux-improvements-dataset
#663 1294660906000000 dread This is my domain, but I suggest you don't assign it to me until it becomes important.
#871 1296340558000000 rgrp This is not a ckan issue. should have been on http://knowledgeforge.net/okfn/tasks
#806 1291134978000000 dread This is not a duplicate of #827
#1543 1324483367000000 dread This is not broken in 1.5 or earlier. Fix is in 1.5.1 release, so not a problem on any release.
#1353 1317075904000000 rgrp This is not deliberate and has been fixed in #1348
#482 1298284158000000 thejimmyg This is now 6 months old and there still doesn't seem to be a requirement for this. Marking wontfix and we can come back to it if it comes up again.
#1192 1310135468000000 thejimmyg This is now a child ticket of #1142
#1514 1323279018000000 rgrp This is now a duplicate of #1534
#1553 1324056939000000 dread This is now ameliorated in thedatahub.org by requiring login to do any edits. But the bug may be an issue for other sites that want more open settings.
#2599 1346756230000000 johnmartin This is now closed and waiting pull request merge back in.
#738 1299761436000000 thejimmyg This is now complete and on UAT.
#569 1297347214000000 thejimmyg This is now complete in ckanext-csw.
#1215 1310385485000000 dread This is now deployed on ckan.net (requires Ctrl-R to reload js).
#878 1315820838000000 rgrp This is now done in feature-1294-ux-improvements-dataset. see e.g. cset:c6f7f5018b4f
#2210 1331549350000000 ross This is now done through the logic layer member_create/member_list/member_delete
#778 1294416567000000 thejimmyg This is now done.
#779 1294416581000000 thejimmyg This is now done.
#780 1294416608000000 thejimmyg This is now done.
#814 1294411109000000 thejimmyg This is now done. It's the "About" link in the main application. Thanks!
#1498 1323165876000000 amercader This is now done. See [1] for the deployment documentation and conventions. CKAN checks the remote schema version on startup to see if it's compatible. See commits starting from 50285ef6. The migration work needed after releasing 1.5.1 is described in #1516. [1] https://github.com/okfn/ckan/blob/feature-1498-multiple-schemas/doc/solr-setup.rst
#813 1294411047000000 thejimmyg This is now done. The text reads "Add a Package" in the main navigation. Thanks!
#1053 1310125444000000 thejimmyg This is now fixed as part of the API refactor and revisioning updates David Raznick has done.
#515 1302774253000000 dread This is now fixed in enh-1046-dictize-the-api. Both groups and packages return the location header.
#996 1300364398000000 thejimmyg This is now fixed, the outcome will be used to inform #995 for the caching.
#847 1295259902000000 pudo This is now functional, minus the index testing tool.
#941 1310134339000000 thejimmyg This is now implemented by pudo in publicdata.eu. For the portal case, apps and ideas will come from Drupal so we no longer need this ticket.
#481 1294248359000000 thejimmyg This is now implemented for DGU.
#939 1323171158000000 thejimmyg This is now implemented, the notification links to the about page. We might want to update that page with better information, but that would be a different ticket.
#103 1311175065000000 thejimmyg This is now implemented. Date parsing is fairly rudimentary but you can now do things like this: http://test.ckan.net/package/uk-crc-rural-services-data@2011-06-10
#2658 1352205894000000 johnmartin This is now invalid due to the work with orgs.
#1065 1303118756000000 thejimmyg This is now more urgent and I think we have enough consensus to go ahead. See #1094 too.
#1020 1300196215000000 thejimmyg This is now on DGU live.
#903 1295265645000000 pudo This is now partially solved by filtering for deleted packages. As two further measures, we should also add a package deletion method to the Solr backend and skip deleted packages when indexing.
#2751 1344015002000000 toby This is now possible via the `paster trans mangler` the initial verdict is that our translation coverage is extremely poor and we need a full template review - maybe there is a jinja2 i18n solution but I think not without `{% trans %}` Moving to phase 4 - also I'm just holding this ticket and will be allocating to aron's successor Publishers vs Groups is more complex than I think is appreciated, is it really worth the time and effort just to make everyone using ckan confused? Anyhow that discussion is not part of this ticket as it is not in-scope
#1013 1299245157000000 sebbacon This is now resolved, but depends on core CKAN behaviour (specifically pluggable middleware and unicode-aware error pages) to function: https://bitbucket.org/okfn/ckan/changeset/c846794c1799
#982 1297850732000000 anonymous This is now rolled into #963. Marking as duplicate. People can get the pip from a branch over HTTP like this: https://bitbucket.org/okfn/ckan/src/<branch-name>/path/to/file/you/want
#1168 1310134901000000 thejimmyg This is now working on dgu-buildbot.okfn.org. The code that manages it is partly the repo.py script from http://hg.3aims.com/public/BuildKit/ and partly the fab code in https://bitbucket.org/okfn/buildbot-scripts
#1176 1310557852000000 dread This is occurring several times a day now - James can you suggest what's happening?
#249 1311182450000000 thejimmyg This is over 6 months old so closing in line with our ticketing policy. Also, I shouldn't think we really want such a complicated search anyway.
#1049 1323169424000000 thejimmyg This is over 6 months old. In accordance with wiki policy, closing.
#185 1291830039000000 thejimmyg This is probably no longer necessary. I've implemented JavaScript to hide the help text and allow it to be revealed by clicking "More >". This makes the form look simpler without needing to hide actual fields.
#1330 1327060201000000 dread This is simply incorrect. test_authz.py (I assume you mean the one in ckan/tests/functional?) tests that authz works all across the Web UI and API in enough detail. The 'total site lockdown' test - perhaps you mean the TestLockedDownViaRoles class which makes up a small part of test_authz? It was a test added due to an untested use case implemented in IATI, DataGM etc. These are currently active so still need testing. Regarding refactoring the tests to be "proper" then please open a new ticket, providing references to why it is not "proper" to test by searching for text in a web response.
#498 1294412520000000 thejimmyg This is something that the Drupal team would need to do. There is no ability or requirement to embed the map widget into the CKAN search system yet.
#809 1297075561000000 thejimmyg This is something to think about more in the future.
#667 1294414834000000 thejimmyg This is something we'll shortly be looking into for DGU work anyway once we switch to the "thin" system so don't need a separate ticket for it here too. Also, the upgrade of SQLAlchmey and test performance improvements may also make this less of a problem now anyway. Marking wontfix.
#560 1288002971000000 dread This is still an issue.
#663 1294414953000000 thejimmyg This is still an issue. Who is best to look into it? Assigning to me for timebeing.
#2599 1340798251000000 aron.carroll This is still broken in IE7 as of 543954b but pretty good in other browsers.
#700 1289823108000000 dread This is still holding back releases. @pudo please can you look at it this
#1503 1323281764000000 dread This is still ongoing - see the spreadsheet!
#804 1294233156000000 thejimmyg This is the document I drafted after discussions with each party which was approved by JF.
#2331 1345192722000000 ross This is the dullest game of ticket tennis ever :D Google don't OR the results, they have an explicit operator for ORing query terms and default to ensuring that all terms are present (in one form or another) in the documents. I understand the argument about cut-offs and relevancy scores, but for a large search engine they have the benefit of scale both in resource and documents. I spent 6 months of my life tweaking weightings for n-dimensional vector space search, I don't think it is likely to be a number we can, or will find by accident. Given that Marcus also got confused by the current behaviour I think we should either: a) Make it configurable b) Just change it to what has been asked for Don't care which.
← 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 →
Note: See TracReports for help on using and creating reports.