Add some aliases for Vera C. Rubin Observatory telescopes

[timj]

Following on from #139 add some aliases for Simonyi Survey Telescope and Rubin Auxiliary Telescope.

Fixes #139

[hamogu]

Would it be possible to not change the primary key? It's a list of observatories or telescopes, so the fact that it's a "tel" is implied, I think. We can have as many aliases as make sense, but we shouldn't change the primary key unless it's absolutely necessary.

[timj]

Ok. Reverted. I changed it because no-one at Rubin calls it this and everyone calls it auxtel.

[timj]

Presumably you want me to revert the rubin -> rubin_simonyi key change as well then?

[hamogu]

Yes, I think that would be nice. People think of the "Rubin" as the main telescope of the observatory. That's probably not correct, but so common, that it might be OK to keep that as key. People using this from astropy as intended won't know the difference (if it's an alias they are searching for or the main key), but it's a public json file and we don't know who else uses it for what purpose, so better to be careful.

Thanks!

[timj]

Done.

[hamogu]

Thank you so much. This database works because people like you put the correct information in one-by-one. It's not perfect, but getting better every time. Thanks!

[gpdf]

I'm uncomfortable with how this ended up. There is a canonical name, and that name is used in the AAS and will be used throughout IVOA services, the IVOA Registry, and a number of other places like publications databases. I certainly support having informal aliases to make it easier for people to find without knowing the exact formal spelling, but the data model should be that the aliases are linked to the canonical name, so that the canonical name can be looked up and then used to perform searches on other services.

[hamogu]

Well, @gpdf, how would you like it to be then? If you feel strongly, as a Rubin insider, that the names should be listed in some specific way, I am happy to do that. I said "we shouldn't change the primary key unless absolutely necessary" and nobody above argued that it gets to the level of "necessary".

We don't want to potentially break backwards compatibility unless there is a very good reason - but if there is a very good reason like the one you laid out, we can do that.
So the question is: Are you just "uncomfortable" as in "unhappy" or are you "uncomfortable" as in "this will lead to all sorts of problems going forward"?

[timj]

I picked the actual telescope name as the name because it's the name of the telescope and this file doesn't even seem to try to use the AAS facility names. I did add the AAS name as an alias but I felt that it didn't make sense as the primary name if we weren't using the AAS names consistently.

[pllim]

will be used throughout IVOA services, the IVOA Registry

Should this be discussed with PyVO or astroquery developers, as they are most likely to be impacted as well?

[bsipocz]

This is 100% user-facing rather than affecting developers, so I don't think astroquery/pyvo needs to chime in here.
(we don't even use EarthLocations in pyvo, and it's only used for the mpc module for astroquery, but even there it's a user input, so whatever they pass on will be used for the query)