Feature Catalogue Template Attribute Element Cardinality Discrepancy

[esnyder-rve]

Describe the bug When selecting a pre-defined cardinality option for a feature catalogue's attribute element, the option 0..n populates the text field with the value 1..n instead.

To Reproduce Steps to reproduce the behavior:

1. Create a new feature catalogue
2. Go to the Elements section
3. For the Cardinalities field, choose the "Recommended Value" option of 0..n
4. Text field populates with 1..n instead

Expected behavior Field should populate with 0..n

Screenshots

Log file N/A

Desktop (please complete the following information):

• Browser: Vivaldi
• GeoNetwork Version: 4.4.6
• Server Application: Docker container (image: geonetwork:latest)

Additional context N/A