Workshop archive and follow-up
AI4RA: The Intersection Between AI and Data
This site now serves two jobs. You can revisit the workshop as it was delivered at REACH 2026, or you can use the post-workshop guides and resources to turn the material into a practical pilot at your own institution.
Start with the path that matches what you need today, then cross over when you are ready.
Funded by National Science Foundation grant #2427549
Choose Your Path
Use the home page as a doorway to either the delivered workshop or the follow-through work.
Revisit the modules, slides, presenters, and interactive materials
Use this path if you want to replay the workshop itself, review the module sequence, reopen the slide decks, or revisit the companion materials as attendees experienced them.
- Open the three workshop modules and facilitator guides.
- Revisit presenter bios, session framing, and workshop resources.
- Re-enable the interactive activities when you want to replay live elements.
Use role-based guides, pilot ideas, and resource maps to move into practice
Use this path if you want help deciding what to try next at your institution, how to start small, or which tools make sense for research administration, software and data teams, leadership, or mixed groups.
- Follow role-based paths for research administration, data teams, leadership, and mixed groups.
- Use the pilot ideas and 30-day roadmap to scope realistic next steps.
- Find the right AI4RA resource faster instead of scanning the whole stack.
Post-workshop support
If you are here to act on the workshop, start with the path that fits your role.
Start with one workflow people already do by hand
Pilots land best when they focus on one document-heavy or review-heavy task such as sponsor notices, subawards, or compliance checks.
Use the tools as prototypes for governed local workflows
Data Crawler Carl, the UDM, and the lakehouse materials are a better starting point than a blank-slate AI build.
Sponsor a small pilot with explicit guardrails
The strongest leadership move is not a broad mandate. It is naming one owner, one source of truth, and one decision rule for success.
Use the workshop as a shared language across roles
Cross-functional teams can replay the modules together, then pick a single 30-day pilot that combines domain expertise, data, and governance.
After you choose support
The fastest way to lose momentum is to treat every workshop idea as one project.
Pick one workflow, one source of truth, one owner, and one evaluation rule. Then decide whether to automate, augment, or leave it alone.
Gemini API Key
Some workshop activities use Google's Gemini AI. Scan the QR code or enter your key below and it will be passed automatically to interactive pages.
Don't have a key? Get one free
- Visit Google AI Studio and sign in with your Google account.
- Click Create API Key and select a Google Cloud project (or let it create one).
- Copy the generated key and paste it into the input field above.
How is my key kept secure?
- Tab-scoped storage. Your key is held in sessionStorage, which is scoped to this browser tab. It is automatically cleared when you close the tab and is never written to disk or shared across tabs.
- Static site. This page is served as a static file from GitHub Pages. There is no server that stores or has access to your key.
- HTTPS in transit. API calls to Google use HTTPS (TLS), so your key and prompts are encrypted between your browser and Google's servers.
- URL stripped. If the key is passed via
?key=, it is read once and immediately removed from the address bar so it does not appear in browser history or bookmarks. - Your key, your account. Each participant uses their own free-tier Gemini key. No shared credentials are stored anywhere.
Note: As with any client-side application, your key is visible in browser developer tools while the page is open. For a workshop setting with free-tier educational keys this is acceptable. Do not use a key attached to a paid production project.
Facilitators: Pre-fill by sharing a link with ?key=YOUR_KEY appended.