softwarepub / hermes

Implementation of the HERMES workflow
https://docs.software-metadata.pub
Other
21 stars 6 forks source link

Document processors to pass on all available metadata #121

Open sdruskat opened 1 year ago

sdruskat commented 1 year ago

The current processors (as of https://github.com/hermes-hmc/workflow/commit/f02ff2a2b7a9ea2b2dd278fd9c0c0b827ac41bbc) don't process all metadata available in the harvesting contexts.

Examples for this are

This is of course bad 💀, and should be fixed for the existing processors.

Additionally though, and this is the scope of this issue, we shuold document how to extend hermes for a new datasource, and include the information that per default (unless configuration says differently), all metadata should be passed on to the CodeMetaContext (currently used for processing output).

led02 commented 9 months ago

This issue seems a bit superseded. E.g., there is a CodeMeta harvester available…

However, we still need to collect everything but we should also explain, how and where to store the data.

See also #153