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

Implement functions for endpoint: Tags #25

Closed
3 tasks done
sboysel opened this issue Jul 12, 2018 · 2 comments
Closed
3 tasks done

Implement functions for endpoint: Tags #25

sboysel opened this issue Jul 12, 2018 · 2 comments
Assignees
Labels

Comments

@sboysel
Copy link
Owner

sboysel commented Jul 12, 2018

https://research.stlouisfed.org/docs/api/fred/#Tags

The following endpoints need to be implemented properly and consistently in fredr:

  • fredr_tags() - Get all tags, search for tags, or get tags by name. (Feature/function parameters (repo branch) #28)
  • fredr_related_tags() - Get the related tags for one or more tags.
  • fredr_tags_series() - Get the series matching tags.

The functions are to be implemented with explicit arguments for each parameter in the FRED API (see documentation for each endpoint and the discussion in #20).

@DavisVaughan
Copy link
Collaborator

I'll take this one

@DavisVaughan
Copy link
Collaborator

DavisVaughan commented Jul 14, 2018

Important note. The JSON example uses monetary+aggregates;weekly as the example. httr::GET transforms the + into %2B which the FRED API apparently does not accept. An alternative is to just use a space, monetary aggregates;weekly where the space turns into %20 which seems to be fine. I'm going to have a validation function that checks this.

https://research.stlouisfed.org/docs/api/fred/related_tags.html#tag_names

They actually even say:
"The '+' in 'monetary+aggregates;weekly' is an URL encoded space character."
so i feel okay with this

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

No branches or pull requests

2 participants