Patryk
My feedback
11 results found
-
266 votes
Dear colleagues,
Thank you for raising this idea.
This was part of the CERV cycle in 2025, but did not make it to the final list.
During the analysis, 3 possible approaches were discussed, each has a different estimation and effort:
Option 1: New dedicated process type
- It will be possible to mark specific items as "unavailable", similarly to the way it is possible to mark them as "missing"
- Items marked as "unavailable" will be considered as "not in place"
- The new "unavailable" option will appear as a possible process type in all the places where there is a list of process types, including configuration options such as Fulfillment Unit Rules
Option 2: Mark a location as "unavailable"
- It will be possible to mark a location as "unavailable"
- All items in this location will be considered as "not in place"
- The difference from option 1 is that when an item…
Patryk
supported this idea
·
-
93 votes
Dear colleagues,
Thank you for raising this idea.
This idea is related to another one - https://ideas.exlibrisgroup.com/forums/308173/suggestions/48370850, which was part of the CERV cycle in 2025, but did not make it to the final list.
During the analysis, 3 possible approaches were discussed, each has a different estimation and effort:
Option 1: New dedicated process type
- It will be possible to mark specific items as "unavailable", similarly to the way it is possible to mark them as "missing"
- Items marked as "unavailable" will be considered as "not in place"
- The new "unavailable" option will appear as a possible process type in all the places where there is a list of process types, including configuration options such as Fulfillment Unit Rules
Option 2: Mark a location as "unavailable"
- It will be possible to mark a location as "unavailable"
- All items in this location will be considered as "not in place"
- The…
Patryk
supported this idea
·
-
23 votes
Patryk
supported this idea
·
-
7 votes
Patryk
supported this idea
·
-
10 votes
Patryk
supported this idea
·
-
100 votes
Patryk
supported this idea
·
-
3 votes
An error occurred while saving the comment
Patryk
shared this idea
·
-
19 votes
Patryk
supported this idea
·
-
69 votes
Patryk
supported this idea
·
-
3 votes
Patryk
shared this idea
·
-
13 votes
An error occurred while saving the comment
Patryk
commented
Library-level request limits would also be useful.
Patryk
supported this idea
·
I could be wrong, but I don't think I am able to set the process type „Requested” for title level requests to make the item unrequestable (trough TOU) after request, but before placing on hold shelf. I would like the ability to request to be limited to only currently available items (i.e. active requests). We loan items for a fairly long period of time, so usually pending requests for physical items are of no use to us. Of course, I may have missed some existing solution