-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support notation
and keywords
fields for spaces/properties?
#159
Comments
About the |
I don't recall offhand the example, but there was some situation where a user was typing something that wasn't quite in one of our given aliases, but was reasonable. We may have even added an alias that was basically the same as another alias or the main name, but used that conjugation of the word so it'd show up in search. |
Seems worth an item for the next zoom meeting |
Along the same line, we can discuss the use of "convenience aliases" for use in the search box in Explore. These are not meant as real aliases as attested in the literature, but more a convenience when doing manual searches. Examples: "T3" for |
Yeah, I think this is all the same thing: strings that should trigger results in search, but don't need to be displayed on the site. |
notation
field for spaces/properties?keywords
field for spaces/properties?
|
keywords
field for spaces/properties?notation
and keywords
fields for spaces/properties?
Decided not to veer pi-base/data#657 off-topic.
Once upon a time I pushed for non-mathematical names for our spaces. Now I'm wondering if I had it backwards: as the pi-base goes deeper into the weeds, we're going to wind up with more examples that don't have names besides maybe "Example x.y.z". But usually there's some kind of notation that could be used to describe these. So maybe...
And then we start displaying something like
And maybe only one of notation or name is required, displaying
or
if the other is missing.
I'm also curious what @awswan and @lunar-starlight think over at the topos fork.
The text was updated successfully, but these errors were encountered: