Allow porting datasets with custom API Endpoint Resource Names #209
Description
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.