Feature Wiki
Tabs
DataCollection : Change Field Type from ’Integer’ to ’Numbers’
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 3 User Interface Modifications
- 4 Additional Information
- 4.1 Involved Authorities
- 4.2 Technical Aspects
- 4.3 Privacy
- 4.4 Security
- 4.5 Contact
- 4.6 Funding
- 5 Discussion
- 6 Implementation
- 6.1 Description and Screenshots
- 6.2 Test Cases
- 6.3 Privacy
- 6.4 Approval
1 Initial Problem
The current implementation only allows integers and is limited to 9 characters. This technological limitation is vastly oudated.
2 Conceptual Summary
Cases regularly occur in which both decimal numbers are to be used and larger numbers are to be used. New Field Type Label is 'Numbers'.
The previous limitations no longer apply. No problems are to be expected with the existing integers. For clarity: negative numbers are also allowed as before.
Fractions are still not allowed. The use of fractions must fall within the scope of the formula field. This could otherwise lead to problems if number fields are referenced in formula fields.
The Refinery (here Transformation kindlyTo->float()
) should be used to handle different separators such as commas and dots. This should ensure a standardised handling of the input of numerical values in ILIAS.
3 User Interface Modifications
3.1 List of Affected Views
- 'New Field' Form in 'Fields'-Tab of a Table of a Data Colletion
- Field Input of a new Entry
3.2 User Interface Details
The name of the Data Type of Field is changed. New Label for Field Type. Adaptation of the Byline.
3.3 New User Interface Concepts
None.
3.4 Accessibility Implications
The new input will allow a wider variety of correct inputs while fully including the current integer scope.
It might not support false inputs in the way it currently does.
This is just for annotation and no positive or negative assessment.
4 Additional Information
4.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Samoila, Oliver [oliver.samoila]
- Authority to Sign off Code Changes: Szmais, Ingmar [iszmais]
4.2 Technical Aspects
The values will be migrated to text within the database since the separate integer storage is no longer feasable, is deprecated and will soon be fully migrated aswell. This is part of a unifying process of the datacollection storage.
This has no impact on the usage.
4.3 Privacy
Nothing specific or new.
4.4 Security
The new implication will allow more inputs and can potentially cause injection based issue, even if very unlikely. To prevent that inside the core new restrictions in form of validations will be added.
However, we cannot guarantee for the handling within external software (plugins, etc.).
4.5 Contact
Person to be contacted in case of questions about the feature or for funding offers: Samoila, Oliver [oliver.samoila]
4.6 Funding
Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.
If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.
5 Discussion
JourFixe, ILIAS [jourfixe], 17 MAR 2025: We highly appreciate this suggestion and accept the feature for ILIAS 11. Please update the related test case(s) and give examples for allowed and not allowed number input.
6 Implementation
Feature has been implemented by {Please add related profile link of this person}
6.1 Description and Screenshots
{ Description of the final implementation and screenshots if possible. }
6.2 Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
6.3 Privacy
Information in privacy.md of component: updated at {date} by {user} | no change required
6.4 Approval
Approved at {date} by {user}.
Last edited: 17. Mar 2025, 15:03, Kunkel, Matthias [mkunkel]