The missing_required_file and missing_recommended_file notices are triggered when the file is not in the feed. This doesn't cover files with headers and no rows. Having a file in the feed with no data(only headers) defeats the intention of the required and recommended notices, as it doesn't encourage producers to add the data.
Solution Proposed
Add additional notices _required_file_empty_ and _recommended_file_empty_ (or a better name) to express that the files are present but have no rows.
Alternative Solution
We can also modify the required and recommended notice to catch files with no rows. The downside is that consumers can be confused when providing a file with no rows and getting missing required or recommended file.
Description
The
missing_required_fileandmissing_recommended_filenotices are triggered when the file is not in the feed. This doesn't cover files with headers and no rows. Having a file in the feed with no data(only headers) defeats the intention of the required and recommended notices, as it doesn't encourage producers to add the data.Solution Proposed
Add additional notices
_required_file_empty_and_recommended_file_empty_(or a better name) to express that the files are present but have no rows.Alternative Solution
We can also modify the required and recommended notice to catch files with no rows. The downside is that consumers can be confused when providing a file with no rows and getting missing required or recommended file.
Example fee, https://mobilitydatabase.org/feeds/mdb-1147