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
C. Places where the org name/ID is displayed, e.g. (5), should link to the org page.
D. The org page should be visually consistent with the rest of the front-end, i.e. the stock image (4) should not appear.
The text was updated successfully, but these errors were encountered:
As part of the data population sprints, I am noticing URLs like: https://portal.transport-data.org/@slocat/transport-knowledge-base-all-slocat
Some related things I've observed:
/@slocat/
as a path component, sometimes/SLOCAT/
, e.g. as in https://portal.transport-data.org/SLOCAT/transport-knowledge-base-all-slocat. It is not clear whether both always exist, or sometimes only one or the other.I think we expect that:
A. There is only one, canonical URL for each organization and each CKAN dataset.
@
prefix, as this is easiest to type. Example: https://portal.transport-data.org/org or https://portal.transport-data.org/org/fooB. Access from other URLs aliased to (A) leads to the canonical URL being displayed in the browser address bar. That is:
C. Places where the org name/ID is displayed, e.g. (5), should link to the org page.
D. The org page should be visually consistent with the rest of the front-end, i.e. the stock image (4) should not appear.
The text was updated successfully, but these errors were encountered: