Skip to content

ESIIL Macrophenology Working Group

Welcome to the Macrophenology Working Group repository, part of the Environmental Data Science Innovation and Inclusion Lab (ESIIL). This repository serves as the central hub for our working group, hosting our project description, proposals, member bios, codebase, and more.

Our Project

Plant phenology — the seasonal timing of leaf-out, budding, flowering, fruiting, and leaf-off — is the most easily observable and well-documented biological response to climate change. Changes in phenology have many aspects of plants relevant to society (e.g., food security, carbon sequestration, seasonal allergies). Often we need to know where and when these seasonal changes in plants occur, which is challenging given their sensitivity to changes in climate. However, little is known about how plant phenology influences a species’ ability to persist in different locations in the face of climate change, how rare versus common species respond to climate, or how native vs. invasive plants may respond to climate change differently. We will tackle these questions by combining different types of phenological data with species distribution data, which will require access to advanced computing resources. We will use a co-production framework with Indigenous scholars to develop a research approach and products that are needed and of value to their communities.

Project Proposal

Here is our project proposal

Group Members

  • Sydne Record (PI): University of Maine, Orono, ME
  • Linda Black Elk (Co-PI): North American Traditional Indigenous Food Systems (NATIFS), Minneapolis, MN
  • Kai Zhu (Co-PI): University of Michigan, Ann Arbor, MI
  • Eric Sokol (Tech Lead): National Ecological Observatory Network (NEON), Battelle, Boulder, CO

Code Repository

This section of the repository will include all the code developed for the project. You can structure it as follows:

  • Analysis Code: Scripts for data analysis, statistical modeling, etc.
  • Data Processing: Scripts for cleaning, merging, and managing datasets.
  • Visualization: Code for creating figures, charts, and interactive visualizations.

Meeting Notes and Agendas

Meeting notes and agendas will be regularly updated here to keep all group members informed and engaged with the progress and direction of the project.

Contributing to This Repository

We welcome contributions from all group members. To maintain the quality and integrity of the repository, please adhere to the following guidelines:

  • Make sure all commits have a clear and concise message.
  • Document any major changes or decisions in the meeting notes.
  • Review and merge changes through pull requests to ensure oversight.

Getting Help

If you encounter any issues or have questions about how to contribute, please refer to the ESIIL Support Page or contact the repository maintainers directly.

Customize Your Repository

As a new working group, you'll want to make this repository your own. Here's how to get started:

  1. Edit This Readme: Replace the placeholder content with information about your specific project. Ensure that the introduction, project overview, and objectives clearly reflect your group's research focus.

  2. Update Group Member Bios: Add details about each group member's expertise, role in the project, and professional background. Include links to personal or professional web pages to foster community engagement and collaboration.

  3. Organize Your Code: Structure your codebase in a way that is logical and accessible. Use directories and clear naming conventions to make it easy for all members to find and contribute to different parts of the project.

  4. Document Your Data: Include a data directory with README files explaining the datasets, sources, and any preprocessing steps. This will help new members understand and work with the project's data effectively.

  5. Outline Your Methods: Create a detailed METHODS.md file where you describe the methodologies, software, and tools you will be using in your research. This transparency will support reproducibility and collaborative development.

  6. Set Up Project Management: Utilize the 'Issues' and 'Projects' features on GitHub to track tasks, discuss ideas, and manage your workflow. This can help in maintaining a clear view of progress and priorities.

  7. Add a License: Choose and include an appropriate open-source license for your project, ensuring that the broader community understands how they can use and contribute to your work.

  8. Create Contribution Guidelines: Establish a CONTRIBUTING.md file with instructions for members on how to propose changes, submit issues, and contribute code.

  9. Review and Merge Workflow: Decide on a workflow for reviewing and merging changes. Will you use branch protection? Who will have merge privileges? Document this process to avoid confusion.

  10. Establish Communication Channels: Beyond GitHub, set up additional communication channels like Slack, Discord, or email lists for quick and informal discussions.

Remember, the goal is to make your repository clear, accessible, and useful for all current and future members of your working group. Happy researching!

Last update: 2024-07-19