Batch Importer (Bib/Acq)
(UXPROD-47)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Lotus (R1 2022) | Parent: | Batch Importer (Bib/Acq) |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Ann-Marie Breaux (Inactive) | Assignee: | Ann-Marie Breaux (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | data-import, epam-folijet, optimistic_locking | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||
| Release: | Lotus R1 2022 | ||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Batch Importer (Bib/Acq) | ||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | Small < 3 days | ||||||||||||||||||||||||||||||||||||||||
| Development Team: | Folijet | ||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 112 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Description |
|
NOTE: This feature assesses how much impact the Inventory Optimistic Locking work has on Data Import. If any UI changes are needed (for the Data Import log or error messages in the UI), then a follow-on feature for Lotus will be added Current situation or problem: Inventory is implementing Optimistic locking in Kiwi. Folijet needs to review and determine how Data Import and SRS may be affected. There are already conflicts when 2 processes, or a person and a process are acting on the same record at the same time. Currently, one set of changes is discarded silently, with no error messages or UI indication.
FOLIO-wide technical proposal: https://folio-org.atlassian.net/wiki/display/DD/Optimistic+locking+proposal In scope
Out of scope
Use case(s)
Possible use cases (validate with Kate and Ivan; maybe consolidate with above)
Proposed solution/stories Links to additional info
Questions |
| Comments |
| Comment by Ann-Marie Breaux (Inactive) [ 10/Aug/21 ] |
|
Hi Debra Howell and Tom Wilson I see that you've marked this as P1, and I think it's totally appropriate. We're hoping to work on this in Kiwi, and we have a placeholder for it, but we don't have any clear user stories for UI or backend requirements. I'm hoping that we'll be able to start filling in these details in the next few weeks. So all of that to say - stay tuned! |
| Comment by Ann-Marie Breaux (Inactive) [ 12/Aug/21 ] |
|
Next steps in defining this feature:
|
| Comment by Ann-Marie Breaux (Inactive) [ 25/Aug/21 ] |
|
Grooming: for Kiwi focus on unblocking the problems when Julian merges existing changes. Will need to test DI performance before and after the merge. If any problems with versioning, then the job will be completed with errors. Next steps: Kateryna Senchenko to write the BE stories and Vladimir Shalaev to review If a record is being used, then we will end up with "discarded" on the summary page. Once DI can accept OL errors, try and see if we can trigger the error. Then meet with Ivan and Kimie to discuss UI options, which may need to be in Lotus. |
| Comment by Ann-Marie Breaux (Inactive) [ 01/Sep/21 ] |
|
Grooming:
|
| Comment by Ann-Marie Breaux (Inactive) [ 22/Nov/21 ] |
|
Hi Martin Tran Just wanted to check on whether
|
| Comment by Martin Tran [ 22/Nov/21 ] |
|
Hi Ann-Marie Breaux, yes, the PTF can test DI with/without OL in the next couple of weeks. |