Open maurolepore opened 7 years ago
Hi @maurolepore,
I can't really make the guide into a book chapter because I am having some trouble fitting the tables of information for the corals into one page. I actually had this same problem when I was developing the book in the beginning. My initial method was to manually type in the desired width of each table column so that they will all fit into a page without making the words too cramped. But that was taking too much time (because I'm not that affluent in R yet), so I basically used microsoft word to make the guide and converted that into PDF for the physical copy of the guide (the online version was made with Rmarkdown). So I'm sorry I can't do much here... But if you have any advice/tips, I'm happy to hear them and try them out.
Cheers, Melisa
On Tue, Jan 3, 2017 at 10:47 PM, Mauro Lepore notifications@github.com wrote:
Hi @odealab https://github.com/odealab and @melisacbl https://github.com/melisacbl,
Our next step, in my opinion, should be to do two things before the end of January (after, it is likely that I will no longer be in Panama):
(A) TIDY UP WHAT WE HAVE NOW
- polish the literature review (book chapter 1), which I plan to do for the backlight paper anyway
- transform the format of the guide to id corals (book chapter 2) to a book chapter sensu stricto.
(B) PLAN FUTURE WORK
- Perhaps, the content that is most urgently needed is the reference collection (book chapter 3). This we should think about this ASAP in case we want/can do something before the end of January.
- write the description of a project aiming to develop the coralbook further. This should help us refine our thinking and will be a great way to attract interns; we could publish the project description at odealab.com or have it ready should any good candidate appear.
@melisacbl https://github.com/melisacbl: by next Monday, would you be able to advance with item 2 (transform...)? I will advance with item 1. Then, we could discuss our progress here and, if necessary, we could meet on skype.
Cheers, Mauro
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/odealab/coralbook/issues/7, or mute the thread https://github.com/notifications/unsubscribe-auth/ATr-NlgM2C531gScd1frF2jENVFzAzzdks5rOxZJgaJpZM4LaRCi .
Hi @melisacbl,
Don't worry! I think two things are important:
ONE is done, so let's not waste energy now formatting. TWO is not done, the guide lives in https://github.com/ccsig/ccsig.github.io but should live in odealab/coralbook.
Let's focus on 2. Let's not change the guide, but its location. This way, all the contents of the odealab/coralbook repo will get a release version and DOI, and therefore can be downloaded as a single .zip file.
For now, take a brake. I'll experiment with a good location and I will let you know.
Cheers, Mauro
Hi @melisacbl, Note I edited the numbers because they appeared confusingly.
Hi @melisacbl, and Aaron,
I released the development version of the coralbook 0.0.0.9001 ("owner"; in development). It has a DOI with Zenodo. I learned here about Zenodo. It is similar to figshare but seems to be better integrated with github.
Now, the front page of the coralbook repo displays this pretty badge: . It is clickable and shows the latest DOI. Each release gets its own DOI.
Release notes are here.
Any thoughts let me know.
Cheers, @maurolepore
Hi @odealab and @melisacbl,
Our next step, in my opinion, should be to do two things before the end of January (after, it is likely that I will no longer be in Panama):
(A) TIDY UP WHAT WE HAVE NOW
(B) PLAN FUTURE WORK
@melisacbl: by next Monday, would you be able to advance with item 2 (transform...)? I will advance with item 1. Then, we could discuss our progress here and, if necessary, we could meet on skype.
Cheers, Mauro