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
Mainly logging this here for future thinking/so it doesn’t get lost…
This is related to the idea that the URL of a “page” might shift over time. Are there other ways we might want to connect pages together over time without necessarily calling them the same, both in the the UI and in the data?
The https://www.epa.gov/statelocalclimate → https://www.epa.gov/statelocalenergy shift is a good real-world use case for thinking about this.
The text was updated successfully, but these errors were encountered:
We'll need to think about this as a best-effort designation, as it's subject to judgement calls and ultimately serves the purpose of making changes comprehensible to humans.
Here's a thought: a given Page only ever has one URL, but it may reference a "parent" Page. I like this solution because it allows for a Page to have multiple "children". For example, an EPA Page from 2016 might have one child in https://19january2017snapshot.epa.gov/ and another in https://www.epa.gov/
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.
Mainly logging this here for future thinking/so it doesn’t get lost…
This is related to the idea that the URL of a “page” might shift over time. Are there other ways we might want to connect pages together over time without necessarily calling them the same, both in the the UI and in the data?
The
https://www.epa.gov/statelocalclimate
→https://www.epa.gov/statelocalenergy
shift is a good real-world use case for thinking about this.The text was updated successfully, but these errors were encountered: