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

Allow porting datasets with custom API Endpoint Resource Names #209

Open
levyj opened this issue Oct 5, 2022 · 0 comments
Open

Allow porting datasets with custom API Endpoint Resource Names #209

levyj opened this issue Oct 5, 2022 · 0 comments

Comments

@levyj
Copy link
Contributor

levyj commented Oct 5, 2022

As discussed in https://support.socrata.com/hc/en-us/requests/52592 (for those with access), port jobs on datasets with the API Endpoint / Resource Name metadata field populated fail because they try to copy that value to the new dataset but it must be unique.

It would be great if that could be fixed somehow. Possibilities that occur to me:

  • Do not copy that metadata field.
  • Copy it but append a number to the end or otherwise change it in some manner.
  • Apply a completely different value, possibly the new 4x4, although that probably does not accomplish much.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant