[Koha] Changing the way passwords are entered in the staff client
There is an open bug report (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5280) suggesting that the staff client's change password page (accessed via the Change Password button from a patron's account in the staff client) use a password-type input form, meaning the password you enter would be masked as it is on login forms (***). I have a patch in progress which would implement this along with a second confirmation field (confirm password) as is customary on change password forms--you can't be confident you're entering the password correctly if your entry is masked. The problem is that this doesn't work with the feature which suggests a random password: Below is a randomly generated suggestion. We can't offer to give the patron a randomly-generated password if we aren't able to tell them what it is when we're assigning it. I'm asking for opinions: Is the random password feature something we can give up? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] KOHA target for SFX
I did some work along these lines a while back; see http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3634 Patch has not been updated since the last time I worked on it. Jane Wagner Senior Project Manager LibLime, a division of PTFS Content Management and Library Solutions 11501 Huff Court North Bethesda, MD 20895 (301) 654-8088 x 151 jwag...@liblime.com jwag...@ptfs.com *From:* koha-boun...@lists.katipo.co.nz [mailto: koha-boun...@lists.katipo.co.nz] *On Behalf Of *Stuart Spore *Sent:* Friday, October 07, 2011 11:53 AM *To:* Koha@lists.katipo.co.nz *Subject:* [Koha] KOHA target for SFX Is anyone out there working on a KOHA target for SFX? I find brief mentions of this being a good and attainable goal but no actual code or files Stuart -- \7c===\7c \7c Stuart Spore \7c Associate Director for Systems \7c NYU Health Sciences Libraries \7c NYU School of Medicine \7c 550 First Ave. \7c New York, NY 10016 \7c v: 212.263.1092 \7c f: 212.263.6534 \7c e: spore...@nyu.edu \7c\7c ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] KOHA target for SFX
Stuart, You can link directly to books and journals with their ISBN/ISSNs with the following URL pattern: OPACBaseURL/isbn/ISBN and OPACBaseURL/issn/ISSN The Apache conf rewrites those URLs into searches, so you'll get 1 or more biblios with those standard numbers in their 020/022 fields. If it's a single result, it'll go directly to the details page. There is no way at this time to link to the volume/issue level, since that information is stored in the MARC only in items.enumchron (952$h), and that's uncontrolled text (and is not indexed in part, only in whole), so you'd have to psychicly predict the way the volume/issue got rendered in your data. Hope this helps, -Ian 2011/10/7 Wagner, Jane jwag...@liblime.com I did some work along these lines a while back; see http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3634 Patch has not been updated since the last time I worked on it. Jane Wagner Senior Project Manager LibLime, a division of PTFS Content Management and Library Solutions 11501 Huff Court North Bethesda, MD 20895 (301) 654-8088 x 151 jwag...@liblime.com jwag...@ptfs.com *From:* koha-boun...@lists.katipo.co.nz [mailto: koha-boun...@lists.katipo.co.nz] *On Behalf Of *Stuart Spore *Sent:* Friday, October 07, 2011 11:53 AM *To:* Koha@lists.katipo.co.nz *Subject:* [Koha] KOHA target for SFX Is anyone out there working on a KOHA target for SFX? I find brief mentions of this being a good and attainable goal but no actual code or files Stuart -- \7c===\7c \7c Stuart Spore \7c Associate Director for Systems \7c NYU Health Sciences Libraries \7c NYU School of Medicine \7c 550 First Ave. \7c New York, NY 10016 \7c v: 212.263.1092 \7c f: 212.263.6534 \7c e: spore...@nyu.edu \7c\7c ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.wa...@bywatersolutions.com Twitter: @sekjal ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Changing the way passwords are entered in the staff client
Owen Leonard oleon...@myacpl.org
There is an open bug report
(http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5280)
[...]
The problem is that this doesn't work with the feature which suggests
a random password: Below is a randomly generated suggestion. We
can't offer to give the patron a randomly-generated password if we
aren't able to tell them what it is when we're assigning it.
I'm asking for opinions: Is the random password feature something we
can give up?
I could give it up BUT why would we need to?
A cool thing I've seen on dtc (package dtc-common) in debian is a
button next to the password field that uses javascript to fill it
with random characters and change it to type=text so you can
read it. The actual password could be generated by the perl
script. dtc's code boils down to:
function dtc_gen_passwd(frm_name,fld_name){
document[frm_name][fld_name].value = 'smpc9cf98dzy';
var curObj = document[frm_name][fld_name];
try {
document[frm_name][fld_name].type = 'text';
} catch (e) {
// type property read only on IE at the time of this writing,
// so replace the control with a new one
if (curObj.getAttribute('type') != 'text') {
var newObj=document.createElement('input');
newObj.setAttribute('type','text');
newObj.setAttribute('name',curObj.getAttribute('name'));
newObj.setAttribute('class',curObj.getAttribute('class'));
newObj.value = curObj.value;
curObj.parentNode.replaceChild(newObj, curObj);
}
}
}
and it's then called from the generate button with somethng like
onClick=dtc_gen_passwd('addnewuser_frm','newadmin_pass');
AFAIK the above is Copyright: (C) 2001-2008, Thomas Goirand tho...@goirand.fr
(C) 2001-2008, Damien Mascord tus...@tusker.org
(C) 2003-2008, GPLHost LLC i...@gplhost.com
License: LGPL-2
Maybe there's a smarter way to do that with the js libs and maybe
generating the password in the javascript, but I offer it as an idea.
Who'd've thunk it? Me suggesting using more javascript.
Hope that helps,
--
MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op.
http://koha-community.org supporter, web and LMS developer, statistician.
In My Opinion Only: see http://mjr.towers.org.uk/email.html
Available for hire for Koha work http://www.software.coop/products/koha
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] New Release team elected
Congrats to the 3.8 team. Looks like a great group. Hooray for Koha! Lori 2011/10/5 Chris Cormack chr...@catalyst.net.nz It is with great pleasure that I get to announce that during last nights meeting, the release team for 3.8 was elected. You can read all about it here http://koha-community.org/koha-3-8-0-release-team-elected/ And all about the other stuff decided at the meeting here http://wiki.koha-community.org/wiki/General_IRC_Meeting,_5_October_2011 (There is a link to the minutes) Congratulations to all those elected Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
