Custom Query (2152 matches)
Results (1027 - 1029 of 2152)
Ticket
|
Resolution
|
Summary
|
Owner
|
Reporter
|
#169 |
duplicate
|
Package derivations
|
dread
|
dread
|
Reported by dread,
5 years ago.
|
Description |
A 'Derived' relationship can be applied from one package to another.
e.g.
sussex-demography is derived from census-2001
'Derived' relationship is:
- directional
- many:many
- stateful
'derived' table columns:
- id (primary key)
- source_package (foreign key)
- result_package (foreign key)
- description (markdown text)
Further tickets:
- WUI - package view - shows 'derives from package x' and 'derived package y' with UML-like diagram of x -> this package -> y
- WUI - package edit form - new option to say it 'derives from' or 'has derivation' and you select the appropriate
- REST if - expose reading and writing this property
|
#176 |
duplicate
|
Package dependencies
|
dread
|
dread
|
Reported by dread,
4 years ago.
|
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:
- directional
- many:many
- stateful
'dependency' table columns:
- id (primary key)
- dependent (foreign key)
- dependency (foreign key)
Further tickets:
- WUI - package view - have list of dependencies (do not need to list packages which depend on this one)
- WUI - package edit form - new option to say 'depends on' (no need for 'has dependent package')
- REST api - expose reading and writing 'depends on' property.
Issues
- How do we deal with dependency at a particular version?
|
#1537 |
fixed
|
Package create form wizard
|
icmurray
|
icmurray
|
Reported by icmurray,
2 years ago.
|
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. (*)
- separate pages for each section of the form
- validation carried out at each stage against the whole schema. Each section/page declares a list of schema keys that need to validate for that section to validate, and thus move onto the next section.
- no draft saving to be performed in this ticket.
(*) - although the javascript alternative will probably provide better UX (each step would require a page-load in the wizard approach), it was decided that:
- with the javascript approach it would be harder to test the workflow.
- with the javascript approach there would be additional work displaying validation correctly. Although not that complicated, it was felt to add another point of failure.
- the multi-page wizard is quicker and easier to implement, and if it provided poor UX, then the javascript approach would be used instead.
- the multi-page wizard wouldn't preclude a javascript-tabbing create-form for other cases (where the wizard workflow wasn't such a good match, eg on the hedatahub.org)
- the multi-page wizard wouldn't preclude a javascript-tabbing edit-form.
|
Note: See
TracQuery
for help on using queries.