Once we have well-defined external identifiers pointing into the archive (T335), the Web UI will need to be able to resolve them, ideally, as a simple redirection.
Example (tentative, as the final identifier scheme isn't finalized yet):
| rDWAPPS Web applications | |||
| rDWAPPS2290aab734d8 browse: Support resolution of SWH persistent identifiers | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Migrated | gitlab-migration | T926 Web UI: support resolution of external pointers into the archive | ||
| Migrated | gitlab-migration | T335 specify the URI scheme swh:... to point to software heritage objects |
For the deposit and the CCSD we have agreed on this url:
archive.s.o/browse/revision/swh-id?origin_type=type&origin_url=url
will it be possible to have the optional params with the new url?
@moranegg's question is most likely for @anlambert, but FWIW it would in no way break the proposal here.
As per URI semantics, one can always add a trailing ?foo=bar to any URL, and it'd make sensible to do so here.
@moranegg the resolution of swh persistent identifiers is now implemented in browse and deployed to production. Query parameters used in the previous URI scheme are of course supported (for instance: https://archive.softwareheritage.org/browse/swh:1:rev:ed823693404f87d3077daaa55643a1b41f06ba35/?origin_type=deposit&origin_url=https://inria.halpreprod.archives-ouvertes.fr/hal-01588942).