I agree with Mr. Bunyan in that Microsoft did not look at user behavior when designing library functionality. And this whole thing is a much more complex issue than just saying, “Oh, well, SharePoint provides for all this metadata in the various fields, so just do it.”

For one, many organizations ENFORCE file-naming conventions, so just saying “convert to SharePoint’s way of thinking” will not work. In addition, many users are moving FROM some other file-storage scheme (file servers, document management systems, hard drives) and INTO SharePoint, and they often move many many documents at once. The users I’ve worked with just want SharePoint to do its job so they can go about theirs. It’s an unnecessary (in their minds) imposition on their “real jobs” that they should have to unpack the metadata from the filename and into several new SharePoint metadata fields.

OOB document library does not have the columns for author and document date, which can be identified as ‘required’ by examining business functions and requirements, and applied accrodingly.