Define mime type in API call?

We have an automated process using the API that creates a folder structure and uploads PDFs to Content Server. Unfortunately, this proicess does not define the mime type so it's set as "application/octet-stream", which means that these documents are excluded from renditioning, since our rendition rule is set for PDFs and Content Server looks at the mime type to determine file type. Is there a way to define the mime type of a file while uploading using the API?

Find more posts tagged with

Comments

Wallace Ho

Hi Tim,

Which API is being leveraged (REST, CWS, etc)? What version of Content Server is deployed?

Regards,

Wallace

Quoted Tim Saunders on 03/02/2018 09:10 AM:

appuGmail

Node. has VersionInfo()

VersionInfo() has GetMimeType() anad a SetMimeType() sound s very promising

Only thing I would say is basically when you get a Node make sure it is a versionable like a 144

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Fri, Mar 2, 2018 at 7:47 AM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

Define mime type in API call? Posted bytim.saunders@guggenheimpartners.com (Saunders, Tim)On 03/02/2018 08:43 AM

We have an automated process using the API that creates a folder structure and uploads PDFs to Content Server. Unfortunately, this proicess does not define the mime type so it's set as "application/octet-stream", which means that these documents are excluded from renditioning, since our rendition rule is set for PDFs and Content Server looks at the mime type to determine file type. Is there a way to define the mime type of a file while uploading using the API?
[To post a comment, use the normal reply function]
Forum: Content Server Development Forum
Content Server: My Support

Ferdinand Prantl

Yes, both SOAP (CWS) and REST APIs allow specifying the MIME type of the uploaded document content. Either your automated tool has to set it correctly by instecting the file name and/or the file content, or it has to allow you to specify it by some configuration.

Tim S

REST API, currently 10.5 with a move to 16.2x pending

Ferdinand Prantl

Most probably you use POST api/v1/nodes to create a new document with content. You need to make the tool send the right content type for the part "file" in the multi-part request body:

Content-Disposition: form-data; name="file"; filename="test.pdf"

If the tool cannot do it, you could investigate, if it is possible to change the MIME type by the node creation callback in OScript.

Adev2023

any update on this issue