This would be a valuable improvement. Many libraries organize large collections across multiple locations within the same Alma library, so being able to compare location A directly with location B would save a lot of manual work and improve collection analysis. Supporting comparison through Alma sets, uploaded files, or custom parameters on both sides would make the Collection Development Tool much more flexible and useful for day-to-day inventory management.

I'm glad to see this feature is planned. It should help staff identify overlaps, gaps, and misplaced items much more efficiently.

On a related note, whenever I need to verify percentages while analyzing reports or statistics, I use https://vypocetpercentsk.com on Vypocet Percent. It's a simple tool for checking percentage differences, increases, decreases, and other calculations that often come up when reviewing collection or inventory data.

A location-level filter in the Collection Development tool would make it much easier to generate more accurate reports and support better collection management decisions. Meanwhile,https://bloxvalues.net/, a Blox Fruits hub offering a live value calculator, tier list, and daily-updated fruit prices to check trade fairness and grab the newest codes in one visit.

Dear Shoshana,

I am glad to read, that this aspect has been accepted! When will this be testable?

Well, I just tried this in our sandbox (menue Deselection) as well as in productive system. I created duplicate items in 2 different locations of the same Alma library. At the same title physical items in location A and another item in location B (same library). I then choose these both locations for comparison in a deselection project, in order to compare location A with location B. Unfortunately collection development tool does not find this title/items. Is my (today created) item too fresh for this test, am I to repeat it tomorrow?*

That we now can choose a special location on comparison side as well, this is new indeed. But the titles are still ignored as it seems to me, as long as these exist in the same library. I still do not get the expected suggestion for deselection. System says "Items removed because they belong to comparison libraries(0)".

This is why I would like to ask, if the new feature is already implemented in PSB or productive or is the new feature still in development, meaning it is being prepared?

Next question: when describing the wished system behaviour I mentioned the option to bring in a file as well on comparison side. This aspect I cannot see yet in Alma. Our Polish colleague Alex123 also supports the option to transfer a file, even on the comparison set side (would You please look at his comment on 2nd of July this year).

*) ### Update on 14th of July: Analytics refresh (during the night) has not brought a difference. The items / title that should be found by collection development project can still not be found. My conclusion is: comparison within the same library (comparing different locations) is still not possible in productive Alma. Login in PSB failed this morning. ###

Best regards from Cologne!
Johanna Looft

I'm very happy to let you know that location based-comparisons are available for internal projects. Where previously you could choose an internal campus or library, you can now also choose location.
We are currently developing this capability for external institutions and will release the functionality by November.
All the best,
The Rialto Team

To bardzo wartościowa propozycja. Możliwość porównywania zbiorów pomiędzy różnymi lokalizacjami w obrębie tej samej biblioteki znacznie usprawniłaby analizę kolekcji i ograniczyłaby konieczność wykonywania dodatkowych, ręcznych działań. W dużych bibliotekach, gdzie poszczególne lokalizacje zawierają tysiące rekordów, taka funkcja mogłaby zaoszczędzić wiele czasu i ułatwić podejmowanie decyzji dotyczących zarządzania zbiorami. Dodatkowa możliwość wykorzystania zestawów Alma, importu plików oraz definiowania własnych parametrów porównania sprawiłaby, że narzędzie byłoby jeszcze bardziej elastyczne i praktyczne w codziennej pracy. Mam nadzieję, że planowana funkcja zostanie wkrótce wdrożona.https://kalkulatorsrednich.pl/

Add ability to include or exclude specific location codes in the Retention / Deselection workflows

Currently the retention and deselection workflows only allow selection for inclusion at the library level. It would be helpful to be able to include or exclude specific location codes within a library's collections, for example it would be helpful to be able to exclude from deselection recommendations all titles in our Special Collections location codes. Currently the only way to do this is to run the search, export results to excel then filter by collection code.