All work
- Story - Lookups - drop down lists for Work componentsUILD-229Resolved issue: UILD-229Siarhei Karol
- STORY: Base component Instance entityUILD-224Siarhei Karol
- Story: Creator and Contributor of Work - Use new API contractUILD-222Resolved issue: UILD-222Doug Loynes
- Story: Edit form - Work block (Part 1) | WireframeUILD-218Resolved issue: UILD-218Doug Loynes
- Story - Lookups - drop down lists for Instance and Work componentsUILD-209Resolved issue: UILD-209Doug Loynes
- Story: Edit form - Instance block | WireframeUILD-201Resolved issue: UILD-201Doug Loynes
- Story: Title Advanced Search FE (Happy Path) | BF Thin ThreadUILD-115Resolved issue: UILD-115Doug Loynes
- STORY: Repeatable fields Instance entity | BF Thin ThreadUILD-94Resolved issue: UILD-94Doug Loynes
- Story: Title Search Box | BF Thin ThreadUILD-81Resolved issue: UILD-81Doug Loynes
- Story: Title Basic Searching FE (Happy Path) | BF Thin ThreadUILD-80Resolved issue: UILD-80Doug Loynes
- Story: Search results first column | BF Thin ThreadUILD-75Resolved issue: UILD-75Doug Loynes
- Resource Description - Comparison | BF Thin ThreadUILD-65Resolved issue: UILD-65Doug Loynes
- Story: Naming convention | BF CatalogingUILD-61Resolved issue: UILD-61Doug Loynes
- Jest/RTL Unit Tests for src/views/EditUILD-51Resolved issue: UILD-51Nikolai_Litvinenko
- Story: Derive marc 245 from Title & Work resource descriptionMODLD-326Resolved issue: MODLD-326Punnoose Kutty Jacob Pullolickal
- Story: Update API to support title of workMODLD-323Resolved issue: MODLD-323Doug Loynes
- Story: Update API to support genre/FormMODLD-278Resolved issue: MODLD-278Doug Loynes
- Story: Update API to support targetAudienceMODLD-277Resolved issue: MODLD-277Askhat Abishev
- Story[Marc2BF]: Convert marc field 008, char 22 to "targetAudience" edge of WorkMODLD-276Resolved issue: MODLD-276Doug Loynes
- Story[Marc4LD]: align Instance<->Work relations with new Marva APIMODLD-275Resolved issue: MODLD-275Pavel Bobylev
- Update API contract for creator & contributor of WorkMODLD-274Resolved issue: MODLD-274Doug Loynes
- SPIKE: Merging graphs - Merge edges of two graphs to form the resulting graphMODLD-261Resolved issue: MODLD-261Pavel Bobylev
- Identify the properties to be used for fingerprintingMODLD-252Resolved issue: MODLD-252Punnoose Kutty Jacob Pullolickal
- Story: API geographic coverage fieldMODLD-241Resolved issue: MODLD-241Doug Loynes
- Story: Java Library for fingerprinting resource descriptionsMODLD-143Resolved issue: MODLD-143Pavel Bobylev
- Story: Contributor Indexing BE | BF Thin ThreadMODLD-112Resolved issue: MODLD-112Doug Loynes
- ETL: Switch to HTTPS-based builds using .netrcMODLD-111Resolved issue: MODLD-111Punnoose Kutty Jacob Pullolickal
- Story [BE]: Create mapping document for "marc" --> "bibframe lite" --> "bibframe 2.0" conversionMODLD-108Resolved issue: MODLD-108Punnoose Kutty Jacob Pullolickal
- [BE] Make mod-linked-data read ETL result data (part 1)MODLD-107Resolved issue: MODLD-107Pavel Bobylev
- Convert Instance records from MARC to BIBFRAME in ETLMODLD-90Resolved issue: MODLD-90Pavel Bobylev
- Story: Title Indexing for Advanced Search BE | BF Thin ThreadMODLD-89Resolved issue: MODLD-89Doug Loynes
- Instance record - part 3MODFQMMGR-171Resolved issue: MODFQMMGR-171Khalilah Gambrell
32 of 32
Story - Lookups - drop down lists for Work components
Duplicate
Description
Environment
None
Potential Workaround
None
Checklist
hideDetails
Assignee
Siarhei KarolSiarhei KarolReporter
Doug LoynesDoug LoynesPriority
TBDStory Points
3Development Team
CitationTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Siarhei Karol
Siarhei KarolReporter
Doug Loynes
Doug LoynesPriority
Story Points
3
Development Team
Citation
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created March 13, 2024 at 12:23 AM
Updated June 12, 2024 at 4:28 PM
Resolved June 12, 2024 at 4:28 PM
Activity
Show:
Doug LoynesJune 12, 2024 at 4:28 PM
Drop down functionality completed with other tickets and deployed as part of the Alpha release.
As a cataloger, I need the ability to select values from drop down lists when in edit mode for the Work entity.
In scope
The Work entity components with drop down menus include:
Assigning Agency
Content Type
Government Publication
Intended Audience
Language Code
Note Type
Place of Origin of the Work
Relationship Designator
Addtionally, the simple action buttons (save & keep, save & close, cancel) are operational with respect to the drop down components of the Work entity
Selecting multiple values from a drop down
Removing / deleting a value selected from a drop down
Out of scope
Drop down components for Instance entity
Toast and warning messages associated with action buttons
Drop down menus were initially supported with the Thin Thread release in December
As we incorporate wireframe designs into the interface, we will need to add this functionality back into the interface to support cataloging workflows.
Each of the components listed above has a corresponding list of controlled terms that should be compiled and displayed alphabetically in each drop down menu.
1. Base case
GIVEN that a cataloger is editing a Work entity
WHEN the Work edit mode screen is displayed
THEN the labels for each of the components from the list above are included in the display
AND corresponding drop down functions are displayed and actionable (e.g. not greyed out)
AND the action buttons (Save & keep, Save & close, Cancel) are displayed and actionable
2. Drop down functionality
GIVEN scenario 1
WHEN the cataloger selects the drop down function for each of the components listed above
THEN the drop down menu displays the corresponding values specific for that component, with the values listed alphabetically
3. Select drop down functionality
GIVEN scenario 2
WHEN the cataloger selects / highlights a value from the drop down menu
THEN the selected value is displayed in the form
4. Save & keep
GIVEN scenario 3
WHEN the cataloger selects Save & keep
THEN the edits made through the drop down menu are saved locally
AND the cataloger remains in edit mode for the Work entity
5. Save & close
GIVEN scenario 3
WHEN the cataloger selects Save & close
THEN the edits made through the drop down menu are saved to the back end database
AND the edit mode closes
AND the home screen for the MARVA editor displays
6. Cancel
GIVEN scenario 3
WHEN the cataloger selects Cancel
THEN none of the edits performed using drop down menus are saved to the back end database
AND the edit mode closes
AND the home screen for teh MARVA editor displays