{23} Trac comments (3729 matches)

Results (501 - 600 of 3729)

← 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 →
Ticket Posixtime Author Newvalue
#1107 1340632612000000 icmurray autocomplete action has been deprecated in favour of /api/2/util/dataset/autocomplete : https://github.com/okfn/ckan/blob/master/ckan/controllers/package.py#L655
#1135 1340632267000000 icmurray Re-assigned to kindly
#1069 1340632215000000 icmurray Assigned to @tobes as he's looking at publication workflows.
#301 1340632055000000 icmurray Unassign in order for it to be triaged.
#285 1340631923000000 icmurray Unassign to be triaged.
#250 1340631430000000 icmurray Package entries already include an enclosure for the json representation of the package: {{{ <link length="1645" href="http://thedatahub.org/api/2/rest/package/microdados-enem-2010" type="application/json" rel="enclosure"/> }}} so it should be easy enough to include something like the rdf link that already exists on a dataset-view page: {{{ <link rel="alternate" type="application/rdf+xml" title="RDF/XML" href="http://semantic.ckan.net/record//4c23a2fd-4349-4525-8de4-3364ce87016e.rdf" /> }}}
#2534 1340631124000000 amercader See #2399
#1553 1340628453000000 aron.carroll Ross, I think you just did :) I'll make sure the new form takes this into account.
#1553 1340628027000000 ross Aron, can I assign this to you for when you do the JS based uploading on demo site/new UI?
#235 1340627624000000 icmurray Replying to [comment:3 icmurray]: > Moved to ckan-future and unassign so that this ticket will be picked up in triage. Sorry, this comment bears no resemblemnce to what I actually did! Assigned to tobes for 1.9.
#2380 1340627558000000 ross Dupe of #2545
#235 1340627057000000 icmurray Moved to ckan-future and unassign so that this ticket will be picked up in triage.
#2552 1340626635000000 ross Clarify
#2550 1340626589000000 ross Clarify
#2548 1340626532000000 ross Accepted to clarify requirements
#84 1340626385000000 icmurray Moved to ckan-future, and assigned to kindly. @kindly : move to a different milestone, or close/won't-fix as you see fit.
#526 1340626152000000 icmurray Won't fix as it's 20 months old, and no feedback on whether it's still relevant or not.
#2495 1340624905000000 amercader See #2467
#2520 1340624831000000 seanh Also see #2370
#2319 1340624083000000 ross Resolved with rework of UI
#2283 1340623843000000 kindly No super tickets anymore.
#1471 1340623578000000 seanh Also test the packaging tools
#2584 1340620576000000 aron.carroll Implemented in 9bebf3d
#2576 1340617688000000 aron.carroll Fixed proper in 4bf158b
#2560 1340617540000000 aron.carroll Clicking "previous" should take you to the last edited resource. Clicking "previous" should take you to the last edited resource but stage 3 should remain active. Clicking "previous" should take you to the last edited resource, clicking next should take you to stage three with the same data as when you went back.
#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.
#2351 1340615641000000 icmurray Scripts and docs in https://github.com/okfn/ecportal-server-setup
#2558 1340615257000000 aron.carroll Marking as fixed. Will create new issues as they arise
#2347 1340613938000000 ross Needs some UI work now, have changed status to blocker which appears to be the only way to denote something as blocked (awaiting resource).
#2528 1340380415000000 toby fixed in 109ec86 what else are we wanting with this?
#2587 1340376975000000 toby fixed by 99d14bd
#2569 1340376578000000 toby @ira, that's fixed in the dev branch just not pushed to demo we need the one i've suggested too
#2587 1340375763000000 shevski If we have a name then yes, should be even without link.
#2569 1340375595000000 shevski Ticket itself is for resource pages, e.g. http://s031.okserver.org:2375/dataset/afterfibre/resource/f5d81da5-2e55-4302-8ed2-58401d2c139e - there are two other resources in that other dataset, should be able to navigate between
#2569 1340375156000000 toby i'm assuming this is the add data part 2 add dataset form
#2440 1340373461000000 toby i'm closing we can make tickets for specific issues
#2555 1340373267000000 toby non urgent moving milestone
#2571 1340369783000000 toby this works so closing
#2576 1340369674000000 toby @aron the resources sidebox is still broken breadcrumb is fixed though
#2581 1340369369000000 toby fixed in commit 0f84d99 in the demo branch david can you just look at this for a sanity check - I'm just concerned that only state benefits from this if good reassign to me and i'll remove the fixme
#2523 1340368036000000 toby there and working
#2558 1340367843000000 toby @aron, metadata now saves pushing back to you - in branch
#2569 1340362284000000 toby @aron, which page is this on? can you add a url - cheers
#2558 1340359174000000 toby groups available now is a helper function (templates updated) commit d0506f3
#2582 1340313961000000 rgrp As this has been a serious UX issue for a while and it may take a while to be fixed I've taken the temporary step of fixing this directly on the datahub.
#2558 1340301273000000 aron.carroll Metadata is back as of b20538f Groups currently aren't showing because the {{{c.groups_available}} param isn't available. https://github.com/okfn/ckan/blob/feature-2375-demo-theme/ckan/templates/package/new_package_metadata.html#L7
#2576 1340300413000000 aron.carroll Fixed in fbeda87
#2374 1340287976000000 ross count is returned at the top level of the dict (at the same level as results) Was added by dread on 2012-05-04, must have been in a recent patch.
#2581 1340287539000000 toby do before data.pop(key)
#2484 1340285964000000 toby merged into master
#2298 1340285049000000 toby related to http://trac.ckan.org/ticket/2579 move sort functions to helpers
#2558 1340284495000000 toby 2) resources save but not sure if being validated etc needs testing but working to an extent @aron, I'm pushing this back to you now reassign as needed
#2558 1340280814000000 toby 1) tags save but don't show in dataset edit - will push fix soon
#2558 1340271359000000 toby @aron, not quite sure what your problem was. I had an integrity error on part 1 save which is fixed. my issues 1) part 1 tags not saved 2) part 2 resources not saved 3) part 3 no form shown - i thought you had one showing where did it go? will look at 1 & 2 for starters
#2365 1340266964000000 ross After discussion with DR, it was decided that multisite wasn't something we would approach now, instead going for individual (shared codebase) installs.
#2556 1340212090000000 aron.carroll Fixed in 2b3b005
#1328 1340191065000000 ross Let's see if this is still an issue in 1.8
#1444 1340190852000000 ross 7 months, no activity, dead bug.
#1345 1340190737000000 ross Moved out of milestone so that it gets looked at again soon
#1452 1340190587000000 ross I believe this has been addressed by Toby.
#2575 1340188954000000 toby wtf I never added that I did write in an hour ago f****g trac
#2558 1340188906000000 aron.carroll Started this as of 4d3c87a however tags need to be hooked up (apparently they can only be added on update at the moment). Also by moving the groups to the metadata form I now get integrity errors while saving. Toby could you please take a look at this.
#2312 1340188741000000 ross We have a ticket for object ownership (group and package) #2548 which will make it much easier to implement this functionality of showing user owned datasets in a 'virtual group'. Will close this in preference to the other ticket which is needed for other features too.
#2323 1340188400000000 ross Can create a new ticket if the requirements change.
#1685 1340188083000000 ross May be subsumed into a service, will keep ticket as a reminder to cleanup
#1684 1340187582000000 ross Left in backlog, but may need re-assessing depending on the data services plan.
#1652 1340187535000000 ross Is this still required?
#2513 1340187230000000 ross Have pushed back to 1.9 but if may be the the converter service will replace it in the meantime.
#2557 1340185609000000 aron.carroll Fixed in 123b914
#2575 1340184557000000 toby @adria, Do you have a url or some more info as I can't reproduce this
#2569 1340123360000000 aron.carroll Templates added in 4e84622 Toby, the implementation in the resource form needs data passing to it. https://github.com/okfn/ckan/blob/feature-2375-demo-theme/ckan/templates/package/pages/form_page.html#L35-36
#2567 1340120404000000 aron.carroll Fixed in 2564dfd
#2566 1340119694000000 aron.carroll Buttons are added in d15cf6f. Toby could you hook these up with appropriate routes.
#2564 1340118952000000 aron.carroll Fixed as of df8f82c
#2527 1340116130000000 aron.carroll Closing as this has been superceded by #2553
#2565 1340116053000000 aron.carroll Social links open in a new tab as of bb41d86
#1737 1340112732000000 icmurray Replying to [comment:23 icmurray]: > > > > Also for the record a couple of things I found when trying to use this: > > > > * No support for facet sort order or facet limit afaict ... > > Thanks, that's good to know. > > facet.limit should be working [1], so if it's not, then that's a bug. I can check that. facet.limit is working as I'd expect. eg (on master): {{{ import requests import json from pprint import pprint as pp pp(json.loads(requests.get('http://ian-laptop:5000/api/3/action/package_search?q=data&facet.field=tags&facet.limit=1').content)) }}} Returns a result where only the tag with the highest count is returned in the search_facets result dict. One thing I did spot though was that we aren't able to specify per-field parameters. ie whilst `facet.limit` sets the facet limit for ''all'' facet fields, solr allows that to be overridden on a per-field basis, eg `facet.tags.limit`. This isn't something we support at the moment. I've created a ticket for this, #2573 . Let me know if this something that you'd find useful, otherwise I'll leave it on the backlog for a future iteration.
#2568 1340108132000000 aron.carroll Fixed in 4d3cd87
#2570 1340107841000000 aron.carroll Closed in a3939a4
#2563 1340106310000000 aron.carroll Done in 73fe36c
#2405 1340097846000000 icmurray Bump: Questions for client team above...
#2536 1340038712000000 toby https://github.com/okfn/ckan/pull/25
#2253 1340038490000000 toby closing as nothing has ever happened with this ticket
#2371 1340038431000000 toby awaiting release and demo theme merge
#2317 1340033433000000 kindly Getting replace as part of new theme.
#2379 1340033026000000 ross Implemented in master
#1197 1340020357000000 seanh AFAIK there isn't a ticket for that, it was something originally requested as part of the demo site, but since the devs think it's a horrible idea I don't think it's going to happen, easiest way to make a CKAN tour would be a series of static pages like the one we already have on ckan.org, I think that combined with a real functioning demo site probably meets the requirement. Anyway, closing this as wontfix
#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?
#1197 1340018903000000 seanh Hi Toby, yes I think I agree with you, it reminds me of when I install new Android apps on my phone, some of them start off by bothering me with some sort of guided tour or long instructional text, I hate this and always skip through without reading it, expecting to be able to figure out the interface for myself. The one thing that something like this could be useful is, rather than showing someone how to use the site, showing them what the site is capable of so they can assess whether it meets their needs/is something they're interested in. However, we already have a good guided tour of this type on ckan.org/features, those pages are really pretty good. Close this as wontfix?
#1737 1340015695000000 icmurray Replying to [comment:22 rgrp]: > But not v1.7.1? (When is v1.8 due?). Not 1.7.1 as it's not a bug fix (https://docs.google.com/document/d/170fxET3kd9dJ4L6VAj3yZugtK0rrVe44J4HuLbTUsEU/) I don't know when 1.8 is due. > > Also for the record a couple of things I found when trying to use this: > > * No support for facet sort order or facet limit afaict ... Thanks, that's good to know. facet.limit should be working [1], so if it's not, then that's a bug. I can check that. for facet.sort, I've added ticket #2543 [1] https://github.com/okfn/ckan/blob/master/ckan/logic/action/get.py#L1022
#2484 1340013145000000 toby merge requested https://github.com/okfn/ckan/pull/17
#1737 1340011203000000 rgrp But not v1.7.1? (When is v1.8 due?). Also for the record a couple of things I found when trying to use this: * No support for facet sort order or facet limit afaict ...
#1737 1340011001000000 icmurray The GET-able actions ( #2330 ) are in master, and will make it into 1.8
#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.
#2198 1339771453000000 kindly Already in the docs.
#2536 1339770953000000 toby minor changes All links now go to the item - before deleted ones didn't. while this makes sense it is inconsistent and adds complexity. Some wrapping spans eg <span class="object">.. have been removed again these add complication and feel wrong given the issues of i18n PS: why messing with my tickets???
#2468 1339757934000000 rgrp DONE. (Closed on github)
#2322 1339750208000000 ross Going to try that last comment again. No, no new features in point releases, we only put bug fixes in unless there is an extremely pressing need.
#2322 1339750135000000 ross No, new new features in point releases, we only put bug features in unless there is an extremely pressing need.
#2322 1339749795000000 rgrp When will this go live? Will this be in v1.7.1?
← 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 →
Note: See TracReports for help on using and creating reports.