{23} Trac comments (3729 matches)

Results (401 - 500 of 3729)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Posixtime Author Newvalue
#906 1328782087000000 amercader Yes, I don't think there will be any problem, and we won't need to create a new version of the schema as the change is backwards compatible.
#662 1288628902000000 dread Yes we all agree this needs fixing it. I'm tempted by John's 'permissive' suggestion of ignoring these 'read-only' values, but to avoid confusion we should except with a 400 error if the user has changed these values. Read only fields: 'id', 'relationships', 'ratings_average', 'ratings_count', 'ckan_url' Use cases for changes between GET package, PUT package: 1. package unchanged - 200 OK 2. user changes id, ckan_url, relationships, ratings_* expecting that value to change - 400 error. 3. just license changes (but not license_id) - 400 error 4. both license and license_id change in step - 200 OK Does that sound reasonable John and Will?
#1167 1306856992000000 sebbacon Yes to all the above. Further question: which extensions should be installed as standard? I would argue: * ckanext-stats * ckanext-googleanalytics * ckanext-disqus * ckanext-solr (implies installing a running solr, too...) * ckanext-follower * ckanext-admin Note that googleanalytics and disqus both require user accounts set up at the corresponding service. Not sure how we would handle this in the instance setup.
#1447 1330082808000000 dread Yes please Nils!
#998 1298372171000000 dread Yes I agree - either of those sounds good. I think I've always used 'db init' in preference anyway.
#2836 1344852009000000 aron.carroll Yeah you can pass an html block into a macro like so: https://github.com/okfn/ckan/blob/2375-demo-theme-development/ckan/templates/package/snippets/resource_form.html#L44-48 What do you think? If it's useful I'll document it.
#1001 1300704249000000 pudo Wrote a WDMMG version of this yesterday: https://bitbucket.org/okfn/wdmmg/changeset/398ce0eb3901#chg-wdmmg/lib/authenticator.py
#1279 1314303732000000 rgrp Wow, that's a pretty big omission. authz groups are important and are used. I think we should discuss this in next planning meeting.
#1065 1302033244000000 dread Wow, lots of solutions here, and not enough evidence of the problems encountered / difficult use cases. I have tried here to extract what John and Seb might be suggesting is difficult with our current http://en.wikipedia.org/wiki/Role-based_access_control system. 1. (Seb) It seems crazy to change the User-Object-Roles for every single package to 'lockdown' a CKAN instance. Instead of using Roles 'reader' & 'editor' we start using Roles 'logged_in_user' and 'anon_user'. Then, with only changing a couple of lines of the Role-Action table for these Roles, you can give or remove permissions to edit / create packages, groups etc. 2. (John) Actions are being added all the time by migrations and extensions. I'm not sure what the problem is here - can someone explain? The separation of Users and the new Actions by adding the Role 'join' means the migration/extension can add existing Users with the new Actions. For example when we added the 'Group' protection object, logged in users could previously create groups, so it is natural to add this action to the 'editor' role. If you get rid of Roles, as John suggests, then you end up having to add as many Rights objects as users. And you might end up trying to infer new Rights on the basis of old Rights, rather than a role, which would be more natural. (Is the only reason to denormalise the UOR and RA tables the sake of ease of understanding? I would think we can explain the concept better now...!) 3. (John) This Group Hierarchy description sounds a bit like earlier incarnations of the DGU requirements. "or any of his groups group-children (but not user-children)" I'm not sure I understand the user-children bit, and I'm wary of any difficult-to-grasp concept. This modelling seems to take the UserGroup/User hierarchy model and use that as a hard-coded interpretation of the Authorized permission. In contrast, in DGU Evan split the Organisation Hierarchy model from the Authorization model. Each User has explicit permissions for each Organisation he is allowed to add/edit packages for. This helps for these two use cases we have to contend with: when a user is an admin for unrelated branches of the Organisation hierarchy, and when an Organisation is actually in two branches of the Organisation hierarchy. It also seems more generally flexible.
#2642 1344243797000000 shevski Would like to have this for next week for a demo if possible
#1245 1311864530000000 annapowellsmith Would be nice to list some extensions somewhere on this site (features page perhaps). Along the lines of: http://docs.ckan.org/extensions.html#finding-extensions It wasn't until I wrote this list that I realised just how many extensions there were, and what it said about the CKAN community that there were so many... So I think it would be a good sales point.
#1374 1317895709000000 dread Would be nice also to print the default language first in the list.
#2678 1342512234000000 shevski Worth checking with Ross on this
#2623 1341232433000000 seanh Works if you remember to enable publisher_auth (the Authorization button never appears, Join is always there, can Edit the org and add users that way)
#2488 1339412538000000 johnglover Works for me on 1.7.1. Perhaps floapps was using older groups (of type 'group' instead of 'organization') and/or didn't add a user to the group?
#1133 1324057072000000 dread Works for me - change occurs successfully. {{{ (pyenv-ckan)[email protected]:~/gitroot/ckan$ paster rights add russianfan admin warandpeace /home/dread/gitroot/pyenv-ckan/lib/python2.6/site-packages/pylons/templating.py:610: UserWarning: Unbuilt egg for setuptools [unknown version] (/usr/lib/python2.6/dist-packages) Engine = entry_point.load() User russianfan -> is admin on -> Package warandpeace (pyenv-ckan)[email protected]:~/gitroot/ckan$ paster rights /home/dread/gitroot/pyenv-ckan/lib/python2.6/site-packages/pylons/templating.py:610: UserWarning: Unbuilt egg for setuptools [unknown version] (/usr/lib/python2.6/dist-packages) Engine = entry_point.load() 22 results User visitor -> is editor on -> Package annakarenina User logged_in -> is editor on -> Package annakarenina User testsysadmin -> is admin on -> System system User logged_in -> is editor on -> System system User visitor -> is reader on -> Group david User annafan -> is admin on -> Package annakarenina AuthorizationGroup anauthzgroup -> is reader on -> Package warandpeace User visitor -> is editor on -> Package warandpeace AuthorizationGroup anauthzgroup -> is editor on -> Group david User logged_in -> is editor on -> Package warandpeace User logged_in -> is reader on -> Group david User visitor -> is reader on -> Group roger User logged_in -> is reader on -> Group roger User russianfan -> is admin on -> Package warandpeace User visitor -> is admin on -> Package warandpeace AuthorizationGroup anotherauthzgroup -> is editor on -> AuthorizationGroup anauthzgroup User russianfan -> is admin on -> Group roger User russianfan -> is admin on -> Group david AuthorizationGroup anauthzgroup -> is admin on -> AuthorizationGroup anotherauthzgroup User visitor -> is anon_editor on -> System system User visitor -> is admin on -> Group roger AuthorizationGroup anauthzgroup -> is editor on -> System system }}} Tests would be nice, but it currently works, is only for admins and is therefore not as high priority as other other tests, such as front-end js.
#2502 1339493182000000 aron.carroll Works beautifully. Be great if we could remove the parens around url_for and add an extra one for h.nav_link but I think call it link_for instead. {{{ {% url_for controller='foo', action='bar', ... %} {% link_for controller='foo', action='bar', class='btn', icon='plus'... %} }}}
#1583 1327422386000000 zephod Working on this on branch feature-1583-qa. https://github.com/okfn/ckan/tree/feature-1583-qa Design work is done, it needs integrating with the live API. That's all in the QA extension. Suggest all my work should be moved into the ckanext-qa extension and plugged into the API available there. Shouldnt have developed this in core after all.
#1236 1311351476000000 dread Working on it on branch enh-1236-view-package-revision
#1683 1326975613000000 dread Workaround done in branch defect-1683-search-order - SOLR is asked for one extra result which it then discards. Merged to master, aimed for release 1.5.2. When we upgrade SOLR from 1.4 then we can remove this workaround
#1003 1298490126000000 rgrp Work so far in http://bitbucket.org/rgrp/ckanjs
#1135 1305210134000000 rgrp Work on this is largely complete in changeset branch: https://bitbucket.org/okfn/vdm/src/changeset/ Overview docs: https://bitbucket.org/okfn/vdm/src/changeset/doc/changeset.rst
#2345 1336492725000000 seanh Work on this has started in branch feature-2345-action-api-autodocs
#1630 1327313971000000 rgrp Work done so far 0.25d. Estimate completion by end of day.
#944 1298571917000000 pudo Won't work on this for now - IATI is now running against plain CKAN but this is not deployed. We will continue work on this once IATI requests more functionality and shelf it for now.
#99 1297081088000000 rgrp Won't fix as we are not using sqlalchemy any longer.
#526 1340626152000000 icmurray Won't fix as it's 20 months old, and no feedback on whether it's still relevant or not.
#2980 1350560137000000 seanh Won't do unless required by a specific client
#293 1271940083000000 johnbywater With the metastable revision of CKAN, the package resource data structure in ckanclient scripts must have all four keys set in the Resource-Dict. Setting 'hash' in the resource data cures this issues with "metastable". The "bad" code was: resources.append((res['url'], res['format'], res['description'], res['hash'])) KeyError: 'hash' This code was adjusted in revision 40c4fe04038d, to default unspecified resource attributes to the empty string. It was changed further in subsequent revisions, to use parameters of the Package.add_resource method to default unspecified values. However, the API doc doesn't mention the resource hash, although it is required, but I just fixed that in the source (in revision 0f20bfb45d13). http://knowledgeforge.net/ckan/doc/ckan/api.html
#1451 1322568784000000 dread With the cron job setup, maybe this is best left as an extension. The core CKAN was designed to be mean and lean.
#1594 1328000053000000 rgrp With #1583 done this is lower priority so deferring into next major milestone.
#789 1294248289000000 thejimmyg Will, this means that we just get given a URL to harvest from and we need to determine whether it is a CSW or a WAF. Can you look at this please? The code may already do it, I'm not sure.
#449 1294411301000000 thejimmyg Will, if this is something you are interested in do you want to kick it off. Otherwise maybe close the ticket?
#191 1305732285000000 dread Will's suggestion is to have "modified_since" param, just as we have for Revision Search. Maybe we don't need a range. 'Order by modification' should be on by default for queries with 'modified_since' param.
#496 1299164106000000 thejimmyg Will has implemented this now and OS have confirmed their export to GeoNetwork works.
#1194 1317053688000000 dread Will go into ckan 1.5.
#2302 1335516537000000 ross Will eventually want to allow customisation of different CSS but designs are currently under review/change.
#1400 1329746131000000 johnglover Will document and update wiki this sprint then ping Mark about a blog post.
#1508 1323168583000000 shevski Will deploy ext-spatial, need to build geo-search for DGU for searching for UKLP datasets - will discuss at next meeting
#2346 1338205553000000 johnglover Will create a separate ticket for 'organization' to 'publisher' renaming, the rest are done.
#429 1285757274000000 dread Will Waites fixed this a couple of weeks ago
#509 1285757116000000 dread Will Waites did this a couple of weeks agoWill Waites did this a couple of weeks ago
#2734 1343121017000000 shevski Wierd. It always breaks for me. Maybe we go through this on skype. I just did it with a non-admin account. Steps: 1. Create new dataset. Name whatever, resource it a link (I use http://trac.ckan.org/ticket/2734) e.g. http://s031.okserver.org:2375/dataset/format-error-test 2. Once you've *finished* the dataset creation process you are on the main dataset page. Click on the resource you added. 3. Click on "edit" 4. Change resource field to "html," for example and click on "update resource" 5. Error shows, clicking on "update resource" doesn't do anything. How about I do it and you watch via screen share?
#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).
#2900 1346335788000000 seanh Why does this only happen on user profile pages and not dataset search page or group read page? Looks like maybe only user profile page uses the package_list.html snippet
#489 1294414420000000 thejimmyg Which RDF service? Why does it need model events? Will, any ideas or shall I close it? Thanks.
#2432 1338325120000000 shevski Where do new tickets go to await triaging? Is priority set by whoever creates the ticket? Does this get revised? Will we have a field for dev time estimate or where will this go?
#476 1294411741000000 thejimmyg Where did this requirement come from? Setting to wontfix for the timebeing. Feel free to re-open if there is a clear use case for this.
#2322 1339749795000000 rgrp When will this go live? Will this be in v1.7.1?
#1401 1326460993000000 dread When javascript calls other scripts, it misses the mount-point prefix. e.g. application.js has hard-coded URL /api/2/util/is_slug_valid The URL prefix is stored in request.environ['SCRIPT_NAME'] so perhaps this value should be put in the HTML somewhere for the javascript to get at?
#1109 1305123852000000 dread What's the status?
#1141 1318862183000000 dread What's the status of this now? The ckanext-moderatededits README still says you need a branch of ckan. Can you say which version of CKAN is required instead? I say we close this if ajax call is now in a better place in the API. (I expect it is now, with the logic layer).
#954 1300447466000000 thejimmyg What would also be really nice is a `help` key in the response which was always returned unless a query parameter of `?help=False` was sent. The help text could explain what the response meant but more importantly would show examples of other calls you can make with the IDs returned such that the whole API is discoverable without anyone ever needing to read any docs! It also means the API documentation is more likely to be up to date since it will be obvious to developers when it isn't. With help=False, the JSON can have all whitespace stripped too for production use. I also think there should be no distinction between GET and POST so that people can easily link to API calls if they want to.
#466 1294411633000000 thejimmyg What was the original requirement? What's wrong with the current HTTP header name? Can we not mark this as wontfix for now and re-open if needed?
#1177 1307360643000000 rgrp What revision of the CKAN code are you using (do hg id to get revision if installing from source). Have you modified the package template in any way? Have you restarted apache after upgrading?
#1792 1332872069000000 dread What is the changeset for this? There is evidence of a branch "enhancement-1792-api-logic" but perhaps this name got fast-forwarded out through a bad merge? Is this merged into 1.6.1 release?
#2781 1343907075000000 aron.carroll What do you mean by "hiding behind that black rectangle"? Just tried it locally with the text "Welcome to the CKAN demo Try out standard CKAN functionality in a sandbox environment. Search for datasets directly from the homepage or by navigating to the Datasets search page where you can facet by tags, groups and format." and it renders okay…
#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
#1409 1319306802000000 rgrp What do we do for people without email addresses (no gravatar or a standard anonymous one?)
#816 1312192499000000 rgrp What about idea of 'model' refactor for resource, specifically to have: * format: human created format string with possible nesting e.g. zip:csv * kind: file | api | example | service * mimetype: standard mimetype (e.g. for zipped csv would be application/zip) * mimetype-inner: mimetype of innermost object (so for example would be text/csv) See http://lists.okfn.org/pipermail/ckan-discuss/2011-April/001139.html
#1378 1324047835000000 dread Went into release 1.5.1
#1695 1330085001000000 dread Went into CKAN release 1.6
#1396 1330086237000000 dread Went into CKAN 1.6
#1413 1330020486000000 dread Went into CKAN 1.6
#191 1330020677000000 dread Went into CKAN 1.6
#1425 1330085282000000 dread Went into CKAN 1.6
#1528 1330020444000000 dread Went into CKAN 1.6
#1536 1330020599000000 dread Went into CKAN 1.6
#1547 1330084379000000 dread Went into CKAN 1.6
#1630 1330085600000000 dread Went into CKAN 1.6
#1493 1324474360000000 dread Went into CKAN 1.5.1.
#1502 1324480415000000 dread Went into CKAN 1.5.1.
#1586 1324480384000000 dread Went into CKAN 1.5.1
#1236 1330019788000000 dread Went into CKAN 1.4.3
#340 1328807317000000 dread Went into CKAN 1.0.2?
#1456 1324472178000000 dread Went into 1.5.1 release
#1141 1318862773000000 johnglover Well, it runs on datacatalogs.org with the current default so CKAN 1.5, but it needs quite a bit of updating to work with all of the new 1.5 UI changes, and as it has been a low priority for quite a while I haven't scheduled time to work on it. Really I would need to spend a few days on it to tidy it up for standard 1.5.
#982 1297518386000000 anonymous Well we could transfer all the dependencies and version numbers to a config file for the fabfile, but we don't achieve much.
#1551 1346662048000000 ross Webstore appears to hav been deprecated in favour of datastore.
#2601 1340960128000000 ross We've taken steps to make sure that users can't add datasets without a group, and can't remove a dataset from a group (without deleting it). Will submit patch to restrict adding without group.
#2434 1341234522000000 seanh We've moved to AWS hosting with docs generated by Jenkins instead, see: http://trac.okfn.org/ticket/1254 There are still two issues to resolve: 1. Automatically updating the symlink so that docs.ckan.org always redirects to the latest stable version 2. Finding somewhere to put links to all the other versions
#466 1282921608000000 dread We've agreed that we need another header for this, although it's not clear that it needs to be configurable. We could just accept Authorization OR the new one.
#1022 1299512991000000 pudo We're now using fileConfig to configure the logger API from the worker config file and this enables us to use SMTPHandler to send out error messages on queue processing failures. Marking as fixed.
#1594 1338203215000000 johnglover We're not using super tickets any more so closing this, most of the smaller tickets are still open however.
#1723 1328533040000000 seanh We're not going to update the existing tag and package classes (as long as they don't break), going to add our own functional tests in a new file instead.
#904 1299840539000000 rgrp We're already now into improving the docs and ticket:927 is now reasonably detailed.
#985 1303118298000000 thejimmyg We'd like CKAN to CKAN harvesting this week if possible.
#691 1294413010000000 thejimmyg We'd also fold up continuous series in search results behind newest sample package. So closing #749.
#691 1294413993000000 thejimmyg We'd also discuss package relationships ideas with JF so closing #444.
#963 1297850773000000 thejimmyg We will also remove all the different pip files as part of this fixing #982 at the same time.
#662 1299755259000000 dread We want this fixed for CLG customer (DGU), so have put in a quick fix into branch 3.1.2 cset:0010a709edf0 (and merged to default) as a stopgap whilst new forms are on their way.
#318 1296482049000000 wwaites We still require form validation to check URIs. They are not free-form strings. This is not the same as 852 or necessarily included in it.
#489 1294416189000000 wwaites We still do need something like this. Right now the rdf generation is a cron job that crawls the API. Really we want two things: * only generate RDF for those packages that have changed * enable multiple client/worker processes, potentially run by third parties, to generate different parts of the RDF description. For example, it is reasonable that we generate the DCat representation ourselves, however the voiD authors (DCat is generic, voiD is about RDF datasets in particular) want to generate the voiD-specific annotations themselves and contribute it back to augment the catalogue. Another example: group curators may also want to annotate packages in their group with group-specific metadata. Yet another example: checks on the coherence, availability, quality, openness, etc. of a package should be done from time to time or when a package changes, which can result in further annotations (see the curate tool). Because of the "third party" aspect we cannot do this with the internal package representation and the rabbit queue. Most likely it is feasible to do this by looking at the revisions in the API to get all changes since the last time a script was run in which case most likely the answer is, yes, there is nothing to do here and the ticket can be closed.
#1037 1303117000000000 thejimmyg We spent last week integrating the new harvesting architecture and testing the code but there are still some areas that need looking at * The source type and label should be part of the plugin, not named in DGU. * Need warnings if a document changes but its date doesn't -> do we have these? * I noticed there are some tests in DGU, should these perhaps be in ckanext-harvest? * If active is False, the job should not be put on the queue * Log if the wrong type of URL is entered as an error the user can see * Deny if the source is already registered * Overwrite all extras, not just merge new ones. * During the import stage use iswms.py to add an extra during import if it is a WMS so that we can add a link to the WMS later https://gist.github.com/900878 * Can errors/warnings be logged in the import stage? Do all fetched documents get passed to import in one go?
#1321 1319558004000000 dread We should not cache if there are flash messages to show (otherwise they get queued up for the next non-cached page view). Fixed in cset:945e2a6ce74f for release 1.5
#2699 1342788074000000 toby We should look at this next weekish
#1608 1325586861000000 ross We should consider some admin dashboard hooks for data such as total file storage usage+count
#1468 1322591997000000 dread We originally talked about a command-line interface for deleting packages. I've done this here: #1499. Note: you can update the search index from a paster shell, simply by doing this before running your commands that edit packages: {{{ from ckan import plugins plugins.load('synchronous_search') }}}
#1383 1319405579000000 kindly We only added the Iresourceurlchange interface as we made the IDomainObjectModification include the Package.
#803 1314031451000000 dread We now use nose to test migrations instead.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracReports for help on using and creating reports.