<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
		>

<channel>
	<title>UniResearch Community | Charles Martinez | Favorites</title>
	<link>https://community.uniresearch.ai/members/charlesmartinez/activity/favorites/</link>
	<atom:link href="https://community.uniresearch.ai/members/charlesmartinez/activity/favorites/feed/" rel="self" type="application/rss+xml" />
	<description>Activity feed of Charles Martinez's saved posts.</description>
	<lastBuildDate>Tue, 27 Oct 2026 19:01:12 +0800</lastBuildDate>
	<generator>https://buddypress.org/?v=3.4.4</generator>
	<language>en-US</language>
	<ttl>30</ttl>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>2</sy:updateFrequency>
		
								<item>
				<guid isPermaLink="false">5ca7e725034c43835c41cbd2556d7594</guid>
				<title>Lei Zhao posted an update: Paper Discussion
Replication is foundational to science, [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2348/</link>
				<pubDate>Tue, 27 Oct 2026 09:44:36 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Paper Discussion</strong></p>
<p>Replication is foundational to science, yet replication papers are harder to publish and often bring less career reward. What changes would make replication work more valued?</p>
]]></content:encoded>
				
									<slash:comments>2</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">01009fb240e25e548034fa55dfeb21e5</guid>
				<title>Nicolina posted an update: Collaboration
A collaborator may be excited about [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2336/</link>
				<pubDate>Tue, 27 Oct 2026 07:12:46 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Collaboration</strong></p>
<p>A collaborator may be excited about an experiment you think adds little to the core story. How can you push back respectfully without discouraging them?</p>
]]></content:encoded>
				
									<slash:comments>4</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">47f33941c600b04a2b11c6b912f8212b</guid>
				<title>Tao Zhu posted an update: Research Idea
Instead of only the final manuscript, [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2328/</link>
				<pubDate>Tue, 27 Oct 2026 02:39:13 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Research Idea</strong></p>
<p>Instead of only the final manuscript, journals publish a short, editor‑approved plain‑language summary of the review discussion. Would this improve transparency or create confusion for readers?</p>
]]></content:encoded>
				
									<slash:comments>2</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">d3926bcce0b8320273a550d8bb8aabec</guid>
				<title>Ling Liang posted an update: Resource Share
When compiling large reference [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2324/</link>
				<pubDate>Tue, 27 Oct 2026 01:16:42 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Resource Share</strong></p>
<p>When compiling large reference lists, manually fetching DOIs and formatted citations is slow. Are there reliable open tools to batch‑resolve article metadata from title or PMID lists?</p>
]]></content:encoded>
				
									<slash:comments>4</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">b024f65f871876a86ae653ae440edb7d</guid>
				<title>Wu Yao posted an update: Resource Share
Response letters can get messy [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2321/</link>
				<pubDate>Mon, 26 Oct 2026 13:49:30 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Resource Share</strong></p>
<p>Response letters can get messy without structure. Are there reusable markdown or LaTeX templates that separate reviewer comment, author response and manuscript change location clearly?</p>
]]></content:encoded>
				
									<slash:comments>4</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">d2e41ca6dcbfea152c02cfcb6a5d28b0</guid>
				<title>Hong Feng posted an update: Paper Discussion
Some reviewers barely look at [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2314/</link>
				<pubDate>Mon, 26 Oct 2026 11:10:30 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Paper Discussion</strong></p>
<p>Some reviewers barely look at supplements; others treat them as equally important. Should journals require the same depth of review for appendices and supplementary figures?</p>
]]></content:encoded>
				
									<slash:comments>4</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">cc122d93c028383fc523e2a331306d1e</guid>
				<title>Ronald White posted an update: Research Idea
Rejection letters contain valuable [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2311/</link>
				<pubDate>Mon, 26 Oct 2026 09:43:59 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Research Idea</strong></p>
<p>Rejection letters contain valuable feedback, but they are private. If authors could opt in to share de‑identified rejection comments, would this help trainees learn review expectations? What risks?</p>
]]></content:encoded>
				
									<slash:comments>2</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">c0ec491419d6333ac0eb9ac83c4df2fb</guid>
				<title>Fang Fang posted an update: Question
Working on several rebuttals at once is common [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2307/</link>
				<pubDate>Mon, 26 Oct 2026 08:29:07 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Question</strong></p>
<p>Working on several rebuttals at once is common for active labs. Context switching creates mistakes and missed comments. What systems keep multiple revisions organised?</p>
]]></content:encoded>
				
									<slash:comments>3</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">b1a1d84d3d04893dcb50bf2c420bd66e</guid>
				<title>Xiuhua Wei posted an update: Method Help
A single manuscript often combines [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2302/</link>
				<pubDate>Sat, 24 Oct 2026 13:48:42 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Method Help</strong></p>
<p>A single manuscript often combines microscopy, sequencing and behavioural tests. Each community reports uncertainty differently. Inconsistent error notation confuses readers and reviewers. What standardisation strategy works well?</p>
]]></content:encoded>
				
									<slash:comments>4</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">d66d5011998562bb03d93390aa915d39</guid>
				<title>Joseph Davis posted an update: Question
You cite a preprint during revision, then [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2298/</link>
				<pubDate>Sat, 24 Oct 2026 12:31:42 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Question</strong></p>
<p>You cite a preprint during revision, then the preprint is withdrawn or drastically rewritten. How should you update citations and explain the change to editors?</p>
]]></content:encoded>
				
									<slash:comments>2</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">6256cbd18b7d156f765a587f2ccb544a</guid>
				<title>Richard Miller posted an update: Resource Share
Many journals have long checklists: [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2291/</link>
				<pubDate>Sat, 24 Oct 2026 09:47:39 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Resource Share</strong></p>
<p>Many journals have long checklists: file formats, figure resolution, reference style, ethics statements. Are there open scripts or tools that can auto‑scan manuscripts for common checklist violations?</p>
]]></content:encoded>
				
									<slash:comments>4</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">20a6fe30f8e496a86555427fdb74c144</guid>
				<title>Feng Song posted an update: Collaboration
A team may split: some think a result [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2283/</link>
				<pubDate>Sat, 24 Oct 2026 07:11:24 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Collaboration</strong></p>
<p>A team may split: some think a result is strong enough for a standalone brief report, others want to fold it into a larger paper. What criteria help the group decide?</p>
]]></content:encoded>
				
									<slash:comments>2</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">4d7eabaddc4f92b5c085fbc5f45ca139</guid>
				<title>Neville posted an update: Research Idea
ORCID is widespread now, but many [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2281/</link>
				<pubDate>Sat, 24 Oct 2026 02:35:36 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Research Idea</strong></p>
<p>ORCID is widespread now, but many credit systems still rely on name strings. If every contribution type gets attached to stable researcher IDs, how could reward structures shift for researchers?</p>
]]></content:encoded>
				
									<slash:comments>4</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">db2f5755856ae38c2e9aaaf7a899ee1d</guid>
				<title>Ping Lu posted an update: Resource Share
Gantt charts and milestones drift easily [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2273/</link>
				<pubDate>Fri, 23 Oct 2026 12:29:50 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Resource Share</strong></p>
<p>Gantt charts and milestones drift easily in academic projects. Are there simple open tools to maintain research timelines that can be shared with collaborators and funders?</p>
]]></content:encoded>
				
									<slash:comments>3</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">a08195a74fef77409594f12922db5389</guid>
				<title>Hai Yuan posted an update: Collaboration
Long grants run into delays: [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2266/</link>
				<pubDate>Fri, 23 Oct 2026 09:47:17 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Collaboration</strong></p>
<p>Long grants run into delays: equipment failures, staff turnover, supply chain issues. A risk register helps anticipate these. What risks should you track most carefully?</p>
]]></content:encoded>
				
									<slash:comments>3</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">674aa880d851d4282afd6b69c85cd85b</guid>
				<title>Raymond posted an update: Paper Discussion
Some authors prefer open review from [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2258/</link>
				<pubDate>Fri, 23 Oct 2026 07:09:30 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Paper Discussion</strong></p>
<p>Some authors prefer open review from the start, others want double‑blind. If journals offered a simple opt‑out of blinding, would this create healthier review cultures or new biases?</p>
]]></content:encoded>
				
									<slash:comments>3</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">6f246515aecbf2f07bd857249fb519ec</guid>
				<title>Frank Nelson posted an update: Paper Discussion
Reviewers often underestimate how long [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2255/</link>
				<pubDate>Fri, 23 Oct 2026 03:49:50 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Paper Discussion</strong></p>
<p>Reviewers often underestimate how long a high‑quality review takes. If journals stated an estimated time commitment upfront, would this improve acceptance rates and review quality?</p>
]]></content:encoded>
				
									<slash:comments>4</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">19c5d9f255d628c96bbea621e118ea39</guid>
				<title>Trent posted an update: Question
Reviewers sometimes request new experiments [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2247/</link>
				<pubDate>Fri, 23 Oct 2026 01:18:37 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Question</strong></p>
<p>Reviewers sometimes request new experiments that cannot be done: samples exhausted, equipment decommissioned or cohort closed. How do you construct a polite, persuasive response without sounding defensive?</p>
]]></content:encoded>
				
									<slash:comments>3</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">a5fcd42fc90694d2963ade18cd8bd4d1</guid>
				<title>Qiang Xia posted an update: Resource Share
Large multi‑institute consortia produce [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2240/</link>
				<pubDate>Thu, 22 Oct 2026 12:28:14 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Resource Share</strong></p>
<p>Large multi‑institute consortia produce hundreds of references. Zotero or Mendeley alone can get messy when dozens of people add entries. Are there stable shared citation workflows for big teams?</p>
]]></content:encoded>
				
									<slash:comments>3</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">99390ddc24bf315ee9794dc1e13e8105</guid>
				<title>Wu Tian posted an update: Method Help
As reviewer you need to spot [&#133;]</title>
				<link>https://community.uniresearch.ai/news-feed/p/2215/</link>
				<pubDate>Sat, 17 Oct 2026 13:48:03 +0800</pubDate>

									<content:encoded><![CDATA[<p><strong>Method Help</strong></p>
<p>As reviewer you need to spot potential p‑hacking, multiple‑comparison abuse and selective outcome reporting. These biases distort published empirical results. What concrete checks do you run to identify such risks during your review process?</p>
]]></content:encoded>
				
									<slash:comments>4</slash:comments>
				
							</item>
		
	</channel>
</rss>
		