[NXP-22746] Handle blobs in lists and complex types within the CSV Importer - Nuxeo Issue Tracker

XML

Word

Printable

Release Notes Description:
Hide

By using a JSON format like

"[{\"file\":{\"name\":\"Meeting.pdf\",\"mime-type\":\"application/pdf\",\"content\":\"dummyContentForMyBlob\"}}]

, we can now import files in the attachment part of the File document (or any of your customized document type), while only the main file:content property could be filld using Nuxeo CSV impoter before.
Show
By using a JSON format like "[{\" file\ ":{\" name\ ":\" Meeting.pdf\ ",\" mime-type\ ":\" application/pdf\ ",\" content\ ":\" dummyContentForMyBlob\"}}] , we can now import files in the attachment part of the File document (or any of your customized document type), while only the main file:content property could be filld using Nuxeo CSV impoter before.
Tags:
Backlog priority:
800
Sprint:
nxfit 9.3.2
Story Points:
5

Currently, only straight content metadata, like file:content, can be mapped to blobs thanks to this code from CSVImporterWork#convertValue

It should be extended to content metadata inside list or complex types, like files:files

By using a JSON format like

"[{\"file\":{\"name\":\"Meeting.pdf\",\"mime-type\":\"application/pdf\",\"content\":\"dummyContentForMyBlob\"}}]

, it is possible to return a StringBlob to CSVImporterWork#convertValue, which could transform it to a File object usable by the CSV Importer.

Estimated:

Remaining:

Logged:

2d 6h