Every funding system asks for your career in its own format, and most ask you to type it in again from scratch. This page explains why that re-typing problem exists, the standards that are supposed to solve it, and how Reservoir uses them to feed the official tools you already use, without trying to replace any of them.
Why research CV data doesn't move between systems
A researcher's record lives in many places at once: publications in Scopus and Web of Science, an ORCID profile, a FECYT CVN for Spanish calls, an NIH SciENcv biosketch for US ones, and an institutional CRIS. Each was built for its own purpose, so the same facts get re-entered again and again. The cost is not just time: re-typing introduces inconsistencies (a date here, an affiliation there) that reviewers notice and that can undermine an application.
The fix is not another form. It's keeping one structured store of your merits and treating each CV format as a projection of what's already there.
The standards that connect them: ORCID, CVN, SciENcv, CERIF
A handful of open standards already make this possible:
- ORCID, a persistent identifier and a public record of your works. It functions as the hub other systems read from.
- CVN (FECYT), Spain's normalised CV: a PDF with embedded CVN-XML, FECYT-signed, required in AEI and ISCIII funding calls. The CVA is generated from it.
- SciENcv (NIH/NSF), the US researcher-profile tool that produces the Common Form biosketch and current-and-pending support, pulling citations from ORCID or My Bibliography.
- CERIF, the European standard for research information systems, the institutional analogue of CVN/SciENcv.
The common thread is structured exchange: information that travels as fields, not as flat text.
What you can bring into Reservoir
Reservoir is the store you maintain once. You can populate it by:
- Importing publications from Scopus.
- Reading your public ORCID record.
- Bringing in an existing NIH SciENcv biosketch (XML) as structured blocks.
- Uploading documents and letting Reservoir propose structured blocks you confirm.
Every import is a proposal you confirm: Reservoir never overwrites a confirmed block, and never invents facts to fill a gap.
What you can take out
From that single store, Reservoir projects your record into the formats you need:
- A conformant CVN-XML and a CVA draft (.docx) to import into the FECYT editor.
- A biosketch draft to populate and certify in SciENcv.
- Your full career as portable JSON, useful for your own backup and a clean way to exercise your data-portability rights.
In every case Reservoir produces the content; the official editor issues the sealed, certified document. It never seals it for you.
How Reservoir fits: the feeder, not the replacement
Reservoir sits upstream. ORCID, CVN and CERIF are the rails; FECYT and SciENcv are where documents get certified; a CRIS is a downstream consumer. Reservoir is the layer the researcher actually maintains and feeds into all of them, so the same confirmed store can become a Spanish CVA, an NIH biosketch, or a JSON export, on demand.
Your data stays yours
Reservoir stores your data in the EU, limited to professional merits: no national IDs, bank details or salary. Nothing is submitted on your behalf, every draft is a proposal you confirm, and you can export or delete your data at any time.