All work
- Requirements Analysis : Re-Order Item Records via APIPOT-23Christine Schultz-Richert
- Refinement and QA for UXPROD-5265POT-24Oleksandr Hrusha
- QA work for UXPROD-5265 (ECS with mod-tlr enabled (Eureka) - Support for requesting Items without barcodes)POT-22Resolved issue: POT-22
- Requirements analysis: Add columns to instance classification browsePOT-21Resolved issue: POT-21Christine Schultz-Richert
- Analyze and refine ability to sort receiving pieces on chronologyPOT-20Joseph Reimers
- Requirements Analysis : Adding item sorting supportPOT-19Resolved issue: POT-19Christine Schultz-Richert
- Analysis: UXPROD-2733: Override non-requester checkoutPOT-18Thomas Trutt
- Analysis: Requesting items with barcodePOT-17Resolved issue: POT-17Anne Ekblad
- Completing Stories for UXPROD-5187POT-16Resolved issue: POT-16Dennis Bridges
- Create and size user stories for UXPROD-4883POT-15Joseph Reimers
- Story splitting for UXPROD-5077POT-12Resolved issue: POT-12Irina Pokhylets
- Aggregating UAT feedback for summary document and story creation.POT-11Resolved issue: POT-11
- Build UAT documentation for testing Organization record historyPOT-10Resolved issue: POT-10Dennis Bridges
- Continued - Requirements analysis - User preferences and Save as you go supportPOT-9Resolved issue: POT-9
- Story splitting for filter implementationPOT-8Resolved issue: POT-8Irina Pokhylets
- Feature requirement analysisPOT-7Resolved issue: POT-7Irina Pokhylets
- Continued - Requirements analysis - User preferences and Save as you go supportPOT-6Resolved issue: POT-6
- Organizing LOC-TO2 acq requirementsPOT-4Joseph Reimers
- Create refinement documents for TO2 featuresPOT-3Resolved issue: POT-3Joseph Reimers
- Refine "Alternate exchange rate" requirementPOT-2Joseph Reimers
- Requirements analysis - User preferences and Save as you go supportPOT-5Resolved issue: POT-5
- Refine “Save-as-you-go Order records” requirementPOT-1Resolved issue: POT-1Joseph Reimers
22 of 22
Requirements Analysis : Re-Order Item Records via API
Description
clones
Checklist
hideDetails
Labels
Assignee
Christine Schultz-RichertChristine Schultz-RichertReporter
Harry RumbleHarry RumbleStory Points
3Priority
P3Sprint
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Labels
Assignee
Christine Schultz-Richert
Christine Schultz-RichertReporter
Harry Rumble
Harry RumbleStory Points
3
Priority
Sprint
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created 20 hours ago
Updated 20 hours ago
Activity
Show:
Harry Rumble20 hours ago
@Christine Schultz-Richert closed https://folio-org.atlassian.net/browse/POT-19 that was initial https://folio-org.atlassian.net/browse/UXPROD-1625 for this request, edited the descriptiotn fro https://folio-org.atlassian.net/browse/UXPROD-5257 and assigned 3 story points to start
Summary: LOC wants a field that allows a library to see default sort order. They want an itemsort order ID that allows them to preserve the item sort order they have with Voyager. They want that order reflected in the edge-rtac response too so that it displays as expected on Locate.
Task supports gathering requirements
Adding the sortID how to pass it to edge-rtac. How to prevent impact to FOLIO UI?
How can libraries preserve the current default item display order?
Is there any value in allowing libraries to set default item display order based on barcode? Or other fields?
Migration and release upgrade handling
Update https://folio-org.atlassian.net/browse/UXPROD-1625 based on requirements analysis.
Requirements:
Add a numeric sort order field to the item record
Do we need to expose this field on the UI?
For existing items: Populate numeric sort order field with current sort (Barcode)
For newly created items, increment the sort order field
Allow for libraries to change the sort order (numeric value) via API
No validation needed for deduplication
No UI mechanism to re-sort needed for this current implementation; will be handled in UXPROD-1625: Re-order Item records
Draft
Add sort order to the RTAC response
Mapping
Upon migration, allow for libraries to map sort order values from previous system to FOLIO
Definition of done: Confirm requirements with LOC before getting high-level estimates.