Settings and activity
346 results found
-
4 votes
An error occurred while saving the comment 
Shawn P. Farrell
shared this idea
·
-
3 votesShawn P. Farrell
supported this idea
·
-
2 votesShawn P. Farrell
supported this idea
·
-
46 votes
An error occurred while saving the comment Shawn P. Farrell
commented
We would like to see this, but as part of its implementation, we would like to be able to limit PTYPEs that can submit suggestions. For example, our Internet registrant PTYPE shouldn't be allowed to make any suggestions, until they validate their card for a more permanent PTYPE.
We would also like a limit on the number of suggestions that can be made by a given user in a specified period of time (for example, a max of 10 per month).
Lastly, if the suggestion is approved, an option should allow that a hold can be placed on the item for the requesting patron.
-
6 votesShawn P. Farrell
supported this idea
·
-
6 votesShawn P. Farrell
supported this idea
·
-
5 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Shawn P. Farrell
commented
We would very much like to see this.
Shawn P. Farrell
supported this idea
·
-
13 votesUNDER REVIEW · 5 comments · ILS - Sierra » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →
An error occurred while saving the comment Shawn P. Farrell
commented
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.Shawn P. Farrell
shared this idea
·
-
2 votesShawn P. Farrell
supported this idea
·
-
5 votesShawn P. Farrell
shared this idea
·
-
17 votesShawn P. Farrell
supported this idea
·
-
10 votesShawn P. Farrell
supported this idea
·
-
17 votes
An error occurred while saving the comment Shawn P. Farrell
commented
We've long relied on a sort of workaround to a traditional text messaging solution of e-mail-to-SMS, which LX Starter was unfortunately not designed to handle, so for e-mail notices sent to many SMS addresses, notices come through across several text messages, are missing images or other rich content, or are otherwise garbled or contain gibberish characters. Sometimes, the conversion fails & they don't get delivered at all, showing as sent & delivered in the LX Starter logs, but unopened. We're hoping to move to a more traditional text message notification, but would still very much like to see this plain text option.
A plain text option for notices sent through LX starter is absolutely essential for accessibility concerns. It would also be useful for the increasing number of patrons into wearables, which rely on text only messaging. But ISP deliverability (not marking our communications as spam) is the primary reason this is important.
Shawn P. Farrell
supported this idea
·
-
23 votes
An error occurred while saving the comment Shawn P. Farrell
commented
This would be fantastic, Sarah!
As often as we've shared & stressed a desired format for notes & messages, it's never universally maintained. And we have a long history of notes still attached to patron records that were imported into Sierra when CHPL migrated from Workflows back in 2012.
Even many more recently applied notes & messages are long irrelevant & should have been removed by staff but were not.
I'd love to be able to search for & purge anything older than 5 years, for example, to help declutter patron records. We found one record recently that had 144 notes attached to it. Nobody needs that much of a headache!
Shawn P. Farrell
supported this idea
·
-
2 votesShawn P. Farrell
shared this idea
·
-
35 votes
We will consider this idea for possible future development. Thank you!
Shawn P. Farrell
supported this idea
·
-
6 votes
An error occurred while saving the comment Shawn P. Farrell
commented
Navigation elements should definitely be consistently available from function to function.
Shawn P. Farrell
supported this idea
·
-
10 votesUNDER REVIEW · 0 comments · ILS - Sierra » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →Shawn P. Farrell
supported this idea
·
-
14 votes
An error occurred while saving the comment Shawn P. Farrell
commented
In a meeting right now where interest in being able to access & report on this data is still very much a thing.
Shawn P. Farrell
supported this idea
·
-
3 votesShawn P. Farrell
shared this idea
·
As Ray notes, this can happen again, as it did outside of our recent upgrade, only yesterday, with a batch of failed notices appearing at random. Not only did these (& those in the example in the original post) fail to send, there's no identifying data attached to the reporting.