As a schema designer I want to be able to use the same metadata field across multiple languages to allow for a single schema to deliver for global users. This needs to include: System metadata fields Global metadata fields Local metadata fields

As a schema designer I want to be able to define an enumerated metadata field (single select drop down/multi-select drop down/taxonomy) that supports multiple languages - i.e. one value per language to reduce administrative overheads around schema...

As a customer I want to be able to rename all system metadata fields (globally) to my chosen term. E.g. As a customer I want to be able to rename the "version number" system field to "revision number". E.g. ISO19650 now refers to "Type" as "Form"....

As a role admin I want to be able to use one set of roles across multiple languages. Each role will need to be able to store a translation for the role name in each language. The correct role name will need to display according to the user's langu...

As a schema admin I want to be able to define multiple language strings for field sets/reasons for issue to support defining a single schema that works globally. As a schema admin I want to be able to define a logical order for the field sets - be...

As a user in the USA I want to be able to use mm/dd/yyyy dates and the 12 hour clock. As a user I want to be able to use the global standard (ISO 8601) of YYYY-MM-DD for dates. Notes Where dates and times are shown, they should be rendered in th...

As a schema designer I want to be able to use Issue Categories across multiple languages. Each issue category should be able to store a translation for each supported language. The language string shown when displaying issue categories - i.e. in m...