[JIRA] Created: (DSY-458) Document tasks improvement ideas

View: New views
3 Messages — Rating Filter:   Alert me  

[JIRA] Created: (DSY-458) Document tasks improvement ideas

by JIRA issues@cocoondev.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Document tasks improvement ideas
--------------------------------

         Key: DSY-458
         URL: http://issues.cocoondev.org//browse/DSY-458
     Project: Daisy
        Type: Improvement
 Reporter: Bruno Dumon
    Priority: Minor


Some ideas for improvements to the document tasks feature:

(1) There should be a way to re-run a document tasks, with the option to include none/all/failed/unprocessed/failed+unprocessed docs. When choosing to re-run the user should again be taken through the document task creation wizard so that modifications can be made.
The implementation of this can be completely in the frontend, current backend APIs suffice.
There is one issue though: simple tasks are converted to, and stored as, a javascript, thus only administrators would be able to perform re-runs, which is not desirable.

(2) The current 'simple tasks' are cool but rather limited. An easier way to make this extensible would be to have a library of predefined, safe scripts, easily extensible by just dropping new scripts in some directory. The scripts should be able to take parameters though, this could be done by having some simple meta-description (possibly in a commented-out section at the top of the script) describing the parameters. The server could store a flag to indicate if a script was taken from the library or custom, which also solves the issue from improvement (1)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/site/services/daisy/daisysupport.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[JIRA] Updated: (DSY-458) Document tasks improvement ideas

by JIRA issues@cocoondev.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

     [ http://issues.cocoondev.org//browse/DSY-458?page=all ]

Bruno Dumon updated DSY-458:
----------------------------

    Component: Ext - document tasks

> Document tasks improvement ideas
> --------------------------------
>
>          Key: DSY-458
>          URL: http://issues.cocoondev.org//browse/DSY-458
>      Project: Daisy
>         Type: Improvement
>   Components: Ext - document tasks
>     Reporter: Bruno Dumon
>     Priority: Minor

>
> Some ideas for improvements to the document tasks feature:
> (1) There should be a way to re-run a document tasks, with the option to include none/all/failed/unprocessed/failed+unprocessed docs. When choosing to re-run the user should again be taken through the document task creation wizard so that modifications can be made.
> The implementation of this can be completely in the frontend, current backend APIs suffice.
> There is one issue though: simple tasks are converted to, and stored as, a javascript, thus only administrators would be able to perform re-runs, which is not desirable.
> (2) The current 'simple tasks' are cool but rather limited. An easier way to make this extensible would be to have a library of predefined, safe scripts, easily extensible by just dropping new scripts in some directory. The scripts should be able to take parameters though, this could be done by having some simple meta-description (possibly in a commented-out section at the top of the script) describing the parameters. The server could store a flag to indicate if a script was taken from the library or custom, which also solves the issue from improvement (1)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/site/services/daisy/daisysupport.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[JIRA] Commented: (DSY-458) Document tasks improvement ideas

by JIRA issues@cocoondev.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

    [ http://issues.cocoondev.org//browse/DSY-458?page=comments#action_13827 ]

Karel Vervaeke commented on DSY-458:
------------------------------------

The 'simple tasks' issue regarding is no longer a problem (the implementation still uses javascript internally, but the parameters are persisted as xml).

> Document tasks improvement ideas
> --------------------------------
>
>          Key: DSY-458
>          URL: http://issues.cocoondev.org//browse/DSY-458
>      Project: Daisy
>         Type: Improvement
>   Components: Ext - document tasks
>     Reporter: Bruno Dumon
>     Priority: Minor

>
> Some ideas for improvements to the document tasks feature:
> (1) There should be a way to re-run a document tasks, with the option to include none/all/failed/unprocessed/failed+unprocessed docs. When choosing to re-run the user should again be taken through the document task creation wizard so that modifications can be made.
> The implementation of this can be completely in the frontend, current backend APIs suffice.
> There is one issue though: simple tasks are converted to, and stored as, a javascript, thus only administrators would be able to perform re-runs, which is not desirable.
> (2) The current 'simple tasks' are cool but rather limited. An easier way to make this extensible would be to have a library of predefined, safe scripts, easily extensible by just dropping new scripts in some directory. The scripts should be able to take parameters though, this could be done by having some simple meta-description (possibly in a commented-out section at the top of the script) describing the parameters. The server could store a flag to indicate if a script was taken from the library or custom, which also solves the issue from improvement (1)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy