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

Add AAS facilities keywords to site-data? #130

Open
hamogu opened this issue Dec 7, 2022 · 3 comments
Open

Add AAS facilities keywords to site-data? #130

hamogu opened this issue Dec 7, 2022 · 3 comments

Comments

@hamogu
Copy link
Member

hamogu commented Dec 7, 2022

Description

It might be neat to add the AAS facilities keywords to our sites.json. If I looked up a site in astropy, I would know how to add the correct facility to my article. I can envision further uses where sites.json could be used to add keywords to data downloaded through astroquery, but those are beyond the scope of this repro. If the data is here, others may find other uses.

While I got this idea from looking at the list of AAS keywords, we should add a more generic category to the database, e.g. {'journal keywords': {'AAS': keyword}} to make it extensible if we add others later. The AAS journals are the only ones with a system like that right now that I'm aware of, though.

Additional context

AAS journals facilities keywords: https://journals.aas.org/facility-keywords/
Maybe this could be done in collaboration with the AAS data editors? @augustfly

@pllim pllim changed the title Add AAS facilities kaywords to site-data? Add AAS facilities keywords to site-data? Dec 7, 2022
@augustfly
Copy link

So my input is that the website above ( https://journals.aas.org/facility-keywords/ ) is the central/original/only version of the facilities keyword list. Updates are done on that site, users filter that site to find facilities, etc. Because of our archaic storage mechanism, I would worry that someone would need to create a scraping mechanism to harvest and sync the results on that website with that list reused elsewhere. Or we (AAS) could try to create a parallel "version" of this list that could be reused (on GitHub for instance). So far we have never had interest at a level necessary to port/mirror this data elsewhere.

@keflavich
Copy link
Contributor

I don't mind writing a scraper (or teaching a student to). I suspect "archaic" means "slow to change" such that a scraper would break less often than a reusable duplicate data set.

@hamogu
Copy link
Member Author

hamogu commented Dec 8, 2022

@augustfly Do you ever remove or re-assign a keyword? I imaging that there are only additions, so the worst that happens if we scrape and mirror is that new keywords might be missing, but the information would never be wrong, only incomplete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants