You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
@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.
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 wheresites.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
The text was updated successfully, but these errors were encountered: