Translator list

2»
  • ajlyon
    And now we have two bars at the top of the page. I don't see where people are getting these pages that trigger an error...
  • ajlyon
    I've updated GS again to use the same XPath in detectWeb and doWeb. Maybe that'll do it.
  • ajlyon
    Can you give an example URL for the HighWire 2.0 errors like "match is undefined"? That section of the translator is known to need special-casing for certain journals; I'm sure we're just missing some of the journals that should be there.
  • ajlyon
    Not sure what happened, but the bars all went red, and the entire repo is listed as having been updated at 2012-01-11 08:15:00.

    I got spooked and thought it might have been me, but I'm pretty sure that isn't something I did; my last commit was at 8:10 UTC, and it looks clean.
  • dstillman
    Yikes. Well that's bad. (This is why I had originally had protection against the post-commit hook updating more than 10 or so translators.) I'll look into what happened, but I've disabled repo updates in the meantime.
  • dstillman
    OK, so it looks like there was an S3 access failure during the post-commit update, and this triggered updating of all the translators. I've changed it to bail instead on an S3 failure, and I've reset all translators in the repo to their stored timestamps.

    The error list will continue to show most as red, since the timestamps in the pushed translators are set to the next five-minute mark from the commit time, meaning that the timestamps in the error reports won't match the timestamps now in the repo. As new versions of those are pushed, the red should fade out.
  • adamsmith
    Now that we have automated translator tests running well (yay for Simon), how about replacing
    http://www.zotero.org/translators/
    with something from here
    http://zotero-translator-tests.s3-website-us-east-1.amazonaws.com/
    - daily, weekly, whatever works.
  • dstillman
    What did you have in mind? We can have that URL just redirect there, but we'd probably want to make the translator test page a bit more user-friendly. Or did you mean parse the results and generate a similar list to what's on there now?
  • adamsmith
    I think the translator tester site is great, actually.
    We could add a short paragraph of explanations at the top, but otherwise I think just having that site visible should be great - users can see which translators are supposed to work, they see the tickets, the color-coding makes it easy to run through the list, I don't see why this isn't user friendly.
  • RintzeRintze
    Dan, maybe you could just have http://www.zotero.org/translators/ redirect to http://www.zotero.org/support/translators ? Then Avram/Sebastian/others can reorganize the latter page and link to the translator status page.
  • dstillman
    That works. Done.
  • adamsmith
    @Dan - thanks, I'll try to get to this soon.

    I would still really like an example URL for and APA Psycnet failure - that's consistently up there with failures.
    Also, there appears to be a major problem with the SpringerLink translator I just put up - could I get a sample URL for failure there, too?
  • dstillman
    edited March 7, 2012
    Here's a SpringerLink one:

    http://www.springerlink.com/content/1rbqbf97y9xhyrw3/

    Edit: That works for me, though. Maybe only works with Guest Access?
  • dstillman
    APA examples:

    http://psycnet.apa.org/journals/xlm/38/2/376/
    http://psycnet.apa.org/psycinfo/1939-00056-000

    But these work for me too.
  • adamsmith
    thanks - I'll try to see if I can figure something out- I tested SpringerLink logged in mainly.
  • RintzeRintze
    edited March 7, 2012
    http://psycnet.apa.org/psycinfo/1939-00056-000 failed for me once, but saved on the second and third try (Google Chrome, Zotero Standalone 3.0.3). Not sure what was going on (pretty sure the page had completed loaded).
  • adamsmith
    a first draft is now up at http://www.zotero.org/support/translators
    I want to make this prettier with time and include an snippet and explanation of the automatic list, but any general comments would be welcome.
  • aurimas
    This might be a pretty dumb question and everyone else seems to understand this, but...

    1) What is red vs yellow?

    2) What does the asterisk indicate (i.e. the one next to Google Scholar)


    Lastly, I can see that since Google Scholar has been updated we already have a couple errors coming up. "Error: Translator called select items with no items" Could you post a couple links that are triggering this?
  • ajlyon
    Red means that the errors are from a version older than the most recent. The asterisk, described in the hover text, means "Includes PDF metadata retrieval attempts".

    The vast majority of Google Scholar errors are from PDF lookups, not from ordinary use of the site.
  • adamsmith
    1) red are translator versions that are not up to date (that's why errors for recently changed translators are all in red - you'll soon see a separate yellow GS bar appearing).
    2) the GS asterisk means that it includes failed retrieve metadata.

This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.

Sign In or Register to comment.