I need to check if chemical names occur in e.g. blacklisted Lists.
You can image that it is a no-go if I can’t just copy-and-past e.g. “6,10,14-Trimethylpentadecan-2-one”
I will get “6”, “10”, “14-Trimethylpentadecan-2-one”. Without an option to ignor the commas, unfortunately Fibery will not fit my use case. Otherwise it is perfect.l
Are the names in quotes?
I put the quotes in place for better readability. No quotes normally occur.
Given that Fibery treats commas as delimiters when pasting into fields that can accommodate multiple entities, I’m not sure it could be made to ‘ignore’ commas, otherwise it wouldn’t support cases where it is desirable to create/link to multiple entities.
How exactly are you trying to copy-paste? Is 6,10,14-Trimethylpentadecan-2-one being pasted into a name field, or a relation field, or …?
use case is to put e.g.
2,5-XYLENOL
2,6-XYLENOL
3,4-XYLENOL
etc. …
in a Relation Field Column (this can be several thousand entries long).
I can enter above chemicals one-per-one in a Relation Field Column (via pressing Enter and pasting).
However, use of the database is to check columns with many entries at once (saving alot time).
I understand that the comma separation is there for a reason. Is there a way to bypass this?
Is there any update on how to paste something like this into a relation field that allows multiple entities?
I tried using brackets, which seems to be the “escape” character in formulas when your field reference has more than 1 word. But that doesn’t work. I still generate two entities if I’m typing “Fibery, LLC” without the quotes. Using quotes doesn’t work as an escape character either.
I’d be open to having formula-named entities that always force the escape characteres on the front and back of my entity names, if it meant I could paste these names without splitting into multiple pieces.
Nothing to report
Hello everyone. I see two possible solutions:
- Allow selection of custom entity separator upon import, e.g. semicolon, comma, even a custom character.
- Implement some kind of escaping e.g. , but I would still allow escaping to be disabled upon import for edge cases where someone would need to import an entity ending in the escape character.