open-traits-network / open-traits-network.github.io

Open Traits Network Registry and Website
https://opentraits.org
13 stars 54 forks source link

I'd like to ... think how to make the 10 rules alive #242

Closed caterinap closed 1 year ago

caterinap commented 1 year ago

Hi!

How to encourage the scientific community (and ourselves) to update the 10 rules when new tools / field practices appear?

The idea would be to write in the paper something like that "We encourage the scientific community to update these rules when new tools and practices emerge. This is possible at the following web page: http://opentraits.org/lifecycle.html"

But then what should we put on the webpage? The full paper? Rule titles and subtitles + bullet points?

Any ideas are welcome!

bmaitner commented 1 year ago

I think this is a great idea. If the licensing permits it, I'd vote for including the full paper. That way all the text is there to edit and update as new best practices emerge. The other kind of nice thing here is that the full rationale for our updates and changes will be preserved in the comments and pull requests.

jhpoelen commented 1 year ago

@caterinap @bmaitner I am also in favor of putting all the rules up there and turn the paper into a living document.

Perhaps we can update the name of the page to be more descriptive . . . like "best practices" or "publishing traits" or "how-to" .

Curious to hear thoughts.

caterinap commented 1 year ago

@jhpoelen, a more descriptive title is good idea. I like "best practices" because it captures better the whole cycle ("how-to" is maybe too generic). @bmaitner I agree, including the full paper would be the easiest. I am sure what we will be allowed to do and if we can choose which CC license we want (MEE website, Wiley policy). There is also maybe a 12 months embargo before putting the accepted version online. Maybe we can ask the editor directly.

bmaitner commented 1 year ago

@caterinap , good idea, I think asking the editor is probably the best option. If there is an embargo on the accepted version, presumably in the interim we can post the preprint version (and maybe include a link to the accepted version?)

jhpoelen commented 1 year ago

ok, so rename page to "best practices" and shove the pre-print on there in markdown ?

bmaitner commented 1 year ago

@jhpoelen that sounds good to me

jhpoelen commented 1 year ago

@caterinap or others - do you agree?

jmadin commented 1 year ago

I think it’s a great idea.

On Oct 6, 2022, at 7:15 AM, Jorrit Poelen @.***> wrote:

@caterinap https://github.com/caterinap or others - do you agree?

— Reply to this email directly, view it on GitHub https://github.com/open-traits-network/open-traits-network.github.io/issues/242#issuecomment-1270429722, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBIZMFCM72IHPXE3UOFOTDWB4CMVANCNFSM6AAAAAAQ4SUWSI. You are receiving this because you are subscribed to this thread.

jhpoelen commented 1 year ago

I took the liberty to rename the lifecycle page to best practices as suggested.

image

Can someone else copy / paste the article into the best-practices.md file?

https://github.com/open-traits-network/open-traits-network.github.io/edit/master/best-practices.md

Thanks!

caterinap commented 1 year ago

I also agree! I asked the original Word file to Alex and checked if he agrees as well.

chiras commented 1 year ago

Work in progress: https://github.com/open-traits-network/open-traits-network.github.io/tree/best-practices