https://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2015-03-23T23:00:05ZDataONE TasksDataONE API - 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.https://redmine.dataone.org/issues/6945?journal_id=248012015-03-23T23:00:05ZDave Vieglaisdave.vieglais@gmail.com
<ul></ul><p>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.</p>
DataONE API - 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.https://redmine.dataone.org/issues/6945?journal_id=248022015-03-23T23:37:36ZPeter Slaughterslaughter@nceas.ucsb.edu
<ul><li><strong>Subject</strong> changed from <i>MNRead.get() should use EML objectName as downloaded file name</i> to <i>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.</i></li></ul><p>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.<br>
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.</p>