Maybe I’m looking too much at this as a simple (non-advanced) user.
So here it is …
When I see the word Documented by, it first conveys to mind the work on the document. In other words, each user can commit any actions on the document based on the permissions granted.
Review refers not to a document but to actions on an article or a review. As far as I’m concerned, it overlaps with the Blog application (which I’ll mention here more than once).
There are no questions regarding visualization. The question is small in functionality and binding. For example, if the point is to display the last 5 unique authors, then this duplicates the History tab, which provides more information (ideally when a summary is also specified). Let’s assume a situation where this tab is disabled visually, and the URL processing file is configured to block access. Then, it will be nothing but a Blog where only the owner or a specific group will have all the information. Ordinary visitors/readers will see Documented by. This could be an improvement or a new feature to the existing Blog application.
The very last word Documented by is confusing because, at the сore level of the platform, users edit documents through Edit, and therefore the result is a document modified by.
OMV, the further introduction or discussion of this field has 3 ways:
- This field is disabled by default (to prevent the display of such field for code documents that are hidden). And can be enabled from page display settings
- Show by default and replace Last modified by, which is the removed field after title of document.
- Only add as an improvement to an existing extension