-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can one credit editors of posts on Rogue Scholar #767
Comments
Crossref metadata (used by Rogue Scholar for DOI registration) support the "editor" role. Crossref plans to support CRediT, which I would be happy to support in Rogue Scholar once available. RSS, Atom or JSON Feed don't support the concept of contributor roles. There are two possible solutions, similar to what we discussed with unsupported metadata before: a) custom extensions for JSON Feed, or b) extract the metadata from the full-text. @maelle are you interested in other contributor roles besides "editor" (not part of CRediT)? |
Thank you @mfenner!! At the moment I can't think of other roles. @yabellini @steffilazerte @mpadge do you think we'd need other new roles than editors for blog posts? |
@maelle here are the roles that commonmeta currently supports, from CRediT, DataCite and Crossref: https://github.com/commonmeta/commonmeta.org/blob/main/docs/commonmeta_v0.14.json#L417-L461 |
I can't think of anything other than Editor, thanks! |
OK. I would suggest a |
If I try and add editors data (for posts who have the info), what JSON field should I use to start with? Thank you and sorry for the delay. |
This is not specified in JSON Feed (or RSS, Atom), so a custom extension starting with an underscore makes sense. For example (for your next to last post, based on your front matter):
I assume that capitalization doesn't matter, so either "author" or "Author". "author" would be the default role if |
see #863 |
👋 @mfenner!
We've started crediting editors of blog posts using an "editor" YAML field. The editor(s) then appear(s) near the author(s): https://ropensci.org/blog/2024/05/17/communication-tips-oss-project/
Would such metadata have its place in the feed that Rogue Scholar uses?
The text was updated successfully, but these errors were encountered: