nus-pe-script
commented
2 months ago Team's Response
As mentioned in the UG, blank headlines are allowed for users to quickly start drafts even if they have not come up with a viable headline.
By the intended use, users should only be searching for non blank headlines using find -a.
Instead of using find -a for draft articles with blank headlines, users can instead use commands like filter -a s/DRAFT t/ st/ en/ to view their drafts and find the article with an empty headline from there. Users are not expected in real use to have that many drafts, especially with blank headlines, at any point in time, making it relatively easy to find articles entered with empty headlines. Other fields like tags, contributors and interviewees or date can also be used to find articles with empty headlines.
For articles with blank headlines accidentally marked as published, only one article can have such an issue at any point (due to duplicate detection) making using the filter -a s/PUBLISHED t/ st/ en/ command and identifying the erroneous article easy.
Ultimately, find -a was specified as requiring a keyword in the User Guide due to the presence of other simple workflows to identify and edit articles with empty headlines in its place.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
I think that since articles which are draft's can have no headline, perhaps the find -a command should also accomodate users to search for these draft's