Use Consistent Terminology Regarding Documents, Files, Messages, and Submissions #6543
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Status
Ready for review
Description of Changes
Fixes #2421 and fixes #6173
Changes proposed in this pull request:
This updates the remaining user-facing references from 'Documents' to either 'Files' or 'Submissions,' depending on the given use-case. In a previous meeting we mentioned using 'Submission' for everything, but in practice I discovered that is not feasible. That's because 'Submission' includes both files and messages, but there are instances where it's necessary to specify between files and messages. This change eliminates the usage of 'Documents,' and adds consistency to the work that has already been done more recently.
Testing
This can be tested by building according to the steps in the README.
Deployment
This will require new translations.
Side-note, is it necessary here to run
make translate
to update the translation files, or does that happen after the fact?Checklist
If you made changes to the server application code:
make lint
) and tests (make test
) pass in the development containerChoose one of the following:
Just to note, normally these changes would require documentation updates, but it appears that the newer terminology has already made it into the product for all the user-facing strings shown in the documentation. I have gone through the source and journalist guides, and do not see any outdated strings that would need to be replaced.