Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
Gulfstream Sprint 95, Gulfstream Sprint 96
-
8
-
Gulfstream
Description
Purpose:
This is a second step in creating/editing OAI-PMH set - adding/changing records filtering conditions in set.
User story statement:
As a system administrator,
I want to be able to create/edit OAI-PMH set with filtering conditions
so that selective harvesting was configurable
Scenarios:
1. Scenario - Open set creation/modification page
- Given user has permissions to edit OAI-PMH settings
- When user opens the page for set creation/modification
- Then both "General information" and "Set filtering conditions" sections are displayed
- And "General information" section includes auto-generated SetSpec (empty by default)
- And "Set filtering conditions" section includes the next fields: Location, Resource type, Format, ILL Policy, Material type
(see)
2. Scenario - Activate filtering condition
- Given "Set filtering conditions" is displayed
- When user checks "Active" checkbox against one of the filtering condition
- Then next fields become enabled:
Name | Type | Description |
---|---|---|
Value | Dropdown | List of Values which depends on filtering condition Field. Should have empty option by default |
Set spec | Text field | Part of the result setSpec. Should be pre-filled with generated value by default |
3. Scenario - Pre-filling set spec generation
- Given Set filtering condition is activated
- When user chooses specific value
- Then set spec is generated using next rules:
Field name | Set spec generation rule |
---|---|
Location | "Loc_"+ first 3 letters from the Value if it consists of one word OR first letters from each word in Value if it consists of more than one word |
Resource type | "RT_" + first 3 letters from the Value if it consists of one word OR first letters from each word in Value if it consists of more than one word |
Format | "Ft_" + first 3 letters from the Value if it consists of one word OR first letters from each word in Value if it consists of more than one word |
ILL Policy | "ILL_" + first 3 letters from the Value if it consists of one word OR first letters from each word in Value if it consists of more than one word |
Material type | "MT_" + first 3 letters from the Value if it consists of one word OR first letters from each word in Value if it consists of more than one word |
4. Scenario - Deactivate filtering condition
- Given "Set filtering conditions" is displayed
- And "Active" checkbox against the filtering condition is checked
- When user unchecks this "Active" checkbox
- Then Value and Set spec fields are cleared
- And Value and Set spec fields become disabled
5. Scenario - Result setSpec generation
- Given user creates or edits a set
- When user clicks "Save" button
- Then setSpec values from each filtering condition are gathered into one string delimited by a colon to generate result setSpec
6. Scenario - Outdated values in set filtering condition
- Given value (e.g. one of the locations) from set filtering condition was removed from the system
- When user opens the page for set modification
- Then removed value is empty
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-2406 Implement sets CRUD for OAI-PMH - frontend work
-
- Closed
-
- relates to
-
UIOAIPMH-5 Create/edit OAI-PMH set with general information
-
- Closed
-
-
MODOAIPMH-201 Enrich sets endpoints with filtering conditions entites.
-
- Closed
-
-
UIOAIPMH-12 Validate set creation or change
-
- Closed
-
-
UIOAIPMH-18 Validate set uniqueness
-
- Closed
-
- requires
-
MODOAIPMH-210 Implement endpoint for getting values of all required filtering condition types.
-
- Closed
-