This depends on and effectively includes the following PRs:
1929
1933
1935
1936
The behavior of the case of None is treated as as synonymous with a NULL value for that field in the database. I've looked over the different use cases and have found that in some cases Unknown and Unassigned are used.
Make this None filter value customizable rather than hard-coding the opinion of None being NULL.
The app.filter.embargoTypeNone and app.filter.submissionTypeNone may now be changed to something other than None. The default remains set to None.
The following new application.yml settings are now introduced:
This depends on and effectively includes the following PRs:
1929
1933
1935
1936
The behavior of the case of
Noneis treated as as synonymous with a NULL value for that field in the database. I've looked over the different use cases and have found that in some casesUnknownandUnassignedare used.Make this
Nonefilter value customizable rather than hard-coding the opinion ofNonebeing NULL.The
app.filter.embargoTypeNoneandapp.filter.submissionTypeNonemay now be changed to something other thanNone. The default remains set toNone.The following new
application.ymlsettings are now introduced:Their respective environment variable names are: