I take your point, but in that case I may be using references wrong (and have spent about 8 hours over the weekend destroying information in my Rich Text fields!). I’ve been using references as “magic” replacements for existing entities: so for example a Task’s Details field might have contained:
… explore using Kibana as a front-end for OpenSearch using SAML authentication…
and if I searched for “Kibana” then that Task would show up, and I’d see that contextual snippet with highlighting:
… explore using Kibana as a front-end for OpenSearch using SAML authentication…
which was perfect. But now I’ve rewritten that Task’s Details field so it contains:
… explore using [T] Kibana as a front-end for [T] OpenSearch using [T] SAML authentication…
ie. the entites are still present (“Kibana”, “OpenSearch”, “SAML”) but now they’re References to actual fibery Entities (Tags in this case) rather than plain text. This is still perfectly readable, but it’s also great as far as the References go (I can easily pull up a list of all Tasks that Reference Kibana for instance), but now when I search for “Kibana” (or “OpenSearch” or “SAML”) I no longer see that Task showing up in my search results: it’s effectively invisible to searching. (I can still find it, but only by going to the Referenced “Kibana” (Tag) Entity view and scrolling through the list of back-references: and at that point I no longer see the contextual snippets or keyword highlight, so it’s a lot more opaque than the search process used to be.
If I had to choose between plain text (“Kibana”, “OpenSearch”, “SAML”) and References ([T] Kibana , [T] OpenSearch,[T] SAML) then at this point I would choose plain text, because as useful as the References are, search is even more useful. But that would mean spending another 8 hours rewriting 190 Tasks’ Details to replace all the References with plain text: I dread doing that! What would be much better would be (maybe an option?) so that search can be told to include the names of References in its index. That would give me the best of both words: I could still search my Tasks for these entities, but I’d still keep the awesomeness of having them encoded as References. I hope that might be possible!
I guess a workaround would be to expose each entity in plain text and as a Tag Reference; something like this:
… explore using Kibana ([T] Kibana) as a front-end for OpenSearch ([T] OpenSearch) using SAML ([T] SAML) authentication…
but that would be very ugly and hard to read (and time-consuming and error prone) so if I can’t configure fibery to treat these References as searchable replacements for the plain text words then I’ll have to convert them all back to plain text again, which would be a shame.