07-30-2008, 08:42 PM
Thanks, Beth. These are great points.
--I hadn't noticed a chat lag but, so far, I've not had any 'patron' who wasn't right there with me (or was me!). Can others chime in as to whether or not they see a delay?
--Not all databases (or all web resources, for that matter) will co-browse properly. With the licensed databases we need to compile a list of the 'idiosyncracies' of each database. Since databases could seldom, if ever, be cobrowsed in tutor.com, we haven't had to deal with these idiosyncracies. Please post comments on which databases co-browse well and which not so well (and which not at all-anybody tried Factiva yet?) and I'll create a list of our licensed databases and how they work with QP.
--I don't know why you are prompted to log in each time, but I think it might be useful for the student since they can see what will happen when they access a database from off campus. As for who should log in, I don't think it matters as far as the ability to cobrowse is concerned (maybe someone can try it both ways and report if there is any difference in co-browsing), but I think it would be better to have the student log in. That way, you can verify that they know their userid and password and, if they are from a different college than you, they will have access to college specific resources. For the librarian to log in to college specific resources, you'd have to use the guest login that is in the policy page.
--I hadn't noticed a chat lag but, so far, I've not had any 'patron' who wasn't right there with me (or was me!). Can others chime in as to whether or not they see a delay?
--Not all databases (or all web resources, for that matter) will co-browse properly. With the licensed databases we need to compile a list of the 'idiosyncracies' of each database. Since databases could seldom, if ever, be cobrowsed in tutor.com, we haven't had to deal with these idiosyncracies. Please post comments on which databases co-browse well and which not so well (and which not at all-anybody tried Factiva yet?) and I'll create a list of our licensed databases and how they work with QP.
--I don't know why you are prompted to log in each time, but I think it might be useful for the student since they can see what will happen when they access a database from off campus. As for who should log in, I don't think it matters as far as the ability to cobrowse is concerned (maybe someone can try it both ways and report if there is any difference in co-browsing), but I think it would be better to have the student log in. That way, you can verify that they know their userid and password and, if they are from a different college than you, they will have access to college specific resources. For the librarian to log in to college specific resources, you'd have to use the guest login that is in the policy page.
Jacque Dessino
Electronic Services Librarian
Tidewater Community College
757-822-2646
jdessino@tcc.edu
Electronic Services Librarian
Tidewater Community College
757-822-2646
jdessino@tcc.edu