-
Notifications
You must be signed in to change notification settings - Fork 6
MC-1698: adding REST endpoint to admin corpus api for rejecting & unscheduling approved items for a domain #283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MC-1698: adding REST endpoint to admin corpus api for rejecting & unscheduling approved items for a domain #283
Conversation
…cheduling approved item for a domain
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one small improvement you could make, but not critical given the time frame.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one more verification in a test for removing the scheduled item, but otherwise this is looking good!
Goal
There has been a request to delete several approved corpus items and all related scheduled items for a domain.
Added a POST REST endpoint to the admin curated corpus api:
/admin/reject-approved-corpus-items-for-domain
:* takes in two params:
domainName
&testing
* if
testing
=false
, approved items for the domain are rejected/unscheduled* if
testing
=true
, the count of approved items found for the domain is returned* Example request body:
{ "domainName": "elpais.com", "testing": false }
admin/routes
rejectApprovedCorpusItemsForDomain
which takes in adomainName
&:User must have FULL access to execute this endpoint.
Deployment steps
References
JIRA ticket: