Topics/keywords

[maelle]

Taking the discussion from #152

So now we have create_codemeta do

Repo topics to codemeta.json as keywords (when there's a GitHub repo)
DESCRIPTION schema.org stuff including keywords to codemeta.json

Repo topics are great because suggestions and bc they are useful per se not only for codemeta.json.

Do we want to make sure repo topics include all schema.org keywords from DESCRIPTION and vice versa? Like a sort of sync_topics function?

Cc @cboettig @sckott @katrinleinweber

[maelle]

For my own repos I wouldn't care about having the repo topics as schema.org keywords in DESCRIPTON, because even if I moved the repo somewhere else, I'd have the topics in codemeta.json and could re-populate the new platform thing (say, GitLab tags if that exists) from codemeta.json.

[katrinleinweber]

Any guesses about the chances of GitLab importing GitHub topics as tags being higher or lower than them importing something from any kind of metadata file?

[katrinleinweber]

I would advise against syncing, but rather nail down one direction for the flow of the data/topics/keywords. Topics should be the point of entry, IMHO, not an end-point.

[maelle]

They just need to be filled from schema.org DESCRIPTION keywords from repos who are in that situation maybe (i.e to make the most of Scott's efforts for instance)