How it works
Curvenote Reader layers a connected reading experience onto the structured content you already maintain. It does this without moving your content or changing your publishing workflows.
From JATS XML to connected reading¶
Curvenote Reader translates your structured JATS XML into Curvenote’s internal content format. From there, each article can be rendered as either of two open, web-native formats that power the reading experience:
Open Exchange Architecture (OXA)
MyST JSON
These formats are what make citations, references, figures, and metadata interactive at the point of reading.
Your content stays where it lives¶
Curvenote Reader connects to your content where it already is — there is no required migration. Content can live in:
Amazon Web Services (AWS)
Microsoft Azure
Google Cloud
Versions¶
Reader supports multiple versions of an article. As new versions are published they are ingested and kept available alongside earlier ones, so readers can move between them. Versions can also be removed when needed.
Discovery¶
Content is indexed so readers can search across a Reader site by title, author, or DOI. See Managing a Reader site for more on search and site configuration.
- DOI
- Digital Object Identifier
- JATS
- Journal Article Tag Suite
- JSON
- JavaScript Object Notation
- MyST
- Markedly Structured Text
- XML
- Extensible Markup Language