{23} Trac comments (3729 matches)

Results (2701 - 2800 of 3729)

Ticket Posixtime Author Newvalue
#665 1294247602000000 thejimmyg Duplicate of #884
#665 1297268097000000 thejimmyg The latest version of the DMS collection interface spec says that this should be a manual process. No work to be done.
#664 1294413696000000 thejimmyg @pudo is this still valid?
#664 1300371645000000 kindly fixed cset:a5f4a49190e2
#663 1294414953000000 thejimmyg This is still an issue. Who is best to look into it? Assigning to me for timebeing.
#663 1294660906000000 dread This is my domain, but I suggest you don't assign it to me until it becomes important.
#663 1298913603000000 kindly cset:76a77439ecd0
#662 1286991079000000 dread I agree we should not have the 'read-only' things like Ratings in the default returned Package Entity. What do you think of having a parameter to be able to get these if you want them though? Do you mean you *can* re-post the *entity* post response? Not sure what you mean by "An issue for CKAN too."? In addition to this ticket, what do you think about changing the behaviour of the Package Entity PUT/POST, so that you replace the entire Package, not just the fields you specify? So you don't keep left-over values, just because you didn't specify them as null?
#662 1286993727000000 johnbywater It might be natural for the locator of the rating for a package to be "/package/{id}/rating". I've got not idea what I meant by "An issue for CKAN too." I may have intended to log this againt ckanclient. Anyway, it seems to be just a CKAN thing. :-) I think I would like to do this: $data = c.package_register_post({'name': 'example'}) $data['title'] = 'Example' c.package_entity_put($data['id'], $data) and this: $data = c.package_entity_get('example') $data['title'] = 'Example' c.package_entity_put($data['id'], $data) I don't think either work. We could write a test for each. I think this does work: $data = c.package_entity_get('example') $data = c.package_entity_put($data['id'], $data) $data['title'] = 'Old Example' c.package_entity_put($data['id'], $data) Which is inconsistent. The reason is that the data returned by the update operation ("entity put") isn't given the same treatment as the read and create operations, which adds various read-only values. That's as far as I got. I inferred that one or several of the read-only values, when present in the update request data, cause the update to fail. I'm not sure how it fails. Rather than cutting down the response data, we could make the update call more robust. One fix would pick out from the request package data only the attributes that are permitted. A alternative fix would make what ever is choking on the extra values ignore them. I mean, ids are read-only, but we wouldn't want to reject an update because it has an id in the data. We do need to be careful about loading up the package entity data, but the 'id' is read-only and we aren't going to quible about that being present in the data of an update request (even if it doesn't match the referenced entity). I would rather not support "replace the entire package" with especial functionality and documentation. I think the model create/update/delete, where update is "set attributes" is sufficient, simple, and fairly optimal. To obliterate all registerd values without deleting, I would get the package entity data, loop over the keys and set the values to '', [] or {} depending on the type, and then PUT the entity. We could write a test for that.
#662 1288624137000000 wwaites Ran into this with RDF export (that then updates the CKAN package with LOD2-compatible extras from the results). Cannot use ckanclient.package_entity_put(ckanclient.package_entity_get("ckan")). Is this related to the modifications htat are showing up in the changelog with no apparent package (the package that should be appearing there is "ckan" itself)
#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?
#662 1297344790000000 rgrp Now part of 'model/validation/forms' meta-ticket #961 so reassigning to Seb.
#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.
#662 1301076443000000 dread Bug: license_id field is assigned the value of the 'license' parameter.
#662 1301076463000000 dread license bug fixed in cset:00038ef33c45
#661 1288271266000000 dread Friedrich has done the main meat of this in ckanext/blackbox/smoke.py I've extended it to include http basic auth, testing wanted error statuses, checking API calls etc.
#660 1311183115000000 thejimmyg This ticket is more than 6 months old so closing it in line with our ticketing policy.
#659 1298379892000000 dread Smoketest scripts exist for exactly this in ckanext. It would be great to have this running on nagios. It is as simple as running: python blackbox/smoke.py -H ckan.net blackbox/ckan.net.profile.json See here for code: https://bitbucket.org/okfn/ckanext/src/default/blackbox
#659 1298424109000000 nils.toedtmann Good idea. Listed this in my nagios ticket http://knowledgeforge.net/okfn/tasks/ticket/600
#659 1311183031000000 thejimmyg Since there is already an implementation and already exists as a ticket in the OKFN tasks, I'm marking this as closed. If there is a reason this is still open, please add it to a more appropriate ticket, such as the API version 3 one.
#658 1285252726000000 johnbywater Referencing ticket #655 has changed sprint.
#657 1285252726000000 johnbywater Referencing ticket #654 has changed sprint.
#656 1285252726000000 johnbywater Referencing ticket #654 has changed sprint.
#655 1285252726000000 johnbywater Referencing ticket #654 has changed sprint.
#652 1284998201000000 pudo Fixed in cset: 688cbd25b3f0 (ckan-authz2)
#651 1311169144000000 thejimmyg This has been open for more than 6 months so closing it. It may even have been fixed in John's auth refactor.
#651 1311171097000000 dread Yes, John fixed this. Changing to fixed.
#650 1286789277000000 johnbywater Moved from sprint 1.2.7
#650 1287391932000000 pudo included since cset:781ef73e61cc
#649 1284889939000000 pudo developed in cset:e65d7342ffe4
#648 1284889656000000 pudo introduced in ckan-authz2 cset:934b30ec84fd
#646 1294413500000000 thejimmyg This is a Drupal requirement rather than a CKAN one for the timebeing.
#645 1284750525000000 johnbywater Moved from sprint 1.2.3
#645 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#645 1285957164000000 johnbywater Referencing ticket #572 has changed sprint.
#645 1286786420000000 johnbywater Referencing ticket #572 has changed sprint.
#645 1287392122000000 johnbywater Referencing ticket #572 has changed sprint.
#644 1284689350000000 johnbywater Referencing ticket #579 has changed sprint.
#641 1284689330000000 johnbywater Referencing ticket #577 has changed sprint.
#636 1284689350000000 johnbywater Referencing ticket #579 has changed sprint.
#635 1285348167000000 johnbywater Referencing ticket #572 has changed sprint.
#635 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#634 1285348167000000 johnbywater Referencing ticket #572 has changed sprint.
#634 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#633 1285348167000000 johnbywater Referencing ticket #572 has changed sprint.
#633 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#632 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#630 1285348178000000 johnbywater Referencing ticket #572 has changed sprint.
#629 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#628 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#626 1284750525000000 johnbywater Moved from sprint 1.2.3
#626 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#623 1285348152000000 johnbywater Referencing ticket #568 has changed sprint.
#623 1286786419000000 johnbywater Referencing ticket #568 has changed sprint.
#623 1287392122000000 johnbywater Referencing ticket #568 has changed sprint.
#622 1285348152000000 johnbywater Referencing ticket #568 has changed sprint.
#622 1286786420000000 johnbywater Referencing ticket #568 has changed sprint.
#622 1287392122000000 johnbywater Referencing ticket #568 has changed sprint.
#621 1285348152000000 johnbywater Referencing ticket #568 has changed sprint.
#621 1285957164000000 johnbywater Referencing ticket #568 has changed sprint.
#621 1286786420000000 johnbywater Referencing ticket #568 has changed sprint.
#621 1287392122000000 johnbywater Referencing ticket #568 has changed sprint.
#621 1287776309000000 johnbywater Referencing ticket #568 has changed sprint.
#618 1284219775000000 johnbywater Referencing ticket #571 has changed sprint.
#617 1284219609000000 johnbywater Referencing ticket #570 has changed sprint.
#617 1284225063000000 johnbywater Referencing ticket #570 has changed sprint.
#617 1285199168000000 johnbywater Referencing ticket #570 has changed sprint.
#617 1285629333000000 johnbywater Referencing ticket #570 has changed sprint.
#617 1286786420000000 johnbywater Referencing ticket #570 has changed sprint.
#617 1287392123000000 johnbywater Referencing ticket #570 has changed sprint.
#617 1287703431000000 johnbywater Referencing ticket #570 has changed sprint.
#617 1288038146000000 johnbywater Referencing ticket #570 has changed sprint.
#617 1294408164000000 thejimmyg Duplicate of #569.
#616 1284219609000000 johnbywater Referencing ticket #570 has changed sprint.
#616 1284225063000000 johnbywater Referencing ticket #570 has changed sprint.
#616 1285199168000000 johnbywater Referencing ticket #570 has changed sprint.
#616 1285629333000000 johnbywater Referencing ticket #570 has changed sprint.
#616 1286786420000000 johnbywater Referencing ticket #570 has changed sprint.
#616 1287392123000000 johnbywater Referencing ticket #570 has changed sprint.
#616 1287703431000000 johnbywater Referencing ticket #570 has changed sprint.
#616 1288038146000000 johnbywater Referencing ticket #570 has changed sprint.
#615 1284219609000000 johnbywater Referencing ticket #570 has changed sprint.
#615 1284225063000000 johnbywater Referencing ticket #570 has changed sprint.
#615 1285199168000000 johnbywater Referencing ticket #570 has changed sprint.
#615 1285629333000000 johnbywater Referencing ticket #570 has changed sprint.
#615 1286786420000000 johnbywater Referencing ticket #570 has changed sprint.
#615 1287392123000000 johnbywater Referencing ticket #570 has changed sprint.
#615 1287703431000000 johnbywater Referencing ticket #570 has changed sprint.
#615 1288038146000000 johnbywater Referencing ticket #570 has changed sprint.
#614 1284219601000000 johnbywater Referencing ticket #569 has changed sprint.
#614 1284689449000000 johnbywater Referencing ticket #569 has changed sprint.
#614 1285199361000000 johnbywater Referencing ticket #569 has changed sprint.
#614 1285957164000000 johnbywater Referencing ticket #569 has changed sprint.
#614 1286786420000000 johnbywater Referencing ticket #569 has changed sprint.
#614 1287392122000000 johnbywater Referencing ticket #569 has changed sprint.
#614 1287703423000000 johnbywater Referencing ticket #569 has changed sprint.
#614 1288038146000000 johnbywater Referencing ticket #569 has changed sprint.
#613 1284219601000000 johnbywater Referencing ticket #569 has changed sprint.
#613 1284689450000000 johnbywater Referencing ticket #569 has changed sprint.
#613 1285199361000000 johnbywater Referencing ticket #569 has changed sprint.
Note: See TracReports for help on using and creating reports.