Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DIS-219: Filter Hold Requests #2216

Conversation

AlexanderBlanchardAC and others added 7 commits January 28, 2025 09:37
Add the ability to filter holds by excluding those of selected linked
users and by displaying only selected holds in the UI.
Update exportHolds so that the new filters are taken into account when
holds are exported.
Prevent disply selected filter from filtering out linked users if they
are highlighted in the ui
When records are selected and display selected is applied, records were
being returned if they had the same record id as a selected record e.g.
they had a different user, but were not selected themseleves, this patch
adds a check for the userid to prevent this
Copy link
Member

@mdnoble73 mdnoble73 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you fix release notes? Also the name of the Pull Request should be DIS-219 Filter hold requests with the dash so that Jira can link properly.

Thanks

@@ -125,6 +125,9 @@
- Eliminate the time portion of display dates from Aspen Open Archives search results (DIS-242) (*JStaub*)

//alexander
### Holds Updates
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AlexanderBlanchardAC this needs the ticket number in parenthesis before your initials for each change.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry Mark, missed that. Updated the release notes.

@AlexanderBlanchardAC AlexanderBlanchardAC changed the title Dis 219 filter hold requests DIS-219: Filter Hold Requests Jan 29, 2025
Copy link
Member

@mdnoble73 mdnoble73 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Alexander,
This development does not follow the design patterns that are already established within Aspen with regards to Linked Accounts. In other locations we have the ability to select the active Linked User or all are shown. This type of filter should follow that pattern.

The input to seelect which user to select should be above the tabs (Libby, Boundless, Physical, etc). so that it applies to all tabs without the user having to reselect as they move between tabs and so they don't need to set it for available vs. pending separately.

This functionality should also be included in checked out titles for consistency.

Let me know if you have questions or want to discuss more.

  • Mark

@AlexanderBlanchardAC
Copy link
Contributor Author

Hi Alexander, This development does not follow the design patterns that are already established within Aspen with regards to Linked Accounts. In other locations we have the ability to select the active Linked User or all are shown. This type of filter should follow that pattern.

The input to seelect which user to select should be above the tabs (Libby, Boundless, Physical, etc). so that it applies to all tabs without the user having to reselect as they move between tabs and so they don't need to set it for available vs. pending separately.

This functionality should also be included in checked out titles for consistency.

Let me know if you have questions or want to discuss more.

  • Mark

Hi Mark,
Please could I have an example of where we filter by linked users so I know what I am aiming at?
Thanks,
Alexander

@mdnoble73
Copy link
Member

Look for cases that use the switch-linked-user-form.tpl template. It looks like we deprecated most of those cases, but that allows the user to change back and forth between which account is active. By default you would want to show all accounts so you would likely need to extend the template to optionally include all accounts.

@AlexanderBlanchardAC
Copy link
Contributor Author

Look for cases that use the switch-linked-user-form.tpl template. It looks like we deprecated most of those cases, but that allows the user to change back and forth between which account is active. By default you would want to show all accounts so you would likely need to extend the template to optionally include all accounts.

Cheers Mark,
The partner wants to be able to see the holds of multiple accounts at once, while also filtering out the holds of some linked users which would mean changing this form to use multiselect, is that going to cause issues in the RosenLevelUp or if any of the depreicated use cases are reinstated in the future?

@mdnoble73
Copy link
Member

mdnoble73 commented Jan 29, 2025

Do you have more information on the request, there isn't a lot of info in the Jira ticket. Is the use case that I want to see my holds as well as the holds of my child, but not the holds for my partner?

If that is the case, having filters at the top where patrons could choose the accounts they want to see (rather than select the ones to hide) would be better. Similar to what we do for materials requests. Then they would default to seeing all accounts in this case.

@AlexanderBlanchardAC
Copy link
Contributor Author

AlexanderBlanchardAC commented Jan 30, 2025

Do you have more information on the request, there isn't a lot of info in the Jira ticket. Is the use case that I want to see my holds as well as the holds of my child, but not the holds for my partner?

If that is the case, having filters at the top where patrons could choose the accounts they want to see (rather than select the ones to hide) would be better. Similar to what we do for materials requests. Then they would default to seeing all accounts in this case.

Hi Mark,
Yes, that use case would be correct. I have added a specification PDF to the Jira ticket. (I will update this tomorrow to the new filtering logic - include rather than hide).

AlexanderBlanchardAC and others added 4 commits January 30, 2025 17:09
Reverse the logic of the filter so that is filters to include records
rather than exclude them. Add the current user to the filters so that
the user can view just their own records.
Fix issue found in testing, move linked user filter to display whether
or not there are holds found and ensure display selected effectd only
the unavailable holds section
@AlexanderBlanchardAC
Copy link
Contributor Author

Hi Mark, I have moved the filter to the top of the page and reversed the logic so that it filters in rather than filtering out. By default the page shows the holds of the main user and all linked users. I have been asked to open a separate ticket for adding this functionality to checked out titles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants