Project

General

Profile

Feature #6945

MNRead.get uses the pid for the download filename, which provides a less that optimal user experience when the pid is an opaque identifier such as DOIs, uuids, etc.

Added by Peter Slaughter almost 7 years ago. Updated almost 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2015-03-23
Due date:
% Done:

0%

Story Points:
Sprint:

Description

MNRead.get uses the pid for the download filename, but should use the EML objectName for the filename. This is currently done for each component filename in MNPackage.getPackage(), which provides
much more user-friendly filenames than a uuid, DOI or other similar identifier.

History

#1 Updated by Dave Vieglais almost 7 years ago

EML is one format supported by DataONE. Perhaps rephrase this to indicate that the content disposition header in the http response may suggest a filename alternative to the pid as recorded in the metadata and the client should utilize this information when available.

#2 Updated by Peter Slaughter almost 7 years ago

  • Subject changed from MNRead.get() should use EML objectName as downloaded file name to MNRead.get uses the pid for the download filename, which provides a less that optimal user experience when the pid is an opaque identifier such as DOIs, uuids, etc.

MNRead.get uses the pid for the download filename. Possibly the content disposition header in the http response may suggest a filename alternative to the pid as recorded in the metadata and the client should utilize this information when available.
For example, if the object is described by an EML document, the objectName element may provide a more meaningful filename for the user than an opaque id.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)