API:bin/export
EPrints 3 Reference: Directory Structure - Metadata Fields - Repository Configuration - XML Config Files - XML Export Format - EPrints data structure - Core API - Data Objects
Latest Source Code (3.4, 3.3) | Revision Log | Before editing this page please read Pod2Wiki
Contents
NAME
export - export some or all items in a dataset using an output plugin.
SYNOPSIS
export repository_id [options] dataset
export repository_id [options] dataset plugin [objectid] [objectid...]
DESCRIPTION
This command outputs a dataset in the selected format. The formats available depend on what Export plugins have been installed.
Some plugins only operate on lists (e.g. RSS), others only operate on single objects only. Some plugins act slightly differently in single-item only mode. For example, outputing a list of eprints as XML gives a number of <eprint> elements in an outer <eprints> element.
To get the plugin to export a single item use --single. This may not always return a complete file. For example it may be missing the <?xml header, depending on the plugin.
ARGUMENTS
The ID of the EPrint repository to use.
==
The name of the dataset to export, such as "archive", "subject" or "user".
==
The id of the output plugin to use. This should not include the leading "Export::". Examples: BibTeX, XML.
If this is ommited or an invalid plugin is requested, then 'export' will list all plugins compatible with the dataset and exit.
==
If this is set then just output the single, specified item or items.
OPTIONS
==
Add an argument to the export plugin. May be repeated. Effects depend on te export plugin.
==
Print a brief help message and exit.
==
Print the full manual page and then exit.
==
Be vewwy vewwy quiet. This option will supress all output unless an error occurs.
==
Explain in detail what is going on. May be repeated for greater effect.
Shows why a plugin is disabled.
==
Output version information and exit.