Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent term for .tab format #6330

Closed
TaniaSchlatter opened this issue Oct 31, 2019 · 8 comments
Closed

Inconsistent term for .tab format #6330

TaniaSchlatter opened this issue Oct 31, 2019 · 8 comments
Labels
Type: Bug a defect UX & UI: Design This issue needs input on the design of the UI and from the product owner

Comments

@TaniaSchlatter
Copy link
Member

On the dataset page, we refer to tabular files as "Archival format (.tab)" in the dataset level dropdown, and "Tab-Delimited" in the file dropdown. Are these the same format? If so, we should pick and use one term for both.

Screen Shot 2019-10-31 at 12 49 13 PM

Screen Shot 2019-10-31 at 12 49 06 PM

@TaniaSchlatter TaniaSchlatter added Type: Bug a defect UX & UI: Design This issue needs input on the design of the UI and from the product owner labels Oct 31, 2019
@TaniaSchlatter TaniaSchlatter changed the title Inconsistent term for tab format Inconsistent term for .tab format Oct 31, 2019
@pdurbin
Copy link
Member

pdurbin commented Oct 31, 2019

I agree with the comment by @adam3smith at #2720 (comment) and think we should switch from .tab to .tsv. It's much more standard.

@adam3smith
Copy link
Contributor

It already gives you the same format (.tab) right now. Switching this to .tsv would indeed be the right thing to do (and just to be clear, that's just a different extension for literally the same file), but wouldn't by itself address the issue @TaniaSchlatter raises here.

So to explain the slightly different naming/dialog:

  • The first one is for multiple files/potentially a whole dataset, which can have different file formats in it (e.g. .xlsx, .dta, etc.) and gives the user the possibility to download the whole dataset as is or with normalized .tab tabular files. Most people will probably want the original format here, e.g. as part of a reproducibility package.
  • The second one is for an individual file and allows the user additional download options such as the DDI and .RData format. For an individual file, a user may well want the .tab/.tsv -- it's easy to read into statistical software.

What you don't want to lose in making these labels more consistent is that they currently convey to the user that for the whole dataset they'll typically want the "Original format" but for the individual file, tab delimited is an option that's not merely "archival". Not sure if this is helpful. I tried to think of a single, unified label, but couldn't come up with anything I liked.

@TaniaSchlatter
Copy link
Member Author

Also noting the inconsistency in wording between "Original Format" and "Original File Format (Stata 14 Binary)"

@pdurbin
Copy link
Member

pdurbin commented Dec 5, 2019

https://twitter.com/Ray_J__/status/1202296388618457089 illustrates why Dataverse should use .tsv instead of .tab for tab-separated files. Here's a screenshot:

Screen Shot 2019-12-04 at 10 34 40 PM

@TaniaSchlatter
Copy link
Member Author

Recent prototype testing makes it clear that we need to specify the file format type, regardless of what it is, when we say "Archival Format", i.e. "Archival Format (.tab)"

@pdurbin
Copy link
Member

pdurbin commented Jun 29, 2020

I just thought I'd mention that this issue is on my mind as I chew on the following bullet from #6118

  • New options for “Download”, or “Download Original Files” and “Download Archival Format” under the Access Dataset btn

@pdurbin
Copy link
Member

pdurbin commented Oct 4, 2022

@cmbz
Copy link

cmbz commented Aug 20, 2024

To focus on the most important features and bugs, we are closing issues created before 2020 (version 5.0) that are not new feature requests with the label 'Type: Feature'.

If you created this issue and you feel the team should revisit this decision, please reopen the issue and leave a comment.

@cmbz cmbz closed this as completed Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug a defect UX & UI: Design This issue needs input on the design of the UI and from the product owner
Projects
None yet
Development

No branches or pull requests

4 participants