16 Research Products: Manuscripts, Abstracts, Posters, Dashboards, and Briefs
Success at RIPLRT is broader than grants and papers. We define it to include student development, presentations, skills, reproducible tools, and reputation alongside traditional outputs. This chapter catalogs the products we make and how we make them well.
16.1 Our product portfolio
| Product | Primary audience | Owned by (typical) | Template |
|---|---|---|---|
| Peer-reviewed manuscript | Scientific community | Writing Lead + Analysis Lead | Manuscript Planning Sheet |
| Conference abstract | Scientific community | Project Lead / mentee | Conference Abstract Planning |
| Poster | Conference attendees | Mentee (often first product) | (see abstract sheet + assets) |
| Reproducible notebook | Internal + open science | Reproducibility / Analysis Lead | Reproducible Analysis Checklist |
| Clinician-facing dashboard | Clinicians, agencies | Visualization/Dashboard Lead | (pod charter) |
| Community risk brief | Communities, partners | Science Communication Lead | (pod charter) |
| Public-health playbook | Agencies, decision-makers | Project Lead + SciComm Lead | (pod charter) |
| Bilingual sci-comm content | General public | Science Communication Lead | (pod charter) |
Among other products not yet listed here.
16.1.1 Ownership of research products
Datasets, code, dashboards, models, and other products carry ownership and intellectual-property (IP) implications that follow the umbrella under which they were created and the resources used (Section 2.2). Get this right before a product with potential value is built.
General principles (confirm specifics before relying on them):
- Products created within Lynn University — by Lynn-employed personnel, or using Lynn resources, time, or funding — are subject to Lynn University’s IP policy, which may assign ownership or co-ownership to the University. Do not assume a Lynn-built product belongs to RIPLRT or the LLC.
- Products created under the RIPLRT Institute / LLC outside Lynn employment and resources — including tools developed by FERM Technologies** — are owned by Felix E. Rivera-Mariani, PhD, LLC subject to any sponsor terms.
- UPR or external contributions are subject to that institution’s IP policy.
- Cross-umbrella products (e.g., a Lynn student contributing to an LLC/FERM tool) require a written ownership understanding agreed in advance with all relevant institutions.
Do not label a product as LLC/FERM-owned, or pursue licensing or commercialization, until ownership is confirmed in writing against Lynn University’s IP policy and, where relevant, UPR’s. When the answer is unclear, the PI obtains written clarification — and, where warranted, institutional or legal counsel — before development proceeds. This protects the member, the Institute, and the University alike.
16.2 Manuscripts
- Start with the Manuscript Planning Sheet: target journal, key message, figures, authorship plan, and timeline — before drafting.
- One Writing Lead coordinates drafting and submission; sections are delegated to build skills (figure lead, methods lead, literature-synthesis lead).
- Every number and figure traces back to a reproducible notebook (Chapter 13).
- Aim for the IAP cadence: a steady, thematically coherent manuscript pipeline organized around our four themes — aeroallergen/fungal early-warning science; respiratory severity and care pathways; biomarker/microbiome signatures; and equity-stratified environmental risk.
16.3 Abstracts and posters
- Abstracts are often a mentee’s first scholarly product — treat them as real training, not filler.
- Maintain a shared abstract calendar of society deadlines (AAAAI, AAI, ATS, SOT, ASM, ISES, ASBMB, ABRCMS, and others).
- Posters reuse manuscript figures and the through-line narrative; keep a poster template and the group’s visual identity in the repository
assets/folder. - Confirm authorship before submission; rehearse presentations as a pod.
16.4 Dashboards and decision-support tools
Forecasting and decision tools (e.g., the RespRisk line described in the IAP) are flagship products:
- Build them reproducibly, with documented thresholds, fairness/equity checks, and clear risk tiers (e.g., green/amber/red).
- Co-develop with stakeholders; validate against real-world outcomes; report calibration, decision-curve utility, and equity-stratified performance.
- Version dashboards like code; never expose restricted data through a tool.
16.5 Community briefs and bilingual communication
These close the Community-to-Clinic-to-Cloud loop:
- Community risk briefs translate forecasts into plain-language, actionable summaries for the communities the data come from.
- Materials are bilingual (Spanish/English) so they reach the people they’re about.
- Briefs get PI review and respect privacy and partner relationships.
- Track real-world uptake (briefs issued, decisions supported, partner adoption) — impact is a product too.
16.6 Quality bar for every product
Before anything leaves the group:
- It is reproducible (or, for non-analytic products, traceable to reproducible work).
- It respects data governance, privacy, and DUAs.
- Its authorship/contributorship is documented and agreed.
- It has been reviewed (peer within the pod + PI as appropriate).
- It advances a SMART goal and the through-line — we make products on purpose, not just to be busy.
Match products to mentees’ growth. A first abstract, a first figure, a first reproducible notebook, a first first-authorship — each is both a research output and a rung on the development ladder (Chapter 8). Plan products with people’s growth in mind, not just the project’s needs.