|
|
| (19 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| [[PeerJ|<Back]]
| |
|
| |
|
| ==Introduction==
| |
| River Valley have a XML complaint production tracking system known as `RVMS' which means `River Valley Management System'. It can import XML coversheets and bookin a new job. It can render the coversheet. So we request XML coversheets from our clients.
| |
|
| |
| ==What is XML coversheet?==
| |
| XML coversheet means, coversheets in XML format which are accompanied with the manuscript for typesetting. Metadata is tagged using XML elements. The XML file can sometimes be a well-formed XML or a DTD/XSD driven one.
| |
|
| |
| ==Advantages of XML coversheets==
| |
| XML coversheet poses lot of advantages.
| |
| # All meta informations are tagged properly.
| |
| # This can be easily generated from the manuscript submission systems without any re-keying.
| |
| # This can be used for booking in an article in any XML complaint production tracking system.
| |
| # The tagged informations can be extracted or re-used in the further stages of production.
| |
| # Since the original data is used, typos can be avoided and eliminates the further checking.
| |
| # Using XSLT, these coversheets can be rendered.
| |
|
| |
| ===Specimen===
| |
| You may download a specimen XML coversheet from here.
| |
|
| |
| ===Elements and attributes===
| |
| ;purchase_order
| |
| Top-level element
| |
|
| |
| ;order_meta
| |
| To hold the details regarding the particular order which may include publisher's name, order_date, due_date, stage.
| |
|
| |
| ;publisher
| |
| Publisher's name. For example <code>PeerJ</code>.
| |
|
| |
| ;order_date
| |
| The date on which the purchase order is created.
| |
|
| |
| ;timestamp
| |
| The timestamp should be in the format <code>2012-12-18T12:24:12.000</code>.
| |
|
| |
| ;due_date
| |
| The date on which the proof is due back to the publisher.
| |
|
| |
| ;stage
| |
| This is to say for which milestone stage the purchase order is sent. This has two attributes namely <code>step</code> and <code>version</code>.
| |
|
| |
| ;article
| |
| Holds the metadata related to the article. The main elements are <code>journal_meta, article_meta, manuscript_meta, other_info, remarks</code>
| |
|
| |
| ;journal_meta
| |
| Contains <code>journal_id, journal_name, issn</code>
| |
|
| |
| ;journal_id
| |
| Provide the journal id here. Normally four or five letter journal code. For example, <code>SPMI</code> for <code>Superlattices and Microstructures</code>.
| |
|
| |
| ;journal_name
| |
| Provide full name of the journal.
| |
|
| |
| ;issn
| |
| This has an attribute <code>type</code> with values <code>epub</code> and <code>ppub</code>. <code>epub</code> is for online issn and <code>ppub</code> is for print issn.
| |
|
| |
| ;article_meta
| |
|
| |
|
| |
|
| |
|
| |
| <!--
| |
| ===Structure===
| |
| * XML declaration on the top.
| |
| <geshi lang="xml">
| |
| <?xml version="1.0" encoding="utf-8" ?>
| |
| </geshi>
| |
| * Top-level element
| |
| <geshi lang="xml">
| |
| <purchase_order>
| |
| </geshi>
| |
| * It holds mainly the following elements
| |
| -->
| |