Change Details

When depositing in SWH a directory with the content and a revision with the metadata are created. There is no notion of release. When pointing to SWH from Wikidata we can only use the `swh:1:rel:<id>` property. We wish for T1752 to have links from software entities in Wikidata to software releases archived in SWH. On the other hand, not all deposits need a release. This is why only deposits with `releaseNote` are concerned and the entry for this metadata should be the message of the release.

When depositing in SWH different software artifacts are created to ingest the content and metadata of the deposit. `origin`- `snapshot `-`HEAD` branch- `revision` with metadata- root `directory`- `content` At present, there is no notion of `release`, but the deposits from HAL are in fact releases. On the other hand, not all deposits need a release. This is why only deposits with `releaseNotes` and `softwareVersion` are concerned and the entry for this metadata should be the message of the release. Here is the mapping table between terms and SWH release fields: | **Metadata term ** | **Fallback value** | **SWH release field** | **Description** | | X | X | target | revision containing all metadata| | X | X | target_type | hard-coded: 'revision' | | softwareVersion | X | name | release name if any | | releaseNote | X | message | release message if any | | datePublished |deposit_date| date | publication date | One use case for the releases is with using Wikidata identifier on HAL deposits. When pointing to SWH from Wikidata we can only use the `swh:1:rel:<id>` property. We wish for T1752 to have links from software entities in Wikidata to software releases archived in SWH.

When depositing in SWH a directory with the content and a revision with thedifferent software artifacts are created to ingest the content and metadata are createdof the deposit. T`origin`- `snapshot `-`HEAD` branch- `revision` with metadata- root `directory`- `content` At present, there is no notion of `release`, but the deposits from HAL are in fact releases. On the other hand, not all deposits need a release. When pointing to SWH from Wikidata we can only use the `swh:1:rel:<id>` property.This is why only deposits with `releaseNotes` and `softwareVersion` are concerned and the entry for this metadata should be the message of the release. Here is the mapping table between terms and SWH release fields: | **Metadata term ** | **Fallback value** | **SWH release field** | **Description** | We wish for T1752 to have links from software entities in Wikidata to software releases archived in SWH.| X | X | target | revision containing all metadata| | X | X | target_type | hard-coded: 'revision' | | softwareVersion | X | name | release name if any | | releaseNote | X | message | release message if any | | datePublished |deposit_date| date | publication date | On the other hand, not all deposits need a releaseOne use case for the releases is with using Wikidata identifier on HAL deposits. This is why only deposits with `releaseNote` are concerned and the entry for this metadata should be the message of the releaseWhen pointing to SWH from Wikidata we can only use the `swh:1:rel:<id>` property. We wish for T1752 to have links from software entities in Wikidata to software releases archived in SWH.