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

Feature Request/Idea: FAIR (data) view on files listings; some suggestions #8453

Open
steltenpower opened this issue Feb 28, 2022 · 3 comments
Labels
Feature: File Upload & Handling Type: Feature a feature request User Role: Hackathon Participant Core developers, frequent contributors, drive-by contributors, etc. UX & UI: Design This issue needs input on the design of the UI and from the product owner UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF

Comments

@steltenpower
Copy link

As I meet too many researchers not having much of a clue about open file formats and the breadth of what they can bring, I came up with a way of helping them in a user-friendly way within the tools they already use. Do you agree that (part of) it would be a welcome improvement to DATAVERSE perhaps?

When you read the few lines of text, you'll understand the ugly drawing
https://github.com/steltenpower/FAIRfilesListing

Looking forward to your views.

ping @TaniaSchlatter

@TaniaSchlatter
Copy link
Member

Thanks for opening this issue, @steltenpower, and for including the sketch and demos. I agree with the importance of clearly showing the file type. Is your intent to help educate researchers depositing data primarily, or looking to use data?

@steltenpower
Copy link
Author

Thanks @TaniaSchlatter, I'm glad to hear you're interested in (part of) it.

My intent is to help both sides of re-use (the one publishing the data and the many using it), depending on the tool or specific parts of it, the focus can be different however:
When somewhere in the future 'all' creation tools and operating systems have this for their file dialogs/explorers, the quality assurance part is already done there and makes less sense to repeat in Dataverse.

I hope that answers your question.
Is there anything else you need explained, or improved at that page, to take anything further?

If/when I have the time and skill to help realize parts, what page or source code file should I look at first?

@pdurbin pdurbin changed the title Feature Request/Idea: Feature Request/Idea: FAIR (data) view on files listings; some suggestions Mar 2, 2022
@pdurbin
Copy link
Member

pdurbin commented Mar 2, 2022

Neat idea. Like I said on the thread at https://groups.google.com/g/dataverse-community/c/jMt-COccvo0/m/9cR_SQg4BAAJ I like the animation at https://github.com/rickdkk/fair-file-columns (linked from @steltenpower 's README) that looks like this:

demo

@steltenpower when you're ready to set up a dev environment please take a look at https://guides.dataverse.org/en/latest/developers/dev-environment.html and please don't be shy about asking questions. We have a dev list at https://groups.google.com/g/dataverse-dev and chat at https://chat.dataverse.org

@pdurbin pdurbin added UX & UI: Design This issue needs input on the design of the UI and from the product owner Feature: File Upload & Handling UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF labels Oct 9, 2022
@pdurbin pdurbin added Type: Feature a feature request User Role: Hackathon Participant Core developers, frequent contributors, drive-by contributors, etc. labels Oct 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: File Upload & Handling Type: Feature a feature request User Role: Hackathon Participant Core developers, frequent contributors, drive-by contributors, etc. UX & UI: Design This issue needs input on the design of the UI and from the product owner UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF
Projects
None yet
Development

No branches or pull requests

3 participants