Use a descriptive name in the UI to hide the cryptic record ID

[wcj365]

Issue: The cryptic record ID displayed on the UI is not user-friendly.

Suggested solution: Create a new required field "Submission Name" as part of the form and add it to the data entry screen.
Use Submission Name instead of record id for screen display.

Note: The submission does not need to be unique. The name collision is unlikely and even if it happens, it is ok since we have record ID to maintain uniqueness.

[janoskabedis]

I'm thinking that we give admins the power to collect display names / titles / summary from end users with a collect_submission_display_names or bulletin_title param for a form. This gives us the ability to keep the application generalizable, but also override the ObjectID unique identifiers which are not very user friendly. I agree that implementing this need not supplant the use of ObjectIDs under the surface, and as such these title's do not need to be checked for uniqueness.

When an admin enables collecting display names, should they be required? If not, is the default behavior to fall back to representing a submission by its ObjectID?