Data Collection - Single view scrolling function

1 Requirements

It is necessary to navigate from one data collection entry to the next or previous without returning to the overview list of entries.

• The user interface should offer buttons for "Previous" and "Next". The current "Back" button to return to the overview needs to be renamed and integrated in this navigation concept.
  • Open question: the current overview of entries has no name. It is under the tab "Content" and has just a name for the table itself. Should we use the table name as button label or the general name "Overview"?
• It would be sufficient if this entry-to-entry navigation is restricted to the set of entries opened in the overview (like known from Mantis). If the number of rows per page is 20, a user can browse from entry 1 to 20. At entry 1 there is only a "Next" button, at entry 20 only a "Previous" button.
• The order of pages depends on the sorting a user has chosen for the table.
  • Additionally, we need to introduce a default sorting criteria to define the default appearance of a DC for new users.

2 Additional Information

• Funding: Universität Bern
• Maintainer: Martin Studer
• Development: Stefan Wanzenried, sr.solutions
• Tested by:

• If you want to know more about this feature, its implementation or funding, please contact: Martin Studer, sr.solutions

3 Discussion

Jour Fixe, 24 Jun 2013: We highly appreciate this improvement of the DC usability and schedule it for 4.4. Nevertheless, funding is needed for this feature to realise it for 4.4.

HL, 16.8.2013. Two suggestions:
 
a) Two subtabs in the content-tab: list-view and detail-view (similar to the test).
b) Implementation suggestion of the forward - backward buttons, see pic below. User interaction of Filemaker.

Matthias Kunkel, 25 Oct 2013: Feature postponed and unscheduled due to missing funding.

Martin Studer, 26 Nov 2013:

The current "Back" button to return to the overview needs to be renamed and integrated in this navigation concept.

We do not have an answer for this question. Does the JF has an answer?

Open question: the current overview of entries has no name. It is under the tab "Content" and has just a name for the table itself. Should we use the table name as button label or the general name "Overview"?

We do not have an answer for this question. Does the JF has an answer?

It would be sufficient if this entry-to-entry navigation is restricted to the set of entries opened in the overview (like known from Mantis). If the number of rows per page is 20, a user can browse from entry 1 to 20. At entry 1 there is only a "Next" button, at entry 20 only a "Previous" button.

In our opinion it is important to consider all records and take no consideration to the table paging. But we consider the table sorting.

Additionally, we need to introduce a default sorting criteria to define the default appearance of a DC for new users.

We have made a separate Feature Wiki Entry for this: Data Collection - Improved navigation through records

AK 1 Apr 2014: I would support the following

• Keep the name "Content" for the tab (since this is a general name used in other components as well). Using an additional Heading "Overview" would be ok for me.
• Name the "Back" link "Back to Overview"
• Name the navigation links "Previous" and "Next"
• Like Martin suggests, the pagination of the table should NOT limit the navigation view "Previous" and "Next"

Matthias Kunkel, 02 Apr 2014: I agree with Alexander's suggestions and schedule this feature for 4.5. Please add the "Status" information about contract, who will write test cases and who will test this feature.

4 Implementation

The user interface should offer buttons for "Previous" and "Next", The order of pages depends on the sorting a user has chosen for the table.