Editing API:EPrints/Apache/CRUD (section)

===HTTP Content Negotiation===
<tt>GET</tt>/<tt>HEAD</tt> requests are processed using {{API:PodLink|file=EPrints/Plugin/Export|package_name=EPrints::Plugin::Export|section=|text=Export}}  plugins. <tt>POST</tt>/<tt>PUT</tt> requests are processed using {{API:PodLink|file=EPrints/Plugin/Import|package_name=EPrints::Plugin::Import|section=|text=Import}} plugins.

The plugin used depends on the request's <tt>Accept</tt> (<tt>GET</tt>/<tt>HEAD</tt>) or  <tt>Content-Type</tt> (<tt>POST</tt>/<tt>PUT</tt>) header and the type of object being acted on. For example, the following request:

  GET /id/eprint/23 HTTP/1.1
  Accept: application/vnd.eprints.data+xml
  
Will search for an Export plugin that accepts objects of type <tt>dataobj/eprint</tt>  and can produce output in the MIME type <tt>application/vnd.eprints.data+xml</tt>.  This will most likely be the {{API:PodLink|file=EPrints/Plugin/Export/XML|package_name=EPrints::Plugin::Export::XML|section=|text=EP3 XML}} plugin.

In addition to the general plugin negotiation behaviour some special cases are  supported to improve compatibility with Atom Pub/Web Browser clients:

<div style='background-color: #e8e8f; margin: 0.5em 0em 1em 0em; border: solid 1px #cce;  padding: 0em 1em 0em 1em; font-size: 80%; '>
<span style='display:none'>User Comments</span>
<!-- Edit below this comment -->


<!-- Pod2Wiki= -->
</div>
<!-- Pod2Wiki=item_id_eprint -->
====/id/eprint/...====

Requesting {{API:PodLink|file=EPrints/DataObj/EPrint|package_name=EPrints::DataObj::EPrint|section=|text=EPrint}} objects as text/html will result in a <tt>303 Redirect</tt> to the eprint object's abstract page or, if the eprint is  not public, its {{API:PodLink|file=EPrints/Plugin/Screen/EPrint/View|package_name=EPrints::Plugin::Screen::EPrint::View|section=|text=View}} page.

<div style='background-color: #e8e8f; margin: 0.5em 0em 1em 0em; border: solid 1px #cce;  padding: 0em 1em 0em 1em; font-size: 80%; '>
<span style='display:none'>User Comments</span>
<!-- Edit below this comment -->


<!-- Pod2Wiki= -->
</div>
<!-- Pod2Wiki=item_id_document_contents -->
====/id/document/.../contents====

Requesting the <tt>/contents</tt> of a {{API:PodLink|file=EPrints/DataObj/Document|package_name=EPrints::DataObj::Document|section=|text=Document}} object  will return the content of the document's main file.

<div style='background-color: #e8e8f; margin: 0.5em 0em 1em 0em; border: solid 1px #cce;  padding: 0em 1em 0em 1em; font-size: 80%; '>
<span style='display:none'>User Comments</span>
<!-- Edit below this comment -->


<!-- Pod2Wiki= -->
</div>
<!-- Pod2Wiki=item_id_file -->
====/id/file/...====

Requesting a {{API:PodLink|file=EPrints/DataObj/File|package_name=EPrints::DataObj::File|section=|text=File}} object with no <tt>Accept</tt> header (or  <tt>*/*</tt>) will return the file's content.

<div style='background-color: #e8e8f; margin: 0.5em 0em 1em 0em; border: solid 1px #cce;  padding: 0em 1em 0em 1em; font-size: 80%; '>
<span style='display:none'>User Comments</span>
<!-- Edit below this comment -->


<!-- Pod2Wiki= -->
</div>
<!-- Pod2Wiki=item_post_id_contents -->
====POST /id/.../contents====

When creating new records via POST, content negotiation is performed against  the Import plugins.

If no Import plugin supports the <em>Content-Type</em> header the content will be  treated as <tt>application/octet-stream</tt> and stored in a new object. The  resulting Atom entry will describe the new object (e.g. the <tt>eprint</tt> object  in which the new <tt>document</tt> and <tt>file</tt> objects were created).

Otherwise, the result will depend on the Import plugin's output. Import  plugins may produce a single object, multiple objects or an object plus  content file(s).

<div style='background-color: #e8e8f; margin: 0.5em 0em 1em 0em; border: solid 1px #cce;  padding: 0em 1em 0em 1em; font-size: 80%; '>
<span style='display:none'>User Comments</span>
<!-- Edit below this comment -->


<!-- Pod2Wiki= -->
</div>
<!-- Pod2Wiki=item_content_type_header -->
====Content-Type header====

If no <tt>Content-Type</tt> header is given the MIME type defaults to  <tt>application/octet-stream</tt> for <tt>POST</tt>s and <tt>PUT</tt>s.

<div style='background-color: #e8e8f; margin: 0.5em 0em 1em 0em; border: solid 1px #cce;  padding: 0em 1em 0em 1em; font-size: 80%; '>
<span style='display:none'>User Comments</span>
<!-- Edit below this comment -->


<!-- Pod2Wiki= -->
</div>
<!-- Pod2Wiki=item_content_disposition_header -->
====Content-Disposition header====

If the <tt>Content-Disposition</tt> header is missing or does not contain a  <tt>filename</tt> parameter the filename defaults to ''main.bin'' for <tt>POST</tt>s and  <tt>PUT</tt>s.

<div style='background-color: #e8e8f; margin: 0.5em 0em 1em 0em; border: solid 1px #cce;  padding: 0em 1em 0em 1em; font-size: 80%; '>
<span style='display:none'>User Comments</span>
<!-- Edit below this comment -->


<!-- Pod2Wiki= -->
</div>
<!-- Pod2Wiki=head_updating_complex_objects_using_put -->