Error when collection or tag name exceeds Notion length limit

[cleovalentine]

Error when collection or tag name exceeds Notion length limit

[Bachery]

Encountered same issue for Tags:

APIResponseError: body failed validation:
body.properties.Tags.multi_select[1].name.length should be <= `100`

I fix it by deleting the long tags manually

[SofiCourtney]

Hi! Oh, I see, because I had the file in multiple collections, it was causing the collections string to be too long. I couldn't change the 'main search' collections because that documents the lit review, but moved 'main search' into another library and that seems to have fixed it. Thank you!

[dvanoni]

Hi @cleovalentine, thanks for reporting this!

I believe what's happening here is that Notero is trying to sync a value for the Collections multi-select property that is longer than what the Notion API supports. This can happen if a Zotero item is nested in collections such that the concatenation of the collection names (joined with ▸) is longer than 100 characters.

For example, with the item in the screenshot below, we'll end up trying to create a multi-select option with the following name that ends up being 117 characters:

This name has 27 characters ▸ This name has 27 characters ▸ This name has 27 characters ▸ This name has 27 characters

Does this seem to describe what you have in Zotero? If so, a quick (though admittedly not great) workaround would be to either remove a layer of nesting in your collections or shorten the names of some of the collections.

For a proper fix, it looks like we'll need to truncate the value to at most 100 characters. I could add ellipses to the end of anything longer than 100 characters, but I wonder if it'd make more sense to add the ellipses somewhere in the middle since the end would be the most deeply nested collection and thus the most "precise" part of the name. Do you have any thoughts on that?

[SofiCourtney]

Hi! I'm having the same issue as @cleovalentine. I tried removing layers of nesting, and shortening the names of collections, but I'm still getting the same error (with the same amount of characters). Any clue what's going on here?

[dvanoni]

Hi @SofiCourtney! It sounds like you've done everything I'd suggest, so to help me figure out what's still going on I'll need to get some more logs from you.

If you're up for it, would you mind installing this test build that enables more logging and then send me a screenshot of the output in the error console when you try to sync an item? The below video shows how to find the logs in the error console.

Thanks!

CleanShot.2023-04-17.at.21.27.06-converted.3.mp4

[SofiCourtney]

Hi David Yes, I can do that, but I’m having a bit of an issue installing the test build- I expected there to be a .xpi file that I can add to zotero using the ‘add on’ menu. How do I install this version with the .rdf file? Thank you!

[dvanoni]

Hi @SofiCourtney, I forgot to mention that the test builds are named as .zip instead of .xpi, but they work the same way. Meaning, you don't want to extract the files from the .zip but instead install the entire .zip the same way you do with a .xpi.

Let me know if that works!

[SofiCourtney]

[dvanoni]

Thanks for sending that, @SofiCourtney! It looks like the collection that's causing trouble is the following:

Main search ▸ databases searched ▸ Natural Science Collection Search ▸ Abstract screen ▸ included ▸ fire

You'll need to either remove some nesting or shorten one of the collection names.

I hope to get a proper fix in for this soon, but let me know if you're able to work around it for now!

[SofiCourtney]

Hi, I did both shorten the collection names and remove nesting, before posting my issue here. This is what the file path has looked like throughout these attempts:

[dvanoni]

I see in your screenshot that the item being synced is in 5 different collections. I see that Full text ▸ fire is one of them, but it's the collections under Main search that appear to be causing the issue. Can you shorten the collections under Main search to see if that helps?