This is going to be implemented in swh-web, so we should codify this,
for implementations that want to be 'quirk-compatible' with ours.
As agreed in T3234.
Differential D5485
docs/persistent-identifiers: Add guidelines for fixing invalid SWHIDs. vlorentz on Apr 12 2021, 4:46 PM. Authored by
Details
This is going to be implemented in swh-web, so we should codify this, As agreed in T3234.
Diff Detail
Event TimelineComment Actions Build is green Patch application report for D5485 (id=19616)Rebasing onto f2dba177ad... Current branch diff-target is up to date. Changes applied before testcommit fab4f35044cdb5f3a90a50147ab41370f3806d42 Author: Valentin Lorentz <vlorentz@softwareheritage.org> Date: Mon Apr 12 16:46:10 2021 +0200 docs/persistent-identifiers: Add guidelines for fixing invalid SWHIDs. This is going to be implemented in swh-web, so we should codify this, for implementations that want to be 'quirk-compatible' with ours. See https://jenkins.softwareheritage.org/job/DMOD/job/tests-on-diff/309/ for more details. Comment Actions Build is green Patch application report for D5485 (id=19617)Rebasing onto f2dba177ad... Current branch diff-target is up to date. Changes applied before testcommit 81a810d17d92b991301423b0e7e99d15b2ffd957 Author: Valentin Lorentz <vlorentz@softwareheritage.org> Date: Mon Apr 12 16:46:10 2021 +0200 docs/persistent-identifiers: Add guidelines for fixing invalid SWHIDs. This is going to be implemented in swh-web, so we should codify this, for implementations that want to be 'quirk-compatible' with ours. See https://jenkins.softwareheritage.org/job/DMOD/job/tests-on-diff/310/ for more details. Comment Actions I think we should rather encourage to validate input SWHIDs and report errors instead of automatically fixing them, We could point to the adequate function and classes in swh-model to do that in Python code. For frontend code, we could create a small npm package to validate a SWHID. |