Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
Gulfstream Sprint 94
-
3
-
Gulfstream
Description
Purpose:
Ability to delete unnecessary or obsolete sets in case it's filtering conditions aren't required anymore or become deprecated.
User story statement:
As a system administrator,
I want to be able to delete OAI-PMH sets
so that redundant sets weren't stored in the system
Scenarios:
1. Scenario - Delete set
- Given user has permissions to edit OAI-PMH settings
- When user selects set from the list
- And clicks "Actions"=>"Delete" button
- Then confirmation message "Delete <set_name> set?" appears
- And after clicking "Delete" button selected set is physically removed from the system
- And the message "Set was successfully deleted" is shown.
2. Scenario - Set deletion fail (module issues)
- Given user has permissions to edit OAI-PMH settings
- And there are some issues on the back-end side
- When user confirms set deletion
- Then set isn't deleted in FOLIO
- And message "Unable to delete due to a module error. Please try again. If a problem persists please contact your system administrator." is shown
3. Scenario - Set deletion fail (delete issues)
- Given user has permissions to edit OAI-PMH settings
- When user confirms set deletion
- And set can't be deleted for some reason (e.g. set has been already deleted)
- Then the message "Failed to delete a set." is shown
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-2406 Implement sets CRUD for OAI-PMH - frontend work
-
- Closed
-
- requires
-
MODOAIPMH-199 Implement the endpoint for deleting set by id
-
- Closed
-