[LibX] broken embedded cues in Amazon.com

Godmar Back godmar at gmail.com
Wed May 28 07:11:59 PDT 2008

There's no wiki as of yet though we could include one as part of our
new website.
Till then, feel free to ask questions already answered again.

 - Godmar

On Wed, May 28, 2008 at 4:41 AM, Chad Nelson <c.nelson at londonmet.ac.uk> wrote:
> Is there a wiki / knowledge base or something similar for these kinds of
> suggestions. I know there is a FAQ on the libx site, but it doesn't cover
> things like this. I use the list archive at Nabble, but it is sometimes a
> bit difficult to find what I'm looking for on it, and so I end up asking
> questions that have already been answered, probably a few times.
> If there isn't something like it yet, I'd certainly be willing to slog
> through some archive threads to pull out the suggestions.
> Thanks
> Chad
> On Tue, May 27, 2008 at 9:40 PM, Tom Pasley <PasleyT at crop.cri.nz> wrote:
>> I agree with Godmar on this point - there will always be changes behind
>> the scenes at sites which will break the code for cues... one of the
>> things we can do is use the debug feature (Firefox) that Godmar told us
>> about earlier to discover what might be the underlying cause.
>> Here's what Godmar suggested on 3/04/2008 2:46 p.m. (my time):
>> "One comment on how to debug this, or help debug this:
>> To see what goes wrong when LibX processes a cue, go to "about:config"
>> and add a new entry of type "boolean".  Call it "libx.doforurl.debug"
>> and set it to true. Then visit the page on which the cue operates. This
>> setting will log any exceptions thrown during cue processing to the
>> JavaScript error console."
>> Firefox is good from the updating perspective... (though it can be a
>> pain at times). I'm not sure how this relates to the locked-down
>> scenario you mention Richard - surely you wouldn't use Internet Explorer
>> in a "locked-down" environment? [cheesy grin]
>> Sending details from the debugging helps speed up the resolution... the
>> way I see it, the cues at sites like Amazon are something extra - the
>> ISSN and DOI linking from vendors such as the Elsevier ScienceDirect and
>> SpringerLink are the crucial bits - thankfully these are relatively
>> stable. Amazon seems to be a problematic site - pity it's so popular!
>> just my inflation-adjusted 2c.
>> Tom
>> Visit our website at http://www.crop.cri.nz
>> ______________________________________________________
>> CAUTION: The information contained in this email is privileged
>> and confidential.  If you read this message and you are not the
>> intended recipient, you are hereby notified that any use,
>> dissemination, distribution or reproduction of all or part of the
>> contents is prohibited. If you receive this message in error,
>> please notify the sender immediately.
>> Any opinions or views expressed in this message are those of the
>> individual sender and may not represent those of their employer.
>> _______________________________________________
>> Libx mailing list
>> Libx at mozdev.org
>> https://www.mozdev.org/mailman/listinfo/libx
> --
> Chad Nelson
> Subject Librarian
> Humanities, Arts and Languages
> Governance and International Relations
> London Metropolitan University
> _______________________________________________
> Libx mailing list
> Libx at mozdev.org
> https://www.mozdev.org/mailman/listinfo/libx

More information about the Libx mailing list