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".

Requirements

1. Renaming a system field locally in a schema is out of scope of this idea.

2. System fields supported shall include but not be limited to:

   1. Name

   2. Description

   3. Type

   4. Version Number

3. We should ensure that when system fields are renamed, it is clear to users and support what their original name was. (E.g. an indicator or on hover or something similar.)

   1. In the end user interface - e.g. when seeing the document "name" in a listing.

   2. In the schema configuration admin interface.

4. Action names such as "Edit Type", "Edit Description", and "Rename" need to be handled appropriately.

5. If the following are simple we should consider them - but if they are difficult we should consider a compromise solution:

   1. KLANG (Keyword Language) supports system field names such as name or description. These need to be handled appropriately. (Either we don't support custom system field names and require the original names to be used or we do support the custom names.)

   2. Do we need API support? E.g. for Workflow and Sync? Or shall we require that these use the underlying "official" names?

      1. If we are mapping Type into a metadata field, it might be key to know that "Type" is actually "Form".

   3. Referencing system fields in auto-filing, auto-tagging, or naming conventions should use the official names.

6. Supporting language variants of names for System, global, and local metadata fields can be found here: BCDECORE-E-423. I.e. this is out of scope for this enhancement.