Custom Query (2152 matches)
Results (1447 - 1449 of 2152)
|
Ticket
|
Resolution
|
Summary
|
Owner
|
Reporter
|
| #1526 |
fixed
|
[super] Update and test existing DGU package form
|
icmurray
|
icmurray
|
|
Reported by icmurray,
2 years ago.
|
| Description |
Re-create behaviour of old form without using form-alchemy. And unit test.
- [X] write high-level functional tests for the form. Creation / edition / validation.
Original estimate: 6 days (3 days x 2)
Time spent: 3 days
Time remaining: 0 days
Original estimate: 2 days (1 day x 2)
Time spent: 1.3 days
Time remaining: 0 days
- [X] modify the existing validation schema
Original estimate: 2 days (1 day x 2)
Time spent: 1.3 days
Time remaining: 1 days
- [X] split resources into types: individual, time-series, and additional.
Original estimate: 2 days
Time spent: 2.5 days
Time remaining: 0 days
- [X] contact information is derived from Publisher, but can be altered for each dataset. #1617
Original estimate: 4 days
Time spent: 0 days
Time remaining: 4 days
(Waiting on publisher integration)
- [X] foi contact information is derived from user, but can be altered for each dataset. #1617
Original estimate: 1 days
Time spent: 0 days
Time remaining: 1 days
(Waiting on publisher integration)
- [X] provide stubs for the theme and sub-themes #1618
Original estimate: 1 days
Time spent: 0 days
Time remaining: 0 days
- [X] provide stubs for the publisher hierarchy #1619
Original estimate: 2 days
Time spent: 0.5 days
Time remaining: 1.5 days
Note - the groups refactor is essentially ready to be used. And this would be a good test case for it.
- [X] don't allow package-type selection when editing a package
Can't change a dataset from containing time-series resources to one containing individual resources or visa-versa. (#1620)
Original estimate: 0.5 days
Time spent: 0 days
Time remaining: 0 days
|
| #1527 |
fixed
|
Break DGU package edit form into sections
|
icmurray
|
icmurray
|
|
Reported by icmurray,
2 years ago.
|
| Description |
- use javascript to selectively hide/show parts of the form
- there's no validation between steps at this stage. It's still a
"big save button at the end".
|
| #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.
