Settings and activity
305 results found
-
17 votes
The product team will review this idea for consideration for a future release.
Shawn P. Farrell
supported this idea
·
-
6 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Shawn P. Farrell
supported this idea
·
-
26 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Shawn P. Farrell
supported this idea
·
-
11 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Shawn P. Farrell
shared this idea
·
-
19 votesShawn P. Farrell
supported this idea
·
-
18 votesShawn P. Farrell
supported this idea
·
-
4 votesShawn P. Farrell
supported this idea
·
-
11 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Shawn P. Farrell
supported this idea
·
-
6 votes
An error occurred while saving the comment Shawn P. Farrell
supported this idea
·
-
4 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Shawn P. Farrell
supported this idea
·
-
15 votes
An error occurred while saving the comment Shawn P. Farrell
commented
This might be helpful, though it's already a significant improvement to be able to point to a third party discovery layer (in my case, BiblioCore). Though our Catalogers & Acquisitions staff especially like to see that changes made to records have registered in the public display & are sometimes hindered by the lag in Bibliocommons. If they could quickly jump to the WebPac view as an alternative, they might be a little more sure that changes are displaying as intended.
Shawn P. Farrell
supported this idea
·
-
16 votes
The product team will review this idea for consideration for a future release.
Shawn P. Farrell
supported this idea
·
-
7 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Shawn P. Farrell
supported this idea
·
-
7 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Shawn P. Farrell
supported this idea
·
-
9 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Shawn P. Farrell
supported this idea
·
-
18 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
An error occurred while saving the comment Shawn P. Farrell
commented
This would be very helpful!
Shawn P. Farrell
supported this idea
·
-
28 votes
This enhancement is planned for Sierra 6.5.
Shawn P. Farrell
supported this idea
·
-
8 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Shawn P. Farrell
supported this idea
·
-
20 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Shawn P. Farrell
supported this idea
·
-
5 votes
An error occurred while saving the comment Shawn P. Farrell
commented
As a library that floats most of our collection, we too often see this problem & without this nuance, these items are very difficult to look for in the reports we produce. We'd love to see this addressed.
Shawn P. Farrell
supported this idea
·
Agreed! I had submitted a related enhancement suggestion some time ago focusing mainly on just additional level(s) of overdue notices, as we want to differentiate between them to demonstrate the increased urgency (but have not been able to do that with other systems including Teleforms or i-tiva). It seems clear development needs to be done on III's side, but equity across the board & involving all available notice types (x level overdues, courtesy, etc.) would be a terrific leap forward for IPA as a product & for our many customers who still rely on telephone notifications.