Change Details

Using the url: - archive.softwareheritage.org/browse/revision/<swh-id>?origin={<url>,<type>} View revision in the context of a deposit. A revision by itself on the web-app doesn't have context so we can't know if the revision was created from a deposit and the origin of that deposit. With the optinal parameters we can search rapidly the context of the revision and show it together with the revision metadata and target directory. so if the user on the HAL webpage cliked on the swh-id it shows him the revision page in context and not just a plain revision

Using the url https://archive.softwareheritage.org/browse/revision/<swh-id>?origin={<url>,<type>}, we can add context to the revision. A revision by itself on the web-app does not have context. As a result, we cannot know if the revision was created from a deposit or the deposit's origin. With those optional parameters, we can search rapidly the revision context and show it together with the revision metadata and target directory. So, in the end, when the HAL user clicks on the swh-id in the HAL webpage, that will open that revision page with the given context.

Using the url: - https://archive.softwareheritage.org/browse/revision/<swh-id>?origin={<url>,<type>} View revision in the, we can add context of a depositto the revision. A revision by itself on the web-app doesn' not have context so. As a result, we can'tnnot know if the revision was created from a deposit andor the origin of that depositdeposit's origin. With those optional parameters, we can search rapidly the context of the revisionrevision context and show it together with the revision metadata and target directory. so if the user on the HAL webpage cliked on the swh-id it shows him the revision page in context and not just a plain revision So, in the end, when the HAL user clicks on the swh-id in the HAL webpage, that will open that revision page with the given context.