[LTER-im-rep] information and poll regarding 2020 meeting of the IMC

[Stevan Earl]

Dear LTER Information Manager,

We are extremely fortunate to once again have funding that will enable us
to host a meeting of the IMC in 2020. As in recent years, we will host a
one-day meeting of the IMC in conjunction with a larger meeting. Typically,
we have hosted our meetings in association with ESIP
<https://www.esipfed.org/meetings/upcoming-meetings> (ESIP 2020:
Burlington, VT, July 7-10 with an IMC meeting on Monday, July 6th), which
is being considered as an option for 2020 as well. The ESIP Summer Meeting
provides ample opportunity for us to lead sessions and interact with data
professionals external to the LTER Network (e.g., NASA, NOAA, and the USGS
among others).

There are a confluence of circumstances surrounding the 2020 meeting of the
Ecological Society of America (ESA <https://www.esa.org/saltlake/>; Salt
Lake City, UT, August 2-7 with an IMC meeting on Sunday, August 1st) that
present it as a promising alternative venue. Foremost, the theme of ESA
2020 is harnessing the ecological data revolution (see meeting website for
more details). While ESA is always relevant to the IMC, the sessions,
workshops, and activities this year are likely to be particularly relevant
given the theme. The deadline to submit workshop proposals is approaching
rapidly (November 21) and these will be reviewed more critically than ESIP.
However, the deadline to submit talks and posters will be later (typically
late February) and there will be an open science track (among others) that
would be relevant for abstracts that IMs may want to submit. Additionally,
ESA 2020 will again host a data help desk (DHD). The DHD is a collaborative
effort among representatives from EDI, ESIP, GBIF, iDigBio, DataONE, and
NEON to answer questions, host workshops, and make presentations designed
to assist the ecological community with publishing data. There may be
opportunities for LTER IMs to be involved with the DHD, and, at the very
least, is emblematic of the ESA community's embrace of the importance of
sharing ecological data. Finally, ESA 2020 coincides with the LTER decadal
review. Though details are not yet available, activities and events focused
on this critical assessment of the LTER program are being planned, some of
which are sure to focus on LTER data and the management of those data.

Attending either of these meetings will be expensive, though costs are
likely to be similar between the two. The registration fee for ESA is
higher than ESIP but airfare to Burlington (ESIP) is likely more expensive
than for Salt Lake City (ESA). Housing costs are not yet known but GSA Per
Diem Rates for Burlington are $142/day, and $127/day for Salt Lake City.
The full ESA meeting is longer by one day, which would factor into housing
costs if participants attend the entire meeting that includes a half-day of
workshops and field trips on the final day of the meeting. Unlike ESIP, ESA
would charge the IMC for meeting logistics (i.e., meeting rooms, projector,
staff time) but these costs are manageable (~$600). Please note that
participants will not be reimbursed for lodging expenses by the LNO or EDI
regardless of the meeting venue, so be in contact with your site leadership
to arrange for your lodging needs.

The IM Exec asks that you please vote for your preference between the two
options for the 2020 meeting of the IMC by completing a brief poll (link
below). IM Exec would also appreciate knowing if you are planning to attend
one or both of these meetings regardless of the IMC venue. Comments are
very welcome as well (but not required). Please address the poll, which
should require no more than two minutes of your time, by Wednesday, October
23rd. Note that the poll will log the email address of the submitter.

link to poll: https://forms.gle/HBRdmSf3qSWavStx8


Thanks in advance for your consideration,

IM Exec
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lternet.edu/pipermail/im-rep/attachments/20191019/b7528a8f/attachment.html>