Settings and activity
203 results found
-
21 votes
-
4 votes
Alison Pruntel
supported this idea
·
-
7 votesAlison Pruntel
supported this idea
·
-
22 votesAlison Pruntel
supported this idea
·
-
73 votesAlison Pruntel
supported this idea
·
An error occurred while saving the comment An error occurred while saving the comment Alison Pruntel
commented
We have random patrons who are receiving their library notices via LX Starter and then suddenly they hard bounce.
Once they have a hard bounce, at least in some cases, we see a message in LX that says “The email address … is invalid because it bounced the last email that was sent to it. Unless you replace this email address with a valid one, this contact cant be emailed.”
E-mail that we send directly to this same patron from the same “from” address (but isn’t a notice going through III) does not bounce. Also, the patron has already put our email address in their safe senders list. Having them put that address in their safe senders/address book/contacts does not seem to mitigate the issue. We don’t want to tell patrons to keep doing this if it doesn’t work.
Is there any remedy besides telling patrons to set up a different email account just for notices and see how that goes? It seems pointless to tell them to put our email address into their safe senders list if it doesn’t fix it. We can’t put their old address/address that already hard bounced back into their account or at least via the LX backend, so they’d have to give us a different address. Their email address IS valid and it's not reasonable to ask them to create yet another email address just for our notices.
-
23 votes
The product team will review this idea for consideration for a future release.
Alison Pruntel
supported this idea
·
An error occurred while saving the comment Alison Pruntel
commented
I like this idea, but we do get complaints that we send out too many notices and none of them are opt in/opt out (ideally opt OUT). If we could somehow allow an opt-OUT for specific notices (not all of them...for example bills), that would help us accommodate those who complain about having no control over their notices (aside from opting out of them all completely by having a notice preference of print or phone).
Also, this might address an issue we've seen where some of our LX notices "fail to send" (with no explanation), including hold pickup notices. We just had a patron come in and complain because she never got the hold pickup (checked LX and it had failed), but did get her hold cancellation notice after her hold expired.
-
25 votes
The product team will review this idea for consideration for a future release.
Alison Pruntel
supported this idea
·
-
21 votes
The product team will review this idea for consideration for a future release.
Alison Pruntel
supported this idea
·
-
23 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
An error occurred while saving the comment Alison Pruntel
commented
It would be much easier to have this in Sierra vs. relying on it to be documented somewhere else. With having it in Sierra, we can make sure the system admin is able to maintain that information (won't get overwritten on a spreadsheet somewhere).
Alison Pruntel
supported this idea
·
-
32 votes
The product team will review this idea for consideration for a future release.
Alison Pruntel
shared this idea
·
-
5 votesAlison Pruntel
shared this idea
·
-
3 votes
An error occurred while saving the comment Alison Pruntel
commented
Due to the limitations of Wix forms, we are having to use a 3rd party application instead (OpenForms), therefore not keeping the user/patron on one domain/platform.
Alison Pruntel
supported this idea
·
-
52 votes
An error occurred while saving the comment Alison Pruntel
commented
This just came up again. We have two books with the title "France" and no author. A 2024 Lonely Planet France guidebook and the 2023 DK guidebook are included in the same Vega record. The books have separate bibs with unique ISBNs. The explanation is that these bibs are rolling up together because they have the same title (245 $abnp) and no author field to differentiate them either. It's frustrating that Vega won’t let versions of the same title roll up if there is an errant comma in an author field, but two books called “France” it determines are the same. Support directs us to this:
1. If the bib is for a single word or simple title that and has no author, consider adding distinguishing data to the title field to unroll it from the larger work. For Example: A travel guide about Thailand that is simply titled "Thailand" and has no author can be updated in the following way to differentiate the instance from other works with the same title and no author:
a. Include the Guide Series in the title: $a Thailand $b (Lonely Planet)
b. Include the publication year in the title: $a Thailand $b (Lonely Planet 2023)
c. Give the guide series an author designation:
1. Title: Thailand
2. 110 Author: Lonely Planet Travel Guides
d. Some libraries choose to have a single bib record for guides with yearly volumes for each reprint of the guide and use the item volume details to allow the patron to select a particular year's guide.Adding a subtitle that is not actually part of the title to satisfy the software is a deviation from standard cataloging procedure.
An error occurred while saving the comment Alison Pruntel
commented
See comment from PrarieCat 1/9/24 on Vega Listserv - https://listserv.iii.com/read/messages?id=507451.
We run into this issue, where a title like Bloom's Literary Places (Paris, London, etc.) were rolling up with travel guides with the same title (i.e., Paris), because in both cases the items in question had the same 245$a and neither had an author. I don't know if this would be remedied by being able to customize or not. Our catalogers would prefer to NOT change the 245 to something other than what's on the book in order to make Vega roll up correctly.
Alison Pruntel
supported this idea
·
-
44 votesAlison Pruntel
supported this idea
·
-
13 votesAlison Pruntel
supported this idea
·
-
10 votes
An error occurred while saving the comment Alison Pruntel
commented
I would like to add on to this idea... it would be nice if you could add a comment to go with each item you bookmark...so WHY you bookmarked it. This is what we'd want if we were making a broad showcase like Staff Picks. So there would be a description of the showcase itself and then each item would have a blurb from the staff member, why they chose it. I think it would also help when patrons bookmark items. Often they don't create a list, may just have "For Later" and then can't remember why they bookmarked something (i.e., friend recommended, etc.). Related, the showcase creator...aside from the Nickname, it would be nice if there was a bio or description you could include.
Alison Pruntel
supported this idea
·
-
2 votes
The product team will review this idea for consideration for a future release.
Alison Pruntel
shared this idea
·
-
19 votes
An error occurred while saving the comment Alison Pruntel
commented
I would love to be able to use a showcase vs. the RSS lists for the mobile app. Less work!
Alison Pruntel
supported this idea
·
-
31 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Alison Pruntel
commented
Per Barbara Leach, the hold-removed table records the following, so would need similar columns to the hold table...
removed_gmt
removed_by_user
removed_by_process
removed_by_programAlison Pruntel
shared this idea
·
-
15 votesAlison Pruntel
shared this idea
·
Another unintended consequence is that if a patron who has an email account that works for everything else, just bounced randomly in LX and thus now blocked forever, they also get removed from our other notification systems (OrangeBoy/Savannah specifically), which we use for marketing e-blasts. OrangeBoy/Savannah looks at the account in Sierra on a weekly basis to confirm the e-mail address has not changed. If the patron's notice bounced, then after a week they will no longer get our other e-mail communications.