Report ID 439393759

Chorsh
Hello

When I was trying to sync my data this error appeared 439393759. and I cannot sync my data. I am not seeing the online when I log in to another PC.

Thanks
  • dstillman Zotero Team
    First name '[...]' too long
    Search for the item with the (malformed) name in the error message and correct the name. You should also tell us where the item came from so that we can fix the import translator if necessary.
  • adamsmith
    @Dan - I want to write a kb article on this - preferences on title/URL?
  • dstillman Zotero Team
    Let's hold off. I'm changing the server to send a much clearer error message.
  • dstillman Zotero Team
    Though the error message could link to a KB article that went into more detail about reporting it, etc., but we can't (in the current version) make the link clickable anyway, and maybe the clearer error message will be sufficient.
  • dstillman Zotero Team
    We need a better fix, though. Saving >255 characters to the Extra field, with "Truncated Author: [name]" on its own line? (Or "Truncated Editor", etc.)
  • adamsmith
    I've been wanting to fix this for a long time. Argument against has always been that it's an indication of a translator not working right - which is true, but I'd still be for fixing this.
    It would be more in line with similar import behavior to put this in a note, but given sync behavior extra might be better?
  • dstillman Zotero Team
    Don't we put extra import fields into Extra now anyway? (Or did we just discuss that?)

    Given sync and UI issues (people get annoyed by the extra notes), Extra is probably the right place for these sorts of things.
  • dstillman Zotero Team
    And we could potentially send translator error reports for these things. I don't think we currently have the capability to send non-fatal reports, but it'd be handy for this and probably other things.
  • adamsmith
    we just discussed that - currently it's still going in notes. The main thing that I remembered from that discussion was that we wanted to turn the default for that behavior to off (which also still hasn't happened). The main advantage of notes is that they're easy to find because they can be tagged separately (as we do).
  • aurimas
    Idk how this would go along with Zotero's privacy policy (should be ok), but we could detect this on import from web translators and send it as an error to zotero.org (without actually breaking the import). Would be much more useful than having an occasional user report the error.

    As far as fixing this goes, for web translators, I guess we can just drop the overflow, since supposedly the data is poor anyway and the user can presumably always go back to the website to check the proper metadata. For import translators, idk... could trim it and throw the original into the same note that we're attaching now for unmappable fields (except this error would probably not be toggleable via hidden pref)
  • dstillman Zotero Team
    For the time being:
    The name ‘Test test test test test test test test test test …’ is too long to sync.

    Search for the item with this name and shorten it. Note that the item may be in the trash or in a group library.

    If you receive this message repeatedly for items saved from a particular site, you can report this issue in the Zotero Forums.
    Let's start truncating these for web translators and, if possible, send non-fatal error reports.

    Adding these to the same note for import sounds good.
  • aurimas
    edited April 15, 2014
    We should also make a clickable link to select the item in question. (Or just automatically select it)
  • dstillman Zotero Team
    Can't do that currently. In classic sync creators can be saved independently of items. With API syncing we'll be able to do that.
  • adamsmith
    Let's start truncating these for web translators
    what's the exact limit we should impose to keep sync running? Is it 255 chars for each firstName and lastName?

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.