Settings and activity
323 results found
-
28 votes
Shawn P. Farrell
shared this idea
·
-
21 votesShawn P. Farrell
shared this idea
·
An error occurred while saving the comment An error occurred while saving the comment Shawn P. Farrell
commented
The current cap of 99 invoices downloadable per day can impede & dictate staff workflows.
Because of this, our Acquisitions staff must also set limits with vendors like Baker & Taylor, as we can receive more than 99 in a day. It would be optimal if they could download at will up to invoice limit.
Not all shipments are dealt with sequentially, which further complicates matters.
-
5 votesShawn P. Farrell
supported this idea
·
-
2 votesShawn P. Farrell
shared this idea
·
-
13 votesShawn P. Farrell
shared this idea
·
-
2 votesShawn P. Farrell
shared this idea
·
-
2 votes
An error occurred while saving the comment Shawn P. Farrell
commented
The usefulness of additional/customizable transaction types came up again in a meeting today. We got a request for the addition of a Technology Instruction category & Patron Account category.
Shawn P. Farrell
shared this idea
·
-
2 votesShawn P. Farrell
supported this idea
·
-
10 votesShawn P. Farrell
supported this idea
·
-
22 votesShawn P. Farrell
supported this idea
·
-
20 votesShawn P. Farrell
shared this idea
·
An error occurred while saving the comment Shawn P. Farrell
commented
We've currently got 55 loan rules in Cincinnati. Not the most I've seen, but also not the least. At a certain point, it becomes difficult to remember, or better yet, know at a glance, their purpose & what loan rule governs what. The character limit to the name entry for loan rules limits how descriptive we can be.
A number of Sierra releases back saw the addition of the tooltip rollover when searching patron records. I'd love to see something similar applied, so when I'm scrolling & rolling over loan rules, I can see a 2 or 3 sentence free text description that offers enough detail to understand what in some cases are decades old rules.
An error occurred while saving the comment Shawn P. Farrell
commented
We've currently got 55 loan rules in Cincinnati. Not the most I've seen, but also not the least. At a certain point it becomes difficult to remember, or better yet know at a glance, what loan rule governs what. The character limit to loan rule names, while understandable, doesn't help.
A number of releases back saw the introduction of the little information rollover bubble in when searching for Sierra patron records. It would be great if a similar feature could be added to the loan rule table, where libraries could add a free text description of the loan rule's purpose - the patron types, item types, locations & durations, in an easy to understand blurb form.
-
11 votesShawn P. Farrell
supported this idea
·
-
6 votes
An error occurred while saving the comment Shawn P. Farrell
commented
Agreed. The current approach is curious. Our autonotice process kicks off shortly after 6:00 AM. Texts go out before emails, though only by a matter of minutes. So a patron might be sent a hold pickup text at 6:15 & a hold pickup email at 6:30, both of which they're likely to receive & see on the same device.
Shawn P. Farrell
supported this idea
·
-
6 votesShawn P. Farrell
supported this idea
·
-
4 votesShawn P. Farrell
supported this idea
·
-
53 votesShawn P. Farrell
supported this idea
·
-
33 votesShawn P. Farrell
supported this idea
·
-
5 votes
An error occurred while saving the comment Shawn P. Farrell
commented
@Elaine, in most cases, for an idea submitted through Idea Exchange, like yours, in order for it to be brought into production, it first has to be selected for an enhancement ballot & then be among the winning ideas once put to a vote by the user community.
The Sierra MEEP group has been discussing the possibility of a different approach for the next round of voting to give ideas like yours more of a shot at being brought to fruition.
Beginning with the ballot for 7.2 later this year, we may alternate between a general ballot where all eligible Sierra ideas are considered for inclusion, & a more focused one, where only those from a specific category, like Cataloging & Metadata Management, Reporting & Analytics, Acquisitions, Serials & Inventory Management, etc. are considered.
This approach would be an opportunity for ideas that may not have broad appeal but are still impactful a better chance of not only making the ballot, but winning.
Shawn P. Farrell
supported this idea
·
-
4 votes
An error occurred while saving the comment Shawn P. Farrell
commented
@Emma, Cirrius Impact (III's partner vendor) did the setup of the opt-in page for us, working with our Project Manager from Clarivate. We weren't able to do much in the way of customization. I've attached a look at part of that.
Shawn P. Farrell
shared this idea
·
-
10 votes
An error occurred while saving the comment Shawn P. Farrell
commented
Having to navigate back & forth from Cataloging mode disrupts the workflow. It'd be much better if staff could do this all within the Serials module.
Shawn P. Farrell
supported this idea
·
Further refinements, as requested by NYPL/BookOps:
We do not know the number of invoices in each file. If the system hits the limit during the load, some of the invoices are not loaded as the system stops before completely loading the file. We have no way of knowing what was missed until we manually check the file against the vendor’s emails. If invoices are missing and we reload, the system loads duplicates that will count against the limit on the day that it is reloaded. If we do not catch a missed invoice while it is on the vendor’s site, we will have to load it manually. In some cases, the vendor sends multiple small invoices and, when these load, the limit prevents us from loading larger invoices. Several staff members are loading invoices each day and have reported not being able to load 99 invoices if other staff have hit the limit.
-I want to be able to load the entire invoice file.
-I would like to know how many invoices are in a file. If there is an issue, I would like to know which invoices did not load.
-I want staff to be able to load invoices reliably before they are removed from the vendor's site so that we do not have to input them manually.