Change Details

When users navigate to the Edit List page by clicking the View Edit List link/button, they expect to see an Edit List. There is really no reason to navigate to the page otherwise. This ticket ensures that they will get what they expect. NOTE: This ticket relies on terms codified in T213136, which defines concepts and language related to the Updating and Downloading processes. Please make sure you have read T213136 before proceeding with this ticket. =Existing Edit List behavior Currently, when the user clicks the View Edit List button from the Event Summary page, she arrives at an Edit List page that displays no Edit List data (though Summary Data based on the last Update is displayed, along with the timestamp as of the last update). To see an Edit List, the user must click Update, upon which the system Updates and a new timestamp and new Summary figures are displayed, along with updated Edit List data. =Desired Edit List behavior - Edit List data is not stored. This means that Edit List data must be Fetched each time it is displayed (unless it was recently Fetched and is in cache). - Visiting the Edit List page will not trigger an Update. The results the user sees on visiting the page will be fetched based on page IDs from the previous Update. **When the user clicks to visit the Edit List page, **the following things will happen: - The user goes to the Edit List page. - The page displays stored Event Summary data at page top from the last update, as well as the timestamp as of the last update. - The system Fetches Edit List data based on page IDs from the last update BUT ONLY for a time period ending at the timestamp of the last update, as described in T213747. - During and after the Fetching process, the system displays the appropriate UI elements for the Fetch state, as described in T213470. - The system displays the first page of newly fetched Edit List data. **Pagination—each time the user clicks page navigation at bottom of the Edit List** to go back and forth among the pages of the Edit List, the process above repeats itself. I.e.: - No Update occurs; the timestamp and stored Summary Data don't change. - The requested page of edits is fetched, based on page IDs from the last Update and only for a time period ending at the last update (as described in T213747). - The system displays the appropriate UI elements during and after the Fetch state, as described in T213470. - The requested page of Fetched Edit List data is displayed.

When users navigate to the Edit List page by clicking the View Edit List link/button, they expect to see an Edit List. There is really no reason to navigate to the page otherwise. This ticket ensures that they will get what they expect. NOTE: This ticket relies on terms and concepts defined in T213136, which summarizes and codifies the Updating and Downloading processes. Please make sure you have read T213136 before proceeding with this ticket. =Existing Edit List behavior Currently, when the user clicks the View Edit List button from the Event Summary page, she arrives at an Edit List page that displays no Edit List data (though Summary Data based on the last Update is displayed, along with the timestamp as of the last update). To see an Edit List, the user must click Update, upon which the system Updates and a new timestamp and new Summary figures are displayed, along with updated Edit List data. =Desired Edit List behavior - Edit List data is not stored. This means that Edit List data must be Fetched each time it is displayed (unless it was recently Fetched and is in cache). - Visiting the Edit List page will not trigger an Update. The results the user sees on visiting the page will be fetched based on page IDs from the previous Update. **When the user clicks to visit the Edit List page, **the following things will happen: - The user goes to the Edit List page. - The page displays stored Event Summary data at page top from the last update, as well as the timestamp as of the last update. - The system Fetches Edit List data based on page IDs from the last update BUT ONLY for a time period ending at the timestamp of the last update, as described in T213747. - During and after the Fetching process, the system displays the appropriate UI elements for the Fetch state, as described in T213470. - The system displays the first page of newly fetched Edit List data. **Pagination—each time the user clicks page navigation at bottom of the Edit List** to go back and forth among the pages of the Edit List, the process above repeats itself. I.e.: - No Update occurs; the timestamp and stored Summary Data don't change. - The requested page of edits is fetched, based on page IDs from the last Update and only for a time period ending at the last update (as described in T213747). - The system displays the appropriate UI elements during and after the Fetch state, as described in T213470. - The requested page of Fetched Edit List data is displayed.

When users navigate to the Edit List page by clicking the View Edit List link/button, they expect to see an Edit List. There is really no reason to navigate to the page otherwise. This ticket ensures that they will get what they expect. NOTE: This ticket relies on terms codifiand concepts defined in T213136, which defines conceptsummarizes and language related tocodifies the Updating and Downloading processes. Please make sure you have read T213136 before proceeding with this ticket. =Existing Edit List behavior Currently, when the user clicks the View Edit List button from the Event Summary page, she arrives at an Edit List page that displays no Edit List data (though Summary Data based on the last Update is displayed, along with the timestamp as of the last update). To see an Edit List, the user must click Update, upon which the system Updates and a new timestamp and new Summary figures are displayed, along with updated Edit List data. =Desired Edit List behavior - Edit List data is not stored. This means that Edit List data must be Fetched each time it is displayed (unless it was recently Fetched and is in cache). - Visiting the Edit List page will not trigger an Update. The results the user sees on visiting the page will be fetched based on page IDs from the previous Update. **When the user clicks to visit the Edit List page, **the following things will happen: - The user goes to the Edit List page. - The page displays stored Event Summary data at page top from the last update, as well as the timestamp as of the last update. - The system Fetches Edit List data based on page IDs from the last update BUT ONLY for a time period ending at the timestamp of the last update, as described in T213747. - During and after the Fetching process, the system displays the appropriate UI elements for the Fetch state, as described in T213470. - The system displays the first page of newly fetched Edit List data. **Pagination—each time the user clicks page navigation at bottom of the Edit List** to go back and forth among the pages of the Edit List, the process above repeats itself. I.e.: - No Update occurs; the timestamp and stored Summary Data don't change. - The requested page of edits is fetched, based on page IDs from the last Update and only for a time period ending at the last update (as described in T213747). - The system displays the appropriate UI elements during and after the Fetch state, as described in T213470. - The requested page of Fetched Edit List data is displayed.