Settings and activity
56 results found
-
3 votes
Phil Agnew
shared this idea
·
-
6 votesPhil Agnew
supported this idea
·
-
14 votesPhil Agnew
supported this idea
·
-
4 votes
An error occurred while saving the comment Phil Agnew
supported this idea
·
-
11 votes
An error occurred while saving the comment Phil Agnew
commented
I have a feeling we're talking specifically about the LDR... I won't pretend to know everything about the database, but I did A LOT of digging to see if I could get LDR data to surface in a report... it seems like the data exists in the database primarily as the component parts for the editable positions, which is probably why the field tag can't be edited directly. It stands to reason that the string must exist SOMEWHERE (otherwise we wouldn't see non-configurable data like the record length), but it doesn't appear to be a part of the normal BibliographicSubfields data... I know that all probably sounds inconsequential to this Idea, but if this development would make it easier to surface LDR data as a string in database queries, all the better!
Phil Agnew
supported this idea
·
-
19 votesPhil Agnew
supported this idea
·
-
14 votes
An error occurred while saving the comment Phil Agnew
commented
This probably should have been deployed with the addition of the feature in Polaris, but I can understand the disconnect, since Vega/LX Starter is designed to support other ILS like Sierra.
Phil Agnew
supported this idea
·
-
10 votesPhil Agnew
supported this idea
·
-
30 votesPhil Agnew
supported this idea
·
-
11 votesPhil Agnew
supported this idea
·
-
15 votesPhil Agnew
supported this idea
·
-
31 votes
An error occurred while saving the comment Phil Agnew
commented
Honestly, we went live with Dated Notes, so I didn't even realize the merged patron data was being stored in a field that we had suppressed from view... I would still say the merged account logging is lacking (why do notes only include library card number when the Delete Patron transaction only logs PatronID?), but at the very least, these notes should be entered as Dated Notes as a configuration option. I might go even further to say that ANY system generated note should be optionally (only because some people aren't using Dated Notes) entered as a Dated Note. They already include timestamps on them, so it's like they were practically engineered for this application.
Phil Agnew
supported this idea
·
-
17 votesPhil Agnew
supported this idea
·
-
10 votesPhil Agnew
supported this idea
·
An error occurred while saving the comment Phil Agnew
commented
Is this really not available in Leap? I haven't really looked into the PDF417 configuration much, but I didn't realize it was only supported by the desktop client... I guess Leap probably just needs a separate "Get Data From Barcode" button on the Registration workform that prepares it to receive the segmented/delimited data from the barcode reader... This is a feature I've always wanted to try implementing, so I'm a little disappointed to hear it isn't supported in Leap...
-
14 votesPhil Agnew
supported this idea
·
-
6 votes
An error occurred while saving the comment Phil Agnew
commented
Yeah... I'm not sure how much of this is a Leap problem and how much is a browser problem, but the staff password field for Leap login should be made distinct in some way from the patron password field that surfaces with the "Reset Password" button. Built in password managers may still recognize it as a password field and attempt to save it for you, but it would be helpful if it at least didn't overwrite the staff login password... though that might be tricky if the passwords are only being managed by the browser per domain...
Phil Agnew
supported this idea
·
-
8 votes
An error occurred while saving the comment Phil Agnew
commented
I see how this could be useful, but want to stress that this would need to have some sort of "Reset Unclaimed Holds Count" similar to the "Reset Claim Count" for claims returns. I can just foresee a situation where a patron has 20 picture books they requested go unclaimed after an unexpected personal tragedy being blocked from holds by an automated process like this. Staff need a way to remedy that without the patron having to wait 6 months (or whatever configured time period) for the block to drop off.
Phil Agnew
supported this idea
·
-
6 votes
An error occurred while saving the comment Phil Agnew
commented
I agree with Lynn, that this should be enabled as a configurable option. While I'm personally on team "Opt-Out" (I just think that most people prefer to have access to their own reading history), I understand and appreciate the needs of people on team "Opt-In". So, yes please, allow Polaris libraries to configure default behaviors reading history (or any field, really) in new patron registrations.
Phil Agnew
supported this idea
·
-
5 votes
An error occurred while saving the comment Phil Agnew
commented
I think this indicative of the broader need to have have better CSS for dynamic scaling of the Leap web client. I'm sure this is something that would also affect anyone trying to view patron account information on a tablet with a smaller screen/resolution... Not directly related, but I'd love to see us eventually get a genuinely "mobile friendly" version of Leap. There are a lot of interesting applications for running the web app on a phone/phablet sized device.
Phil Agnew
supported this idea
·
-
9 votesPhil Agnew
shared this idea
·
.png){kind=link}
.png){kind=link}
I can remember other systems using tag data containing image URLs to display custom cover art for bibliographic records. I'm not going to advocate we play whack-a-mole with every DVD that doesn't have cover art available in Syndetics, but I can understand the impulse to want to fix "the big ones". Furthermore, it's sometimes useful to provide links to images for "Things" that a library might circulate like laptops, activity kits, musical instruments, etc. and this would make that possible as well.