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

REFACTOR: revisit registry examples to explore other ways for servicetype aliases #130

Closed
bsipocz opened this issue Aug 16, 2023 · 2 comments · Fixed by #171
Closed

REFACTOR: revisit registry examples to explore other ways for servicetype aliases #130

bsipocz opened this issue Aug 16, 2023 · 2 comments · Fixed by #171
Labels
question Further information is requested

Comments

@bsipocz
Copy link
Contributor

bsipocz commented Aug 16, 2023

Registry searches currently support a few alias terms for servicetype, e.g. 'image' or 'spectra'. However, there is an ongoing discussion of deprecating these.
It would be extremely valuable to do an auditing of the suggested user workflow and whether any of the alternatives would make sense (IMO, I don't think it's realistic to request the beginner users we aim this workshop for to know anything about the individual protocols, especially their different version ,and do registry search for SIA, or SIA2, or SSA, etc.

xref: astropy/pyvo#429

@bsipocz bsipocz added the question Further information is requested label Aug 16, 2023
@tomdonaldson tomdonaldson assigned bsipocz and unassigned bsipocz Aug 16, 2023
@bsipocz
Copy link
Contributor Author

bsipocz commented Aug 16, 2023

One alternative could be: astropy/pyvo#470, we need to check on that from the end user POV

@tomdonaldson
Copy link
Contributor

Further philosophical reference: https://blog.g-vo.org/towards-data-discovery-in-pyvo.html

@bsipocz bsipocz linked a pull request Jul 31, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants