please add SciCrunchRegistry crosswalk file about codemeta HOT 6 CLOSED

Hello,

Could you send a pull request?

Also, a few needed changes:

• Keep the header of the first column as-is ("Property")
• add the name of the vocabulary as the header of the second column
• Keep the last four rows empty

from codemeta.

from codemeta.

I am not allowed to upload my csv file to the git repo (permission issue?) for some reason

That's what pull requests are for: https://docs.github.com/en/repositories/working-with-files/managing-files/adding-a-file-to-a-repository

but sure, I can upload it myself once the crosswalk is ready.

Please note, there are multiple columns that match some of the codemeta elements, so I made them into a comma separated list. If there is a better delimiter, please let me know.

Use a /

I still wish that I could have used this: https://codemeta.github.io/codemeta-generator/ to do the crosswalk.

This is to write codemeta.json files, which is rather different from crosswalk editing.

For the field labelled "has part" we have a set of relationships that we use, some of them are has part, but others are in there too. There are 13 relationships including recommends, lists, related_to, duplicate, has_grant, has_plugin, has_organizational_facet and others. How do you want to handle that? has_part is in the list, so I added it, but what will this do if the relationships are more complex?

None of the ones you listed sound like they are part of the software (except maybe plugins). We have the funding property for grants, but I don't think the others have a corresponding codemeta property.

from codemeta.

from codemeta.

Yes this is the issue, we have a set of these relationships in the field,
some are relevant and some are not relevant. So I could not map this or I
could map it and risk having irrelevant values.

The sciscunch registry covers much more than software tools so
relationships for repositories will not come into play if we subset for
only software entities, but the allowed options are numerous. What is your
feeling about this in a crosswalk?

You definitely don't need to map all values from your vocabulary to Codemeta. Only the relevant ones.

The file is attached here.

I didn't get it (keep in mind this is a Github issue, not direct emails)

from codemeta.

from codemeta.