Resync crosswalks with the main repository.

[progval]

Applies the latest state of the master branch of the main repository (plus these PRs: codemeta/codemeta#237 codemeta/codemeta#238 codemeta/codemeta#239 )

[mbjones]

@amoeba I'm unsure, but I think this PR is reverting some of the work you did on consistently using schema:author over other contributor and creator fields. I suspect this is because we haven't been following a commit practice for releases, and so master no longer reflects the current release. @cboettig can you and @amoeba review to see if its ok to merge this?

[amoeba]

Hey @mbjones, from a quick scan, I think this is mostly fine. But I notice that, when I re-build the site today I get a larger (17 file) change set than in this PR so I'd be inclined to close this unmerged and update once we've resolved #32.

[progval]

@amoeba Which files are changed?

[amoeba]

Hey @progval, here's what I get: hugo...amoeba:hugo. I think the files you changed are changed in the same way as mine. Now that I look again, it looks like the changes I have that you don't are some sort of RMarkdown fluff that Blogdown added automatically. Sorry for not noticing that at my first look. Aside from the added <script> tags, are our changes effectively the same?

[progval]

In its currents state, it undoes some fixes made previously on the generated files. You should either apply codemeta/codemeta#237 + codemeta/codemeta#238 + codemeta/codemeta#239 to a local crosswalk.csv file and use it as input, or wait for them to be merged in codemeta/codemeta.

[progval]

And your branch is missing the changes in terms.Rmd

[amoeba]

Okay, thanks for taking a look @progval. I just scanned it more closely and I think it looks fine. I'd say this only depends on #32 now. Looks like we need someone to look at codemeta/codemeta#237, codemeta/codemeta#238, and codemeta/codemeta#239 too.

[moranegg]

Keeping this for after the #45 merge.