Meeting Authorization

Meeting Information

This authorizes the annual meeting: .
The meeting will be held on 03/02/2021 at Online-Remote. :

Admin Advisor: Loren J. Giesler (lgiesler1@unl.edu)

Additional Info

NCERA-137 Meeting (virtual). <br /> March 2, 2021 - Starting 9:00 am central.<br /> <br /> There are three action items to prepare for the 2021 meeting. <br /> <br /> 1. Research presentations: We will offer an opportunity for those interested to present research results (10-15 min) (postdocs and graduate students are encouraged). Please follow link to submit author, title and brief abstract https://purdue.ca1.qualtrics.com/jfe/form/SV_enimM7wwr7PxeQt , no later than Feb 20, 2020 to be part of the program.<br /> <br /> 2. State updates: we are asking that you send 1 slide (Due Feb 20, 2021) to me dtelenko@purdue.edu and fill-out the state report on a google form (thanks to Alyssa Koehler for developing this new tool) https://forms.gle/paEHBnqDEnKNHj9V8. Your 2020 Annual Report will be due March 15, 2021. I have attached both a template and the most recent impact statement, which was created from the reports from 2014-2019. The google form can be used instead of the word document and if submitted by Feb 20 will be included in an infographic for the meeting. If you fill out the word document please send to Daren Mueller dsmuelle@iastate.edu <br /> <br /> 3. Sign-up for NCERA-137 basecamp group: All future correspondence for NCERA-137 will come from basecamp. https://3.basecamp.com/3209262/join/yhi1PJ4bL6sU, as not everyone that attends is signed up in the NIMSS system. I will try to add as many people to the list – but just in case I miss someone the link will also allow you to sign-up for the group. <br /> <br /> A final program agenda and meeting access will be sent the week of Feb 22, 2021.<br /> <br /> Reach out to Dr. Telenko with any questions. <br /> <br />
Log Out ?

Are you sure you want to log out?

Press No if you want to continue work. Press Yes to logout current user.

Report a Bug
Report a Bug

Describe your bug clearly, including the steps you used to create it.