Custom Query (2152 matches)
Results (1099 - 1101 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1174 | wontfix | API Representation Registry | pudo | pudo |
Description |
As CKAN grows, more and more optional representations of packages will become used. Besides RDF (which is the motivation for this ticket), support for DSPL, home-grown XML, or CSV listings is imaginable. To properly support this CKAN should have an extensible representation registry that can be extended when new output types become available (and without changing the API in the process). This needs to integrate in two places:
To support this we should have a registry with two registers:
This should be set up on load_environment so that IConfigurer plugins can feed into it. The registry should then first be added to _finish in the REST API (which needs to be refactored to be passed the {format} part of the URL if one is given. Based on the format part and HTTP headers, an appropriate representation can be generated by the registry and then be returned to the user. Forwarding of requests to the regular WUI controllers with Accept headers set or a format specified can be implemented in a separate effort. |
|||
#1199 | fixed | Implement an email function for users. | pudo | pudo |
Description |
We need an email function in CKAN to accept messages sent to users. The basic signature will be:
This has a number of use cases:
Finally, the mail function should be exposed in the API for sysadmin clients. This way we can have scripts traverse CKAN for 404s, invalid data or missing fields and ping users about that automatically (requires traversal by revision, not package, to get the associated users). ImplementationNote we have already written code like this (*and* tested it) in isitopen: |
|||
#1223 | fixed | Caching of static files | pudo | pudo |
Description |
StaticURLParser can have caching - use it |