This can be accomplished through a "non-blank" validator and the metadata validation code that I added.
On Tuesday, September 9, 2014 2:08:08 PM UTC-4, Roberto Rosario wrote: > > That is a great idea Gary and of the top of my head I don't think the > implementation would be too hard, thanks! > > On Saturday, September 6, 2014 9:51:22 AM UTC-4, Gary D Walborn wrote: >> >> I have been playing around with metadata types. I am looking for a way >> to make metadata required. For example, I can automatically add "Physician >> Name" to a document type, but I can't force the user to choose a valid >> physician. Even though there is a list which creates a drop-down menu, the >> user can just leave the value "-----" and the metadata remains blank. As a >> matter of fact, there is one change that would add HUGE functionality to >> the entire program. By adding a "validation" field to the metadata type >> (much like you have a "default" field), the user could provide a python >> function to validate what the user has entered (or chosen) for the metadata >> value. That would add tremendous power to the program. For example, >> validating that a field is a validly formed social security number, zip >> code, credit card number, etc., would be immensely helpful. >> >> Thanks, >> >> Gary W. >> >> -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
