The basic scenario is the basic process. Test data resembles (almost) up-to-date real data. It ensures the availability and quality of the data at the given times.
Depending on the requirements, which are quite different across industries and the usage of the corresponding platforms, it could be necessary to tailor the test data in specific ways.
The content-less scenario may have the same requirements in terms of time and scope of documents but the content files should not be recreated. That means that the test system shows the documents and their attributes but not the actual content file.
Either it is simply not necessary to also have the content file for the tests or it is strictly forbidden e.g. the test or dev system allows access for more or other people than the productive system and confidential content is involved.
In other cases, the document’s attributes must be concealed or blackened for the same reasons (confidential, security) or in general the test data should be created in a tailored scenario. Here the test data contains only the necessary subset of original information and certain values can be disguised.