Custom Query (2152 matches)
Results (1123 - 1125 of 2152)
Ticket | Resolution | Summary | Owner | Reporter | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
#190 | fixed | Package comments | pudo | dread | |||||||||||||||
Description |
Cost 7 days When viewing a package, users can read user comments and leave their own. Users need to be logged in to leave a message. Comments appear immediately. A mechanism for deleting unwanted comments is provided to an authorized user. Comments are sorted with the most recent first. Comments are available for read, creation and deletion in both the Web UI and over the REST API. The admin for the package and a superuser can delete unwanted comments, both on the package page and a collation of all comments on their user page. Users can delete their own comments(?) Need to consider whether over the REST API we encourage the use of a 'frontend user' APIKEY which can be used to leave comments for another, actual user. Example at bottom of package page: Leave a comment:
Comments:
Implementation details:Comments table is with columns:
|
||||||||||||||||||
#1537 | fixed | Package create form wizard | icmurray | icmurray | |||||||||||||||
Description |
Create the form wizard for the package-new form. Each section of the form will be a separate page as this was decided to be simpler than the alternative of making AJAX calls for validation at each stage. (*)
(*) - although the javascript alternative will probably provide better UX (each step would require a page-load in the wizard approach), it was decided that:
|
||||||||||||||||||
#176 | duplicate | Package dependencies | dread | dread | |||||||||||||||
Description |
(Related to ticket:169 - Package derivations) A 'dependency' relationship can be applied from one package to another. It implies that a package requires the download or existence of another package which it 'depends on'. (Analogous to software package dependencies.) e.g. london-traffic-visualisation depends on road-map 'Dependency' relationship is:
'dependency' table columns:
Further tickets:
Issues
|