Content ingestion
Content reaches Curvenote Reader through an automated ingestion pipeline that is set up once and then runs on its own. There are no migrations, rebuilds, or changes to your publishing workflows.
Getting set up¶
Consultation. We review your systems, content formats, and workflows together.
Sample XML. You provide a sample of the JATS XML you already have available.
Runner. From that sample we build a runner tailored to your content, validating that it translates cleanly into Curvenote’s internal format.
Automated. Once validated, ingestion runs automatically as new content is published.
Ongoing ingestion¶
After setup, the runner ingests new articles and new versions as they become available. Versions can be removed when needed. No manual steps are required to keep a Reader site current.
Many repositories and publishers are still working across PDFs, Word documents, or mixed legacy formats. We are launching a new product soon designed to help organizations structure and transform scientific content before it reaches Curvenote Reader.
- JATS
- Journal Article Tag Suite
- Portable Document Format
- XML
- Extensible Markup Language