Publication date ranges should not support formats "null/YEAR-MM/YEAR" or "MM/YEAR-null/YEAR"
[Provide a general summary of the issue in the title above]
Expected behaviour
Check comment here and issue #1216 (closed)
Current behaviour
The user is allowed to save the Metadata of the collection or a chapter-processed book if the Publication date is a range in these formats:
-
null/YEAR-MM/YEAR
the user should not be able to save and the error message should be "If a closing month for the range is provided, a start month must be provided too." -
MM/YEAR-null/YEAR
the user should not be able to save and the error message should be "If a start month for the range is provided, a closing month must be provided too."
Steps to reproduce
- Open a collection or a chapter-processed book
- Click on the Metadata
- Fill in all the required fields and choose Print publication range or Electronic publication range
- Fill in the date in one of these formats: "null/YEAR-MM/YEAR" or "MM/YEAR-null/YEAR" and save
Environment
[Provide browser name and version and if you're working from a PC or Mac]
Possible solution
[Not required. Suggest a fix for the bug]
NCBI's priority feedback
[Select "Y" or "N" and provide an explanation]
- This bug is blocking NCBI's work on migration planning for deployment 1 (Y/N)
- This can be prioritised after deployment 1 (Y/N)
QA Steps
- Open a collection or a chapter-processed book
- Click on the Metadata
- Fill in all the required fields and choose Print publication range or Electronic publication range
- Fill in the date in one of these formats: "null/YEAR-MM/YEAR" or "MM/YEAR-null/YEAR" and save
- Notice that you are not able to save metadata and the validation error is shown.
The current validation error messages are described in this google spreadsheep in "Current Behavior for Publication Ranges" sheet.