search

proycon / codemeta-harvester

Harvest and aggregate codemeta/schema.org software metadata from source repositories and service endpoints, automatically converting from known metadata schemes in the process
GNU General Public License v3.0
8 stars 4 forks source link

Is services still needed in the config? #13

Open ddeboer opened 1 year ago

ddeboer commented 1 year ago

I’m somewhat confused about the services property in the harvester config vs. targetProduct in the codemeta.json file. Which is preferred? Do we need both?

proycon commented 1 year ago

The services property in the harvester config translates, after harvesting, to a targetProduct in the resulting codemeta.json. I

If you can include a targetProduct in your codemeta.json, then that is of course perfectly fine and you do not need services in the harvester config. The reason services exists is because there is often a separation between the producer of the tool and the provider of a service: the tool producer can't always know where his/her tool is deployed, so can't include that in the software metadata (nor might it always be desirable to list all SaaS instances in the source code metadata).

At the CLARIAH level, however, we have some oversight and we can 'glue' source code to the instances where they are deployed, and let the harvester do the job.