Skip to content
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

Open
StevenClontz opened this issue Jun 13, 2024 · 6 comments
Open

Support notation and keywords fields for spaces/properties? #159

StevenClontz opened this issue Jun 13, 2024 · 6 comments

Comments

@StevenClontz
Copy link
Member

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...

uid: S000101
notation: \omega^{\mathfrak c}
name: Continuum power of a countable discrete space
aliases:
  - Uncountable products of $Z^+$
keywords:
  - (any words that someone might reasonably use to find this space but didn't fit into notation/name/aliases)
counterexamples_id: 103 # (unused, probably should be deprecated anyway)
refs:
- doi: 10.1007/978-1-4612-6290-9
  name: Counterexamples in Topology

And then we start displaying something like

$\omega^{\mathfrak c}$ (Continuum power of a countable discrete space)

And maybe only one of notation or name is required, displaying

$\omega^{\mathfrak c}$

or

Continuum power of a countable discrete space

if the other is missing.

I'm also curious what @awswan and @lunar-starlight think over at the topos fork.

@prabau
Copy link

prabau commented Jun 13, 2024

About the keywords attributes, often a space can be determined, or at least the list of possible choices can be greatly reduced, by the properties of the space. This is already available via the Explore search box. There could be cases where keywords beyond properties of a space become useful. But before implementing this, I think it would be better to have some concrete examples showing the need for that feature.

@StevenClontz
Copy link
Member Author

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.

@prabau
Copy link

prabau commented Jun 15, 2024

Seems worth an item for the next zoom meeting

@prabau
Copy link

prabau commented Jul 28, 2024

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 $T_3$, "CG1" for $k_1$-space, "WLC" for weakly locally compact, etc. Possibly worth moving these out of aliases and into something like abbreviations:?

@StevenClontz
Copy link
Member Author

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.

@StevenClontz StevenClontz changed the title Support notation field for spaces/properties? Support keywords field for spaces/properties? Jul 29, 2024
@prabau
Copy link

prabau commented Jul 29, 2024

notation: seems slightly different, about a way to display things when something like {S101} is expanded in text?

@StevenClontz StevenClontz changed the title Support keywords field for spaces/properties? Support notation and keywords fields for spaces/properties? Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants