Make it possible to mark items as "unavailable"
Please make it possible to mark items as "unavailable". This marking can be used in two situations: when an item or a set of items becomes temporarily unavailable to readers, and when items are withdrawn permanently.
Marking should be both manual and by running the job "Change Physical items information".
Ex Libris' advice to use a process is inappropriate because neither a process nor a process-related request is required in these cases.
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 difference from option 1 is that when an item is in an "unavailable" location, it can still be in a process such as loan, work order or any other process type. These are 2 separate attributes
- The existing options for location based configuration can be used
Option 3: A new "unavailable" field in item level
- It will be possible to mark specific items as "unavailable", similar to the availability status of portfolios
- Items marked as "unavailable" will be considered as "not in place"
- Similar to option 2, "unavailable" item can still be in a process such as loan, work order or any other process type. These are 2 separate attributes
- As this is a new attribute, relevant configuration options will need to be enhanced to take this attribute into consideration. Further analysis will be needed here
The description here, on this idea, is actually option 3.
During the analysis we identified that
although option 3 might give more flexibility, it is super complicated and would require huge effort. Therefore, the recommended option is option 2: Mark a location as "unavailable".
Do you think that implementing option 2 is enough? in that case, a dummy location "Unavailable" can be utilized for marking specific items by assigning them this location.
I want to share with you the analysis and discussion - you can see it in: https://public.3.basecamp.com/p/ERLrkhNUHtTYerEiaQAsG2uT
Please let me know your thoughts.
Thanks,
Tamar Fuches
Alma product team
-
Anonymous
commented
Please see also this idea: Enable us to display items in an "Unavailable" location type as Unavailable in Primo
https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/48370850-enable-us-to-display-items-in-an-unavailable-loc