The Codemeta standard based on Schema.org is supported both SWH, Zenodo and InvenioRDM as a common metadata exchange format. Further, InvenioRDM registers DOI via DataCite and thus provided DataCite metadata format as an exchange format for repositories and aggregators
Supported terms
The following Codemeta terms have existing fields in InvenioRDM or requires only minor adaptions to be supported:
downloadUrl
fileSize
releaseNotes
author
citation
contributor
copyrightHolder
copyrightYear
creator
dateCreated
dateModified
datePublished
editor
fileFormat
funder
keywords
license
producer
provider
publisher
sponsor
version
isAccessibleForFree
isPartOf
hasPart
position
description
identifier
name
sameAs
url
relatedLink
givenName
familyName
affiliation
identifier
name
maintainer
embargoDate
funding
referencePublication
readme
The following Codemeta terms requires new fields:
codeRepository
programmingLanguage
runtimePlatform
developmentStatus
operatingSystem
The following Codemeta terms will not be supported:
targetProduct
applicationCategory
applicationSubCategory
installUrl
memoryRequirements
permissions
processorRequirements
softwareHelp
softwareRequirements
softwareVersion
storageRequirements
supportingData
email
address
softwareSuggestions
contIntegration
buildInstructions
issueTracker
SWH ID
InvenioRDM must also be able to store a Software Heritage Identifier (SWH ID). The SWH ID will be a fully system managed property that users will not be able to edit. The identifier will be managed using InvenioRDM's internal persistent identifier management system which further enforces that we cannot store duplicate SWH ID's.
Codemeta for interoperability
The Codemeta standard based on Schema.org is supported both SWH, Zenodo and InvenioRDM as a common metadata exchange format. Further, InvenioRDM registers DOI via DataCite and thus provided DataCite metadata format as an exchange format for repositories and aggregators
Supported terms
The following Codemeta terms have existing fields in InvenioRDM or requires only minor adaptions to be supported:
downloadUrl
fileSize
releaseNotes
author
citation
contributor
copyrightHolder
copyrightYear
creator
dateCreated
dateModified
datePublished
editor
fileFormat
funder
keywords
license
producer
provider
publisher
sponsor
version
isAccessibleForFree
isPartOf
hasPart
position
description
identifier
name
sameAs
url
relatedLink
givenName
familyName
affiliation
identifier
name
maintainer
embargoDate
funding
referencePublication
readme
The following Codemeta terms requires new fields:
codeRepository
programmingLanguage
runtimePlatform
developmentStatus
operatingSystem
The following Codemeta terms will not be supported:
targetProduct
applicationCategory
applicationSubCategory
installUrl
memoryRequirements
permissions
processorRequirements
softwareHelp
softwareRequirements
softwareVersion
storageRequirements
supportingData
email
address
softwareSuggestions
contIntegration
buildInstructions
issueTracker
SWH ID
InvenioRDM must also be able to store a Software Heritage Identifier (SWH ID). The SWH ID will be a fully system managed property that users will not be able to edit. The identifier will be managed using InvenioRDM's internal persistent identifier management system which further enforces that we cannot store duplicate SWH ID's.
https://wiki.eduuni.fi/display/cscRDIcollaboration/InvenioRDM+-+SWH+SPECS