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
Note that this will require moving all submissions that are under that Place (ie Comments, Supports, etc) to a new Dataset as well, if needed. Ideally, we'd have a batch operation for this.
Also, it may change the url of the place too. How should we deal with that? For example, if we have a Place under heyduwamish.org/reports/123 and move that place to a DuwamishFeatured dataset, our client would route it under heyduwamish.org/123 or heyduwamish.org/featured/123. This will break existing links. So how should we handle this?
The text was updated successfully, but these errors were encountered:
One way we can get around changing links is to take advantage of the "landmark-style" url-title field. If the client loads a model with this field present, it will ignore the underlying slug/id url and use the value of url-title as the url instead.
But it's true that if a url-title field isn't present, changing datasets will probably break existing links.
Note that this will require moving all submissions that are under that Place (ie Comments, Supports, etc) to a new Dataset as well, if needed. Ideally, we'd have a batch operation for this.
Also, it may change the url of the place too. How should we deal with that? For example, if we have a Place under heyduwamish.org/reports/123 and move that place to a DuwamishFeatured dataset, our client would route it under heyduwamish.org/123 or heyduwamish.org/featured/123. This will break existing links. So how should we handle this?
The text was updated successfully, but these errors were encountered: