Summary: | ERM > Titles > Import from a list needs a full page reload to get the up to date lists | ||
---|---|---|---|
Product: | Koha | Reporter: | Victor Grousset/tuxayo <victor> |
Component: | ERM | Assignee: | Jonathan Druart <jonathan.druart> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P5 - low | CC: | jonathan.druart, jonathan.field, martin.renvoize, matt.blenkinsop, pedro.amorim |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Victor Grousset/tuxayo
2023-11-26 23:06:28 UTC
> 3. in another tab, create a new list
And add records. Even though an empty list is visible with a full reload.
Yes, data are loaded when the app is mounted. That's "expected". Not a bug for me, we don't want to fetch all the data the app needs every time we go to a new view. (In reply to Jonathan Druart from comment #2) > Yes, data are loaded when the app is mounted. That's "expected". Not a bug > for me, we don't want to fetch all the data the app needs every time we go > to a new view. Even with that being the case, it's still a confusing experience for the user! (In reply to Pedro Amorim from comment #3) > (In reply to Jonathan Druart from comment #2) > > Yes, data are loaded when the app is mounted. That's "expected". Not a bug > > for me, we don't want to fetch all the data the app needs every time we go > > to a new view. > > Even with that being the case, it's still a confusing experience for the > user! We "just" need a route for lists. Bug 28965 (but maybe not enough). (In reply to Jonathan Druart from comment #2) > we don't want to fetch all the data the app needs every time we go > to a new view. It wasn't about all data. (In reply to Pedro Amorim from comment #3) > Even with that being the case, it's still a confusing experience for the > user! Indeed, no data consistency with the chronological order of page navigation (not sure about the phrasing ^^") even if it's on different tabs should be considered a bug. I think the only close thing to an exception are stuff when there are like tabs when editing a record or a framework subfield. The UI is in-page tabs, it's not perceived as going to another page, it's the same functional page. And there is no important external data loaded there. Inside the ERM it's completely different pages functionally and some display data from other part of Koha that might be updated in the meantime. Here the workflow make it likely part of the time to go create a list in another tab, before being in the right page in the ERM. Whereas the record editor being the same page functionally, it's not expected to have the framework fields refreshed by switching between tabs. So one would refresh the page. The same for the ERM if being already on ERM > Titles > "Import from a list" before going to create the list elsewhere. There, it's expected to refresh the page. (In reply to Jonathan Druart from comment #4) > We "just" need a route for lists. Bug 28965 (but maybe not enough). Great. The important was to have a ticket here documenting the behavior and being known if patches are accepted. If no users with a support contract or in-house dev capabilities ever triggers the making of a fix, it's okay. So many fishes for so few frying pans ^^ |