[
https://issues.apache.org/jira/browse/AIRAVATA-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989117#comment-16989117
]
ASF subversion and git services commented on AIRAVATA-3281:
-----------------------------------------------------------
Commit cdfe35bb95db2c68956d2b18cb75e138b7b5aa46 in airavata-django-portal's
branch refs/heads/master from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=cdfe35b ]
AIRAVATA-3281 Fix typo
> Capture and use mime-type for input and output files
> ----------------------------------------------------
>
> Key: AIRAVATA-3281
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3281
> Project: Airavata
> Issue Type: Bug
> Components: Django Portal
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
>
> h2. Proposal
> - store {{mime-type}} in {{DataProduct.productMetadata}}
> - For input files, {{mime-type}} value is whatever is present in the upload
> request. (Perhaps can also come from application interface's
> {{InputDataObjectType.metaData['file-metadata']}}).
> - For output files, {{mime-type}} value comes from
> {{OutputDataObjectType.metaData['file-metadata']}}. When output data staging
> register the DataProduct, it will need to read the
> OutputDataObjectType.metaData and copy the file-metadata to the DataProduct's
> productMetadata
> - in Django portal, when downloading data product, if metadata has
> {{mime-type}} then use that as the content type. Otherwise, set the content
> type to {{application/octet-stream}} and add a {{Content-Disposition}} header
> with value {{attachment; filename=...}} (which is what is currently happening
> all the time).
> h3. Other details
> - Django portal should retain DataProduct metadata when moving or copying
> input files
> - The DataProduct download URL will accept a {{download}} query param to
> force download even when there is a mime-type in metadata
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
