{23} Trac comments (3729 matches)

Results (1601 - 1700 of 3729)

← 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 →
Ticket Posixtime Author Newvalue
#1570 1324314741000000 rgrp Deleting this ticket as integrated file storage has been available and finished for months.
#1571 1325265148000000 rgrp Rewrote description extending it significantly and linking to etherpad and code.
#1571 1325555270000000 rgrp Done (4d) ago: rename todo(s) -> issue(s) in extension
#1574 1325774336000000 rgrp @ross: Is it possible to update the detailed description of this ticket so it reflects current reality (whatever that is ;-) ) (BTW: you can edit the main descript of the ticket by scrolling to the bottom of this ticket edit page)
#1575 1325866330000000 rgrp Can we also lose the Canada government group. Let's just have have the Canada group plus a tag for gov (e.g. just gov or gov-canada or canada-gov or ...)
#1576 1325183389000000 rgrp Updated wiki page (stats was not on there yet!): http://wiki.ckan.org/Extensions#Stats_-_Statistics_for_CKAN and added deprecation notice on https://github.com/okfn/ckanext-stats
#1576 1325190496000000 rgrp Fixed. Merge cset: https://github.com/okfn/ckan/commit/cb29d62133bb4d060622f2fa752dd281b71a252b
#1576 1327056070000000 rgrp Some questions arising from this. Now on http://ckan.okfnpad.org/extensions * How do I add Stats to a menu ... * ANS (?): Main menu: should make this configurable sooner rather than later (what about footers ...) * How do I have plugins support other plugins ... * E.g. stats incorporate QA info == Extensions in Core == * Do we centralize templates and public directory or not ... * (+) quicker, simpler * (-) have to change things, does it mess up non-core extensions * Tests: need to be run! (Put them into core area ...) == Qu: Going forward how do we handle extensions and plugins == Specifically: * Inclusion of html into *core* html - e.g. showing download counts ... * Concrete examples: * Including widgets into the dashboard * Including widgets in stats section * (not simply inclusion of html into routing system separate from core -- which is relatively trivial) * More entry points? == Other stuff I think we should look at == * config in dashboard
#1577 1325473564000000 rgrp Foreign characters aren't allowed in file names I would image as they will be part of url. worth noting this at some point but don't think this is very high priority and hence deferring out of v1.6.
#1578 1325473015000000 rgrp Removing from v1.6 as not high enough priority atm to justify.
#1583 1324484387000000 rgrp I'm not sure star rating is the key thing I want to know and I also think it will be visually very confusing (I associate stars with ratings now with some automatic quality assessment + (IMO) 5 star isn't that useful). I'm much more interested in things like: * Is this down (all the time) * Has this been down recently * When was this last modified (not quality per se ...) This is an area where referring back to the original user stories (if any) around QA is really useful. I guess my feeling would be some of this should be about providing e.g. helper methods so that theme designers can incorporate things into their design with some work putting this into default CKAN theme.
#1584 1325475164000000 rgrp Moving out of v1.6 until determined it is in (super ticket is in).
#1588 1325475117000000 rgrp Moving out of v1.6 (super is in atm).
#1589 1325475095000000 rgrp Moving out of v1.6 (super ticket is in).
#1591 1325866229000000 rgrp Report of time spent / time estimate would be brilliant :-)
#1591 1327317321000000 rgrp Done. (DGU waiting on integration)
#1594 1325473486000000 rgrp #1583 seems important and quick. #1584 I'm more dubious about esp as I think time estimate may be a bit optimistic :-) (e.g. #1584 includes search of reports ...). At this point in time I'd vote for #1583 plus deployment as good enough for v1.6.
#1594 1328000053000000 rgrp With #1583 done this is lower priority so deferring into next major milestone.
#1597 1325202152000000 rgrp Is there not a limit option to the package_search action (if not maybe there should be (with say a maximum of 200 ...)). Also I'm not sure how essential this is to #1521. In general we just want to search (and facet on) datasets and resources not on tags. So IMO: this is a low value item.
#1598 1325474818000000 rgrp Moving out of v1.6 as many more important things to do.
#1599 1325555192000000 rgrp Done. See http://okfnlabs.org/ckanjs/widgets/count/ and live deploy at http://openeconomics.net/ (RHS sidebar).
#1600 1327335778000000 rgrp Booted: https://github.com/okfn/help.thedatahub.org
#1600 1327401279000000 rgrp Update (for reasons to do with CNAMES) repo is now: https://github.com/okfn/datahub-help Pages are now deployed at (no theming yet!): http://help.thedatahub.org/
#1600 1333362031000000 rgrp Closing as wontfix atm since think this will either go to main manual or won't be done here. (Also did quite a lot of work).
#1602 1328175521000000 rgrp Image (pre)viewing done in https://github.com/okfn/ckan/commit/2b08425c3aef424d4192838e418b7ad9ccc6a129.
#1602 1328175553000000 rgrp (Time elapsed: 1h.)
#1602 1328175719000000 rgrp Closing ticket as everything done except geo (pre)viewing and that is a substantial chunk of work that needs planning and is already separately ticketed (and was already marked as (?)).
#1608 1328101443000000 rgrp Want to re-enable direct upload to cloud storage.
#1608 1328175329000000 rgrp Fixed in https://github.com/okfn/ckan/commit/4488795a54866a02305268d77a2648fa85538ee8 And working on <http://thedatahub.org/>, test etc. One important note: test using remote storage has been disabled -- see https://github.com/okfn/ckan/commit/3c9ddd31d741eb8ec8c145063ce967e781947a88 Time spent: 0.25d.
#1609 1325774098000000 rgrp Move analysis into main body of ticket.
#1609 1326905350000000 rgrp Any comment on how this related to #1398 - Automated conversion of resource data into webstore. They seem to be exact duplicate -- but obviously #1398 was done and this wasn't.
#1610 1325773944000000 rgrp IMO this is very low priority at the moment (also I guess this ticket which is webstore only should go in http://github.com/okfn/webstore/issues -- though that is something of a moot question)
#1613 1325866393000000 rgrp Why is this a problem. It is a very minor annoyance. I'd strongly vote for deferring and, if necessary at all, integrating with #1506 (UX improvements).
#1615 1325774573000000 rgrp We have done several successful deploys behind a proxy server on apache. Any details of what didn't work? Worth adding details here: http://wiki.ckan.org/Deployment ?
#1630 1327313971000000 rgrp Work done so far 0.25d. Estimate completion by end of day.
#1630 1327620031000000 rgrp Did not make it by end of day but now done!
#1630 1327620506000000 rgrp Done, see: https://github.com/okfn/ckan/commit/211c8006fe28106f532db5f09ca47e02f065f454
#1649 1330860766000000 rgrp A general comment: I wonder if we can pull the *core* part of that extension into core and strip out any external dependencies like rdflib. Specifically the 80% use of this extension is the DCAT read/write: * Get a Dataset / Resource etc as DCAT RDF (I'd suggest we *just* supply something simple like n3 or even json-ld (see below)) * (Possibly not even essential) Consuming Dataset info in that format And even more radical solution would be to simply use json-ld: http://json-ld.org/ which would then just involve minors mods to our json output. Having this in core (with option to enable?) would be a nice 80/20 (it was this feature that everyone asked for at the LOD meetup -- no-one mentioned SPARQL).
#1649 1331550598000000 rgrp Can you elucidate on this template idea? I was thiking we want specification/configto be in the form of mappings (e.g. field X is really type Y etc rather than a specific piece of rdf/xml or n3) though perhaps that makes more sense. Let's centralize discussion on this in #2209.
#1654 1330863104000000 rgrp I'd vote -1 on SPARQL endpoint and doing the simple version of #1649 as proposed in my comment http://trac.ckan.org/ticket/1649#comment:2
#1660 1327614737000000 rgrp The broken-ness arose from a (very sensible) refactor (done by Tom Rees) to be stricter about what we tried to preview. Rather than hack around the conditions of the format string for previewing, my strong suggestion is to get rid of weird format types like x-osdata-csv (just change it to csv). An alternative, that would preserve ability to set 'funky' formats would be to set the mimetype correctly (to text/csv) (this may still need an update to the previewer but one that would be sensible to make).
#1660 1327616782000000 rgrp Update: I've done the change I suggested and it now works fine.
#1687 1329338671000000 rgrp Closing as unclear what this involves (blob storage changes were deployed but webstore ones weren't ...)
#1691 1327314081000000 rgrp OK Great. I only raised this because James mentioned this at sprint before Christmas as did Fry guys. One of us should update James on this at next standup.
#1709 1327620136000000 rgrp I have already fixed the issue with counts (in a branch to be merged) :-) Also this is opened in an already ended sprint :-) IMO we don't bother testing simple_search since intended to be hacky and unsupported. Worth documenting the option but highlighting non-supported nature.
#1709 1327620218000000 rgrp I also note there is an error with how importing was working (re top level imports in lib/search.py) that meant simple_search was broken. I've fixed this locally and raised with Ross (whose commit triggered the problem) ...
#1718 1328093772000000 rgrp WEll known issue. Just needs an upgrade in jquery to 1.7.
#1719 1328519411000000 rgrp Fixed in https://github.com/okfn/ckan/commit/90c76b0b006cf505698834e833b548634cf10d17 (see log message for details of error and the fix).
#1737 1330908235000000 rgrp Did not get to this sprint as focused on #1797.
#1737 1336328947000000 rgrp Having now thought about this I'm re-opening this ticket for the following reasons: * No real documentation (other than that in this ticket yet available) * It would also be nice to know how this maps to SOLR API (can i use all of the facet options solr provides or not ...?) * And I would again emphasize my preference for having *direct* access to something that looks *exactly* like SOLR API as I can then use client and docs from SOLR to work with it. * No clear resolution of separation between Action and REST API (and search API). Really seems to me there should be convergence between latter 2 (as suggested in the ticket) -- this would also resolve the problem that having GET /api/dataset return all datasets is *not* a great idea * The Action API requires a POST request. Since the primary purpose of the search API would be usage from JS it would be nice if GET and JSONP were supported. (Though given our CORS support we could argue this was optional). Not saying *all* of this needs fixing but some clear approach here would be useful
#1737 1337942345000000 rgrp I *strongly* disagree re access to solr API -- i don't really care if it is direct but I want something that looks like it at least for core query parameters and facets ... Is there some major issue around security etc (e.g. limiting to only public datasets or similar?)
#1737 1338719220000000 rgrp Let's close. What would be nice though is ETA on the GET support getting deployed on the DataHub -- just tried using it today and realized it didn't work :-)
#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 ...
#1739 1328176197000000 rgrp Sorry if we did. I (and Tom) do run tests ;-) However, occasionally I'm unsure whether I've caused a problem when there are existing failures.
#1741 1328526473000000 rgrp 2.5d, 1d remaining.
#1743 1328527086000000 rgrp Marking as wontfix - as per discussion here: http://lists.okfn.org/pipermail/ckan-dev/2012-February/001652.html
#1753 1330908337000000 rgrp As of today kindly has this working in https://github.com/okfn/ckanext-webstorer/tree/webstorer-for-datastore and deployed on the DataHub. Need to merge into master and to possible rename of extension, update docs and we are done.
#1788 1330111162000000 rgrp Believe most of these are resolved by https://github.com/okfn/ckan/commit/27f4fc776b9199621d259749cf20787328df101f @zephod: could you check again and see if anything remains?
#1788 1330644056000000 rgrp Re the Upload file button not sure what's best. We do have plans to replace jquery-tmpl with mustache in the near future (but not clear exactly *how* near). We'll think about this and get back to you. Thanks for the detailed debug report.
#1797 1330550304000000 rgrp New API endpoint, Authorization and documentation done and merged to master. Time so far. 1.5d. https://github.com/okfn/ckan/commit/a054071e2e29e70e7cfa69df8c117ad5d5871a24
#1797 1330863639000000 rgrp Data Viewer support for new DataStore in https://github.com/okfn/ckan/commit/9ab8b0283bb086eb4cd663ff73c27066bdd3c79a
#1797 1331412469000000 rgrp All done!! Help for data api done in https://github.com/okfn/ckan/commit/1d8e464f8542d4c33286bb93f4de50060665799f Checkbox for datastore enabled in https://github.com/okfn/ckan/commit/3f1320cd92ae0e775fde1b5eada156260c55e0a6
#1797 1331412644000000 rgrp Merge fix https://github.com/okfn/ckan/commit/476a5bd32a3fac5d2dd85614f5d86c79f4ff6547
#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 ...)
#1828 1330525412000000 rgrp Fixed in https://github.com/okfn/ckan/commit/e6da48d9337575a83bc6a30896e68d1081b43847
#2201 1330765400000000 rgrp Duplicate of #1171.
#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 1337582843000000 rgrp Surely this ticket was closed 3w ago? @Ross: can you close ...
#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.
#2224 1332475944000000 rgrp Autocomplete based on bootstrap looks pretty non-trivial ...
#2226 1332475468000000 rgrp All done (as of Tuesday in fact!). No doubt further work to do but that's a new ticket!
#2234 1337237687000000 rgrp This looks interesting but is this a priority :-) (also no estimate as yet :-) )
#2236 1332153688000000 rgrp Done. See https://github.com/okfn/ckan/commit/0d970d3a0e523a1695830e8c8c28c0ba10a8d8b9
#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 1332524123000000 rgrp Update description in great detail.
#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.
#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 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 :-)
#2278 1333441177000000 rgrp https://github.com/okfn/ckan/commit/b7b32820a9132811028e7ccc243b2d2339492d4d
#2284 1337583675000000 rgrp This needs connecting to the user stories being generated at http://ckan.okfnpad.org/dataexplorer-user-stories
#2285 1334580266000000 rgrp Recline improvements are done. https://github.com/okfn/recline/issues/88
#2292 1335021860000000 rgrp This annoyed me so much I just fixed it: https://github.com/okfn/ckan/commit/5eca7d5e37c0ef392b768b8b3768b2c3f93448b5 Issue was that our auto-completion depended on structure of the HTML which changes with bootstrapification. BTW: have deployed this via copy and paste on datahub so i can use it. Will want to revert this when you do a deploy. @Ross: I note that the same bug probably affects organization auto-complete.
#2322 1339749795000000 rgrp When will this go live? Will this be in v1.7.1?
#2322 1344086640000000 rgrp Can I confirm this is in v1.8 ...
#2331 1338390995000000 rgrp @kindly I really don't get this but I may understand poorly. Google does not work by or-ing does it (as i add things to the search query I get *less* results not more ...). It also makes it really hard to find stuff: as I add query terms to my query I get more stuff not less which makes for terrible finding of stuff - I appreciate that there is a scoring aspect but that seems secondary.
#2331 1343814758000000 rgrp I'm re-opening this. This is a reasonably significant UX problem -- not just a philosophical difference. It is just *weird* to get *more* results as I add search terms rather than less. Please can we have this fixed ...
#2331 1345191494000000 rgrp Re-opening yet again. This is something brought up by entire client team on several occasions :-) We really do need to fix this as it is really poor UX. To give, yet another, example: http://datahub.io/dataset?q=thatcher+wages This returns 15 datasets yet only one of them has any mention of thatchers (the first one!). (The others are there because they match wages). This isn't what I expect. I expect *only* to see datasets that match *both* terms ...
#2331 1356474344000000 rgrp Now transferred to github at https://github.com/okfn/ckan/issues/258
#2332 1337582891000000 rgrp @rossjones / @amercader: can you do a full review and generate sub-tickets as necessary (obviously may not all be this sprint ...)
#2347 1337238738000000 rgrp This looks great Ross. Couple of things not included (which I have taken liberty of adding to the description as well - you will probably want to tidy up): * Related is a pretty terrible name in the UI - much better to have it called Apps, Ideas etc (perhaps title tag could even give more details e.g. "Apps, Ideas, Visualization and other material related to this dataset") -- btw i thought this was in #2332 but realize it wasn't (apologies for that!) * Documentation, documentation, documentation - AFAICT I can't see anything in v1.7 or master docs. I imagine this would be a short section like http://docs.ckan.org/en/ckan-1.7/commenting.html (and probably coming right after that in the ToC) which says * What it does * How to enable (and perhaps includes a nice-screenshot!) * How to customize (e.g. can one customize the list of options of things one can create (e.g. can I set it to just be app and idea or ...) * Also liase with Mark W re a blog post about this from the user perspective (a screenshot walkthrough ...) * Clearly mark this old extension as deprecated from v1.7 forward: https://github.com/okfn/ckanext-apps (I just met someone last week who was working on integrating this and had no idea it was replaced by something better in v1.7)
#2389 1337237502000000 rgrp Just to note these were 2 *different* options. '''Either''' you do the fallback approach '''or''' we turn off DataStore by default and only use if enabled (which happens due to explicit enabling of DataStorer turning it on ...)
#2405 1337583749000000 rgrp Assigning to ross for review and assignment.
#2468 1339757934000000 rgrp DONE. (Closed on github)
#2550 1342535924000000 rgrp Sounds good. BTW all users stories if at all possible go in google docs now for permanence. Here is the template: https://docs.google.com/document/d/1U5yahDrvp_PKQMNjzI_8u3xixnALf4eNZWK2BdTXOVw/edit
#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.
#2639 1345125290000000 rgrp #196 is fixed. Not sure about #195. Otherwise think we are good to go.
#2639 1345125344000000 rgrp There is also an additional issue which is that recline no longer uses elasticsearch_url so we will need to patch this either in js or in the controller code for the embed ...
#2639 1345146087000000 rgrp Also found that previous recline setup used elasticsearch_url in recline 'state' (dataset part) when generating embed_url for dataset. But recline no longer supports this so move to url attribute of dataset attribute of state.
#2639 1345146289000000 rgrp Port of fix for recline issue 196 in https://github.com/okfn/ckan/commit/fd1abd9d5701b4addf7e709c1766d6ffed1bb8bf Fix of embed issue in https://github.com/okfn/ckan/commit/fd1abd9d5701b4addf7e709c1766d6ffed1bb8bf
← 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 →
Note: See TracReports for help on using and creating reports.