Settings and activity
141 results found
-
11 votes
Elizabeth Wright
supported this idea
·
-
23 votes
An error occurred while saving the comment Elizabeth Wright
shared this idea
·
-
31 votesElizabeth Wright
supported this idea
·
-
4 votesElizabeth Wright
shared this idea
·
-
8 votesElizabeth Wright
shared this idea
·
-
25 votes
Please watch the roadmap; this is work we are planning on doing.
https://portal.productboard.com/iii/15-vega-product-portal/c/676-wish-lists-and-vega-bookmarks-integration
Best,
Angela Nolet
Sr. Product Manager
Elizabeth Wright
supported this idea
·
-
8 votesElizabeth Wright
supported this idea
·
-
14 votesElizabeth Wright
shared this idea
·
-
7 votesElizabeth Wright
shared this idea
·
-
8 votesElizabeth Wright
shared this idea
·
An error occurred while saving the comment Elizabeth Wright
commented
I have attached an example of an item record with a status of claimed returned.
An error occurred while saving the comment Elizabeth Wright
commented
For libraries with floating collections, the location where an item was made "claimed returned" may not reflected in the item record. This is because the 3 options staff have when an item is "claimed returned" does not change the location of the item.
Essentially the problem:
An item is “checked out” at location A.
The item is “claimed returned” at location B.
The item location remains as location A.Staff have 3 choices when they make an item claimed returned:
· 1. Places a claimed returned note in both the item and patron records
· 2. (Optional) Removes the check-out link between the patron and the item; this is equivalent to checking in the item without assessing a fine. If desired, the operator can generate a manual charge and apply it to the patron.
· 3. (Optional) Flags the item as missing (STATUS = 'm') and cancels any outstanding holds on the item
In the second scenario above the item is not "checked in" - instead the link between the patron and the item is severed and there is no check in.
Why is this important? Libraries with floating collections often allow customers to return their items to any branch. If the customer says that they returned the item to a branch that was not their checkout location at a later date, the item is impossible to find. The item location still reflects the original checkout location.
Thank you,
Elizabeth -
19 votes
An error occurred while saving the comment Elizabeth Wright
commented
It is odd that the bib level holds continue to appear on the notices for as long as the library notice cycle setting, but the item level holds do not.
Elizabeth Wright
supported this idea
·
-
15 votesElizabeth Wright
supported this idea
·
-
30 votesElizabeth Wright
supported this idea
·
-
10 votesElizabeth Wright
shared this idea
·
-
2 votesElizabeth Wright
shared this idea
·
-
30 votesElizabeth Wright
supported this idea
·
-
15 votesElizabeth Wright
supported this idea
·
-
14 votesElizabeth Wright
shared this idea
·
-
6 votesElizabeth Wright
shared this idea
·
An error occurred while saving the comment Elizabeth Wright
commented
Sierra 6.6 includes an upgrade to PostgreSQL 16. Innovative should be more specific and tell us that we are upgrading to PostgreSQL 16.10. PostGres 16.14 was the last version in this cycle.
Does Innovative upgrade PostgreSQL with each Sierra upgrade? Will they patch between upgrades with any security fixes?
Libraries need to know Innovative's plans PostgreSQL development, and I am unsure if they are always included in the upgrade notes.
-
16 votes
An error occurred while saving the comment Elizabeth Wright
commented
Please. We have developed very long and complicated workarounds because we cannot export the Invoice Summary report. If Innovative needs an "export option" idea for each functionality please let us know so that we can start creating those idea.
Elizabeth Wright
supported this idea
·
If a library's circulation or OPAC rules allow a customer to place a bib or item hold, the customer should also be able to freeze that hold at any time. This functionality is available in Polaris, but not Sierra.
Currently, customers cannot freeze a bib-level hold if there is an available item that could fill the request. This prevents customers from managing their holds the way they want. In many cases, they do not know an appropriate "Not Needed Before" date, but they do know that they are not ready to receive the item immediately.
Allowing holds to be frozen regardless of item availability would give customers greater control over their accounts and reduce unnecessary hold fulfillment.
This enhancement is particularly important for:
Libraries that catalog DVD seasons on separate bibliographic records, where customers may want to request an entire series but receive the seasons over time.
Libraries with heavy users who routinely place the maximum number of holds and prefer to manage when those holds become active based on their own reading or viewing schedule.