Project Idea

Taverna Mobile is for anyone who wants to create and run workflows, It basically shows workflow, developed by different people, this app is to give them a platform by which they can view, that is not at his desk. For instance, when visiting a conference he might hear about someone's workflow, which he can quickly locate and mark for later exploration. When in the biology lab, faced with updated scientific data, the user can rerun her own workflow with new inputs. While commuting, he can monitor the status of a long running job. 

Wishlist

  • Announcements Feature.
    The Jira Ticket :  https://issues.apache.org/jira/browse/TAVERNA-953
    Description : Announcements is the latest news, issued by the organisation, the user can view the latest news. it will be showed in the form of google cards. After on clicking the cards, the user can see the details in Material Dialog about the news, like who declare the news.
    Implementation : 1. Making UI for Announcement List.
    2. Making Retrofit Network Request in ApiManager and wiring with the DataManager.
    3. Network call in Announcement Presenter (Logic class) class and showing in RecyclerView.
    4. Making Announcement Material Dialog with google standard guide.
    5. Making Announcement Details Network call and parsing with UI.
    6. Making this Announcement feature offline.
    Reference PR : #PR
    Needed Discussion : REST API response is showing oldest to newest response in pagination hit. As an Example, if the                    
                                    user requests http://www.myexperiment.org/announcements.xml here then user got the response a list of Announcements in which old Accouncement is showing  first and newest than after.
    Suggestion: When the user requested the Announcement list, REST API should give the data in reverse order.
    Note : 1 to 5 is done. 6th will be implemented during the implementation of the Datahelper layer.

  • Code Analysis Tools Implementation.
    The JIRA Ticket : 
    Description : Code Analysis tools are those tools that checking the java standard  rule and warning to the user and some logical and generic warning will also be displayed. there are three types of tools we are using here.
    Implementation : 1. PMD : PMD is the source code analyser. It finds common programming flaws like unused variables, empty catch blocks, unnecessary objects creation and so forth.
    2. CheckStyle :  It ensures that Java Language Rules, Besides some static code analysis, it is used to show violations of a configured coding standard.
                                  3. FindBugs : This tool uses static analysis to find in java code. Unlike PMD, It uses compiled Java bytecode instead of source code.
    Reference PR : #PR.
    Note : 1 to 3 are implemented perfectly and Code Analysis tools analysing the code and building check pass if the all check passing.


  • [WIP] Redesigning the workflow showing method into app
    The JIRA Ticket : https://issues.apache.org/jira/browse/TAVERNA-947
    Implementation : 1. Making UI for WorkFlow Card UI.
                                  2. Making Retrofit Network Request in ApiManager and wiring with the DataManager.
                                  3. Network call in WorkFlows Presenter (Logic class) class and showing in RecyclerView.
                                  4. Making Workflow details UI.
                                  5. Making Workflow Details Network call and parsing with UI, when will click on the workflow.
                                  6. Making this WorkFlows feature offline.
    Reference PR : 
    Description : Currently Workflow card is showing the Author image and name, WorkFlow Title and a link to open in the browser. for Fetching, Author details developer needs to first fetch workflows 
                           list and then request for workflow details and then developer request for author details. As we are showing Workflows card this is bad practice for requesting REST API in the deep hierarchy. this thing creating the inconsistency in the fetched data in App.
    Needed Discussion : As the REST API designed workflows section. Application not showing in that manner. 
    Suggestion: Redesign the Workflows Card : Card will consist the Workflow Image and WorkFlow Title and Author Name and we can its type.

 

  • No labels

1 Comment

  1. Gale Naylor

    Hi Rajan Maurya,

    You are making good use of the wiki!

    In your introduction you say, "It basically shows workflow, developed by different people, this app is to give them a platform by which they can view, that is not at his desk." Will the mobile app show more than one workflow at a time? And, I presume it shows workflows not only developed by other people but also developed by the user? If I'm correct, maybe your sentence could be two sentences and read something like, "It basically shows workflows, developed by the user and others. This mobile app provides users the ability to view workflows away from their desks." (Or something like that.) (Also, I think you have a typo at the end of your first sentence: Taverna Mobile is for anyone who wants to create and run workflows. (It needs a period at the end.)

    I appreciate you mixing he/him and she/her in your descriptions. I think you can avoid the issue entirely by using "user." For example, you could say, "When in the biology lab, faced with updated scientific data, the user can rerun a workflow with new inputs." This approach would work for the rest of your introduction as well.

    Keep up the good work!

    Gale