Settings and activity
487 results found
-
18 votes
Lynn Reynish
supported this idea
·
-
26 votes
Lynn Reynish
supported this idea
·
-
12 votes
Lynn Reynish
supported this idea
·
-
8 votes
Lynn Reynish
supported this idea
·
-
19 votes
Lynn Reynish
supported this idea
·
-
51 votes
Reviewing this idea for future development.
Lynn Reynish
supported this idea
·
-
76 votes
Lynn Reynish
supported this idea
·
-
33 votes
Lynn Reynish
supported this idea
·
-
36 votes
Lynn Reynish
supported this idea
·
-
38 votes
Lynn Reynish
supported this idea
·
An error occurred while saving the comment -
42 votes
I apologize for the erroneous update. The change we made in Nov/Dec of 2024 did not actually deliver the requested functionality in this idea request. Changing status back to Under Review.
Lynn Reynish
supported this idea
·
-
14 votes
Lynn Reynish
supported this idea
·
-
5 votes
Lynn Reynish
supported this idea
·
-
6 votes
Lynn Reynish
supported this idea
·
-
26 votes
Lynn Reynish
supported this idea
·
-
60 votes
Lynn Reynish
supported this idea
·
-
42 votes
Lynn Reynish
supported this idea
·
-
38 votes
Lynn Reynish
supported this idea
·
-
54 votes
Lynn Reynish
supported this idea
·
-
32 votes
Lynn Reynish
supported this idea
·
I agree with Eleanor and Jason that an ability to share reports more easily between systems is essential on Polaris. Back when my library was on Horizon, we participated heavily in the SQL Bloodbank that shared reports and client / PAC customizations.
It wasn't simply plug-and-play due to variations on each system, but it was a much simpler process. It also didn't rely on Dynix (or SirsiDynix) to maintain reports - though they did push out changes that customers made that were useful to other customers.