Display aliases on Explore page

[StevenClontz]

See pi-base/data#792

[cloudflare-workers-and-pages]

Deploying topology with    Cloudflare Pages

Latest commit:	11f625c
Status:	✅  Deploy successful!
Preview URL:	https://0efbc844.topology.pages.dev
Branch Preview URL:	https://stevenclontz-explore-aliases.topology.pages.dev

View logs

[StevenClontz]

@prabau thoughts?

[StevenClontz]

[StevenClontz]

The fact "cantor space" doesn't show up first for "cantor" is addressed here: #178

[prabau]

The search filtering both by formula and by text does not work as expected. When searching for compact spaces related to "Cantor", one get things like S19, S20, which are compact but have nothing to do with "Cantor", even with fuzzy matching. It seems that there is a flaw in the algorithm here.

Even searching for "cantor" without specifying properties returns spaces like Euclidean real numbers, Irrational numbers, Altered long ray, etc that have nothing to do with "cantor", 43 spaces in total.

Ordering the results by closest match when searching by text does not seem a bad idea, but the problem above is much more serious and should be looked at.

Compare also with the search from the Spaces page:
https://topology.pi-base.org/spaces/all?filter=cantor
which gives the first best three matches in the right order, followed by irrelevant ones.

[prabau]

As for displaying the alias for spaces, would that apply only when filtering by text (with or without also filtering by formula)?
When not filtering by text, it's maybe preferable not to use it because it occupies more real estate and there is no need to. When filtering by text, it could be ok.

Another thing that the sample screenshot above points to is the inadequacy of many of the current aliases.
Just taking S36 (Successor to the first uncountable ordinal) as an example, we have aliases like "Omega1 + 1" and "ω_1 + 1" and ... Several of these aliases date from way back, when we could not render LaTex in aliases. But that has changed. Some of the other aliases may also be debatable.

I think it would be beneficial to discuss in general terms how to improve the aliases, and also the search issue above. A good topic for next zoom meeting.

[StevenClontz]

When not filtering by text, it's maybe preferable not to use it because it occupies more real estate and there is no need to.

I thought about this, but I still think that if we have relegated the name of a space to an alias that a user expects, it's still good to have it handy so they can quickly find a space they are familiar with, even if we use a different canonical name than they are used to.

inadequacy of many of the current aliases

Absolutely agreed - if we're going to display aliases this prominantly, we should also clean up some less-useful ones. I like discussing this next month.

[prabau]

I thought about this, but I still think that if we have relegated the name of a space to an alias that a user expects, it's still good to have it handy so they can quickly find a space they are familiar with, even if we use a different canonical name than they are used to.

Maybe. Although when you filter only by formula, you are interested in just a list of spaces matching the criteria. Then the user can just click on things that look interesting and they will find more detail of each space if they want to. It does not matter that the name is not the one they are used to. After drilling down, they will find more details. Anyway, we can discuss further in the zoom meeting.