Skip to content
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.

Sign up for GitHub

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

Jump to bottom

OHBM 2020 submission - consent and author information #310

Closed
adswa opened this issue Dec 12, 2019 · 45 comments
Closed

OHBM 2020 submission - consent and author information #310

adswa opened this issue Dec 12, 2019 · 45 comments

Comments

@adswa
Copy link
Contributor

adswa commented Dec 12, 2019 •
edited
Loading

@loj @aqw @marisaheckner @lisanmo @lilikapa @yarikoptic @kyleam @jbpoline @bpoldrack @effigies @LisaWiersch96 @NevenaK @nhjjreuter @pvavra @TobiasKadelka @heytitle @mih

Dear wonderful handbook contributors!

I will submit a poster abstract about the handbook for the OHBM 2020 in Montreal. I would like all of you to be co-authors. A draft on an abstract is here, and the submission deadline is December 19th.

If you consent to being a co-author I would like you to do the following:

  • Please add your name, affiliation, and - if you have one - ORCID ID to the .zenodo.json file.
  • Please give the draft a read and let me know if there is something you disagree with. If you want to suggest changes, please do it in "suggest mode".
  • Please add your name and affiliation to the draft of the abstract.

Please note: If I don't get a response, I can't add you as a co-author!

Thanks for being a part of this! :)
@p16i
Copy link
Contributor

p16i commented Dec 12, 2019

Hi,

My contribution is rather small, fixing a typo in README. For me, it doesn't seem to be sufficient for being a co-author.

@adswa
Copy link
Contributor Author

adswa commented Dec 12, 2019

Hey @heytitle, its of course completely up to you whether you want to become a co-author. Please do know that I'd gladly have you as a co-author, and that I think your contribution is completely sufficient - in my opinion, it is engaging in the first place (regardless how much) that makes all the difference and enables such open projects. If the amount of contribution is the only aspect that makes you hesitant, be assured that I don't feel that it is not enough.

@effigies
Copy link
Contributor

Thanks for the offer! The abstract looks good; made some small suggestions.

For the Zenodo, would you prefer a PR or just a JSON snippet here that you can add in one big commit?

If PR, should we be creators, or do you want to add a contributors section? (See fMRIPrep's .zenodo.json for an example where creators and contributors are distinguished.)

@adswa
Copy link
Contributor Author

adswa commented Dec 12, 2019

Thanks for your suggestions, thanks for your json snippet (what a cool thing to have readily available!), and thanks for the hint about the creators/contributors difference! :)

  • Re suggestions: Will work them in
  • Re Zenodo: I'll add your snippet, no need for PR
  • Re structure: Prior to the upcoming release I'll restructure to distinguish creators and contributors

See you in Montreal, hopefully!

@adswa adswa mentioned this issue Dec 12, 2019
Closed
6 tasks
@pvavra
Copy link

pvavra commented Dec 12, 2019

Also thanks for the offer! Made some small comments around wording.

got inspired by @effigies and made my own json snippet.

@effigies
Copy link
Contributor

It's spreading...

@p16i
Copy link
Contributor

p16i commented Dec 12, 2019

I've made some comments on the draft, and thanks again for the offer.

This is my json snippet.

@jbpoline
Copy link
Contributor

jbpoline commented Dec 12, 2019 via email

@PeerHerholz
Copy link

I'm part of the club now as well: here's mine. Thx to the trendsetter @effigies.

@adswa
Copy link
Contributor Author

adswa commented Dec 16, 2019

ping @kyleam @lisanmo @LisaWiersch96 @NevenaK

@lisanmo
Copy link
Contributor

lisanmo commented Dec 16, 2019

Thank you for including all of us! Here's my json snippet:
https://github.com/lisanmo/meta/blob/master/zenodo.json

@adswa
Copy link
Contributor Author

adswa commented Dec 16, 2019

Thx! The link leads into nowhere, but I found it ;-)

@lisanmo
Copy link
Contributor

lisanmo commented Dec 16, 2019

Sorry for that!

@adswa
Copy link
Contributor Author

adswa commented Dec 17, 2019 •
edited
Loading

handbook_abstract_submission.pdf

Hey everyone, I have completed the abstract submission. Here's the PDF summary and all of you should get notified via email.
Fingers crossed!

@mih
Copy link
Collaborator

mih commented Dec 17, 2019

Awesome! Thx much for putting this together and making it huge!

@p16i
Copy link
Contributor

p16i commented Dec 17, 2019

@adswa thanks!

Is it still possible to make a small change?
My first name and surname are in the opposite order. It should be Pat... Chor...

@effigies
Copy link
Contributor

It has Stanford located in Stanford, NH. Should probably be Stanford, CA.

@adswa
Copy link
Contributor Author

adswa commented Dec 17, 2019

Oh, good find. I blame you, though, I found you in the system and used the existing entry ;-)

@adswa
Copy link
Contributor Author

adswa commented Dec 17, 2019

@heytitle sincerest apologies! I will try to adjust that later!

@mih
Copy link
Collaborator

mih commented Dec 17, 2019

If you edit it once more, there are a bunch of (five) redundant, but different affiliations for the FZJ.

@effigies
Copy link
Contributor

Oh, good find. I blame you, though, I found you in the system and used the existing entry ;-)

I think when I registered it asked for my address, and then later asked for my affiliation. Not sure if I screwed something up or it's picking and choosing from different tables.

@marisaheckner
Copy link
Contributor

marisaheckner commented Dec 17, 2019 via email

@nhjjr
Copy link

nhjjr commented Dec 17, 2019 via email

@yarikoptic
Copy link
Contributor

Just to be sure, since I do not see it mentioned, ideally (but not mandatory) every co-author should be registered within OHBM submission system: https://ww4.aievolution.com/hbm2001/ and that is where you, while registering, would enter affiliations AFAIK, so they would get populated whenever Adina finds/selects you in the system while submitting. It is possible to add co-authors while manually entering details, but IMHO it is inferior process, and you might end up with multiple you in the system. So if you didn't add yourself in the system, I would advise to do so.

@adswa
Copy link
Contributor Author

adswa commented Dec 17, 2019

Now I'm properly back at my computer (vacation today due to wedding) -- @nhjjreuter @marisaheckner et al: Yes I know about the two affiliations, however, the submission portal has a character limit and does not allow inputting several affiliations. If you want to have both, try it by setting up an account for yourself (not sure whether there is more space, but during abstract submission there definitely isn't) and let me know so that I can adjust to that one :)

Re differences in INM-7 names also stem from pre-existing accounts (where I don't have any means to change them), but I've tried to adjust them just now.

Re @heytitle: sorry again for confusion last and first name. I feel horribly culturally insensitive. I believe you created an account in the system, and I was able to update your authorship with the existing one, so it should be correct now.

Overall, I'd second @yarikoptic strongly :) And I would assume that noone will bat an eye about aaccuracy of author affiliations in the review process. I promise to make sure that everything is correct on the poster, should the abstract be accepted :)

@adswa
Copy link
Contributor Author

adswa commented Jan 15, 2020

FYI: https://zenodo.org/record/3608612#.Xh7UnKYo8UF

@adswa
Copy link
Contributor Author

adswa commented Feb 20, 2020

Dear Adina Wagner:

1933 - The DataLad Handbook: A user-focused and workflow-based addition to standard software documentation

Congratulations! The OHBM Program Committee has completed their review of all submitted abstracts, and we are pleased to inform you that your abstract has been accepted for a poster presentation during the 2020 OHBM Annual Meeting in Montreal, Canada. For 2020, posters will be displayed for two days each, over a four day period, Saturday, June 27 - Tuesday, June 30. There will be a poster reception for each two day period, before your poster comes down. You will receive a separate email in April with your poster number, poster session stand-by time, poster guidelines, and instructions for uploading an E-poster (an electronic version of the poster as a pdf).

As a poster presenter, you must register for the meeting and make your own travel and hotel arrangements. Having an accepted poster is not equivalent to a conference registration. Please visit the OHBM conference website: www.humanbrainmapping.org/2020registration for more information on how to register. The Early Registration deadline for the meeting is April 1, 2020. Register now and save on registration fees!

Any author on the abstract is eligible to present at the meeting. If another author will be presenting at the meeting, please forward this email to them. If your poster cannot be presented at the conference, please notify the OHBM Executive Office as soon as possible at info@humanbrainmapping.org.

To increase the visibility of accepted abstracts, we invite all authors to supplement their presentations with 2-minute videos to be hosted on the OHBM YouTube channel. As this is a new format, we encourage everybody to get creative and to experiment with slides, animations and cameras. The only requirement is to stay under 2 minutes. The videos will be embargoed until the annual meeting, and can then be shared on social media. If you are interested in trying out this new format, please e-mail us at ohbm.blogteam@gmail.com so we can send you the submission guidelines.

Congratulations again on your poster acceptance. See you in Montreal!

Sincerely,

OHBM Program Committee

@adswa
Copy link
Contributor Author

adswa commented Apr 16, 2020

For the record:

Dear Adina:

Congratulations again on being selected as a poster presenter for OHBM 2020!

As you probably are aware by now, OHBM 2020 will NOT be taking place in Montreal this year, but WILL go on as planned via an innovative and interactive virtual experience, utilizing the already accepted submissions. We will still be featuring all accepted posters over a two week time span, beginning June 23. In addition, we will be scheduling standby times to provide the opportunity to chat with authors about your poster. With that said, please make sure your poster is in PDF format - more specific instructions will be sent out soon.

Note: an updated registration link (with reduced registration fees) will be sent out shortly - kindly disregard original deadlines. If you have already registered several options will be made available, please wait for further communication.

If you have any questions, please contact the OHBM Executive Office at info@humanbrainmapping.org. We look forward to seeing you online!

Sincerely,

OHBM Program Committee

@bpoldrack
Copy link
Contributor

bpoldrack commented Apr 17, 2020 •
edited
Loading

Dito.

Using this to note my number:
2280 - A model implementation of a scalable data storage for scientific computing with DataLad

@adswa
Copy link
Contributor Author

adswa commented May 29, 2020

Hey everyone, in preparation of the OHBM I drafted the poster. Please review and tell me if there is stuff that you disagree with or would like to see improved. Please check whether I have included you in the author list and spelled your name correctly. If you have a double affiliation (all of the Juelich PhD's) I've used only one affiliation on the poster. Its busy enough on there, and all your affiliations were correctly inputted into the system, so please don't mind this unless you know of any reason I may have missed why these affiliations may be important.

I pushed the svg sources of the poster in #504, please feel free to contribute, or leave comments here or in the PR. If you're fine, I'd appreciate a thumbs-up (but honestly, unless you voice criticism here, I'll take a non-response as approval ;-) )

The only criticism I won't take is if it is in the lines of "This does not comply to the research centre's poster templates" ;-) If this becomes a problem with any FZJ person or Simon, I'll discuss and defend this personally with the german bureaucracy. In my honest opinion, the FZJ template does not add anything to a poster apart from making it look more generic. There is a clearly visible Juelich Logo which should suffice as an affiliation indication, and after all, this is a not-only-FZJ-collaboration.

Thanks in advance!
OHBM_2020

@yarikoptic
Copy link
Contributor

In tech infrastructure:

typo readthedocsrg

Remove trailing period in 3rd item for consistency

You could mention Princeton handbook being based on your setup in/after the first item.

"Simple audience tailoring" - does it mean that outsiders (like me or not) could submit their own branches to official handbook?

@adswa
Copy link
Contributor Author

adswa commented May 29, 2020

"Simple audience tailoring" - does it mean that outsiders (like me or not) could submit their own branches to official handbook?

If you can make a case as for why you'd need one, and if I don't need to be the one managing it, I don't see a reason why not ;-) In theory, I just need to switch on readthedocs for the new branch and we're done. We'll do one handbook version with EBRAINS Logos everywhere (#486) for example. Do you have a usecase?

@loj
Copy link
Contributor

loj commented May 29, 2020

Looks great! Just a few things I noted...

In Background:

  • Missing a close parenthesis

DataLad (Halchenko, Hanke et al. is a comprehensive...

In Book layout: Basics:

  • typo: save-space -> safe-space

Trial and error: Common errors are explicitly demonstrated in the save-space of a tutorial

In Book layout: Usecases:

  • typo: descriped -> described

Explanations and instructions towards the descriped real-world application.

@NevenaK
Copy link
Contributor

NevenaK commented May 29, 2020

I completely agree with Laura:
"Looks great! Just a few things I noted...", adding to that:

In Background:

  • is there a "to" too much?

"and can help to solve to various data..."

  • is there a comma missing?

"such as file size [comma] independent version control..."

In "Technical Infrastructure"

  • is it extendable, rather than extentable?

and I love the design of the poster! 🤗

@adswa
Copy link
Contributor Author

adswa commented May 29, 2020

Awesome, thanks much all for finding that many typos already! 🤗

@yarikoptic yarikoptic mentioned this issue May 29, 2020
Open
@yarikoptic
Copy link
Contributor

Do you have a usecase?

Sure I do, I don't have probably enough time ATM to push it forward by myself, but I will keep it in mind now as an opportunity! I have asked because this little "feature" could be of great advantage and utility, so I think it should be promoted/streamlined a bit more: #506

@effigies
Copy link
Contributor

Hi @adswa, this looks great! I have some comments at varying levels of nit-pickery. Modulo the typos, most of these are aesthetic, so feel free to disagree with and ignore them.

  1. Subtitle: "A[n] [...] infrastructure for ...."

    • Infrastructure is an aggregate noun, so "an infrastructure" reads oddly. You could replace infrastructure with "framework" if you're focusing on the tooling, or "model" or "template" if you're focusing on the process.

  2. Background

    • The first two columns aren't really a list, so the bullet points are out of place. I think these sections would stand well as paragraphs.
    • s/fulfils/fulfills/
    • Extra colon: "different software user types**:** independent of background:"
    • Colon after background feels a little odd at the bottom of a column. One option could be to replace it with a visual element that points to the list (schematized below):
                                                  /-> Trainees
                                              |
ndbook is a comprehensive documentational     |-> Planners
fulfills the needs of different user types    |
 background ----------------------------------+-> Teachers

  3. Book layout

    • With the bold slugs (the bold bit... I don't have a better word), I think you can drop the bullets from all of these, as well.
    • These descriptive sections are heterogeneous. Some are phrases expanding on the slug, some are statements. Sometimes this can't be helped, but I would consider the flow, at least within a box.
    • Introduction: Newline after Guidance: would make these three sections look more uniform.
    • Basics: "allows to explore" -> "allows for exploration of"
    • Usecases: Two words? You seem to use the one- and two-word forms interchangeably from a quick scan of https://handbook.datalad.org/en/latest/usecases/intro.html. Unless datalad has a specific meaning for the one-word form, I would go with two.

  4. Technical infrastructure

    • First line: infratructure (missing s)
    • Second line: reStructuredText is abbreviated "rst". Wikipedia lists abbrevations as "RST, ReST, or reST".
    • Formats: I think EPUB is generally capitalized

  5. Caveats

    • I would drop the "yet" in "yet unreleased functionality".

  6. Contributing

    • This doesn't feel like a single list. Some seem like examples of the "contribution types" mentioned in point 1, others are independent points. I can try to think about a higher-level structure, but it might be as easy as relegating some points to a sub-list.
    • High and low barriers: A full sentence followed by a sentence missing a period feels odd.
    • Review: This one in particular feels out of place with the rest. I think it's good to mention, though. Maybe an un-bulleted statement like "All contributions are reviewed by the DataLad core developer team"

Thanks for all the work on this (and the Handbook)!

@adswa
Copy link
Contributor Author

adswa commented May 30, 2020

Thanks a lot @effigies, much appreciated! I applied all of your suggestions, and thanks for catching all of the typos. :)

For everyone joining in to the typo-hunt later, here's how everything looks with all suggestions so far applied:
OHBM_2020

Coincidentally, last night the OHBM also send out another poster presenter update. Here are the hours in which I will (wo)man the poster ;-) (the poster number is even (1914), so I'll be there during the first hour of each two-hour time slot)

The poster presentation schedule (day and start time) is as follows:

• Wednesday, June 24: 12.00H - New York; 17.00 - London; 24.00H - Hong Kong
• Friday, June 26: 20.00H - New York; 1.00 +1d - London; 8.00H +1d - Hong Kong
• Tuesday, June 30: 20.00H - New York; 1.00 +1d - London; 8.00H +1d - Hong Kong
• Thursday, July 2: 2.00H - New York; 7.00 - London; 11.00H - Hong Kong

I'm certain that it will be dreadfully boring so sit in front of my computer in the middle of my night (lol, two of these slots are 2AM in my time zone), so feel free to drop by and chat if you want to, everyone. :-)

@yarikoptic
Copy link
Contributor

To me all those times are wonderfull opportunities for yet another datalad drinkathon among ourselves if nobody else from audience doesn't come ;-)

@effigies
Copy link
Contributor

Small final comment: I usually include my middle initial (J) in author lists.

Otherwise, LGTM.

@jbpoline
Copy link
Contributor

jbpoline commented May 31, 2020 via email

@yarikoptic
Copy link
Contributor

Work harder JB, work harder! ;-)

@jbpoline
Copy link
Contributor

jbpoline commented May 31, 2020 via email

@adswa
Copy link
Contributor Author

adswa commented Jun 2, 2020

Small final comment: I usually include my middle initial (J) in author lists.

Done, thx!

@adswa
Copy link
Contributor Author

adswa commented Jun 24, 2020

closing this issue, the poster can be found here: https://cdn-akamai.6connex.com//645/1827//OHBM_2020_15922340091267382.pdf
Everyone's welcome to join and chat during poster presentation times.

@adswa adswa closed this as completed Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests