|
By Wensday - Monday, May 9, 2016
|
Permanent ID field should, at least, accept more special characters than just underscore. Allowing slashes, periods, dashes, and spaces would allow users to hand enter per any of several standard numbering systems.
An automated numbering system with user selected formatting would be even better.
|
|
By GenoProSupport - Thursday, May 12, 2016
|
|
Great suggestion.
|
|
By V.L.o - Thursday, June 16, 2016
|
|
I concur with suggestion, but only standardized system of permanent ID's can be used at least in single system - in single file with strict rules for transfer to other systems or use of strictly pre-defined systems.
I work with databases with lot of data imported from previous systems and inputs were done by few dozen people over course of 30 years. After automatized clean up of inconsistent data every day or so I stumble upon a case that needs almost full rebuild of data.
Fields were free text input or had some data input restrictions and data control mechanisms but insufficient ones.
To cut to the case - Permanent ID might be customizable but only up to a point, and there should be a rule how far this customization can go, otherwise there should be an Permanent ID's Unique ID generated...
|
|