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: Provide an "Open Access" badge on a dataset page #9943

Open
dozed opened this issue Sep 22, 2023 · 1 comment
Open
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Feature: Metadata Type: Suggestion an idea User Role: Guest Anyone using the system, even without an account 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

@dozed
Copy link

dozed commented Sep 22, 2023

Overview of the Feature Request

It would be nice to mark "open access" dataset as such, for example with a badge.

This is how Zenodo does it:

Screen-Shot-2023-09-21-at-1 56 55-PM

Any open or closed issues related to this feature request?

One issue is how to classify a dataset as (non-)open access.

A possible idea would be: a dataset is open access, if

  • an appropriate license is used, e.g. CC-0, and
  • all files are public/non-restricted

Having a controlled vocabulary would be useful here, so this seems relevant:

@pdurbin pdurbin added UX & UI: Design This issue needs input on the design of the UI and from the product owner Type: Suggestion an idea Feature: Metadata User Role: Guest Anyone using the system, even without an account Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF labels Oct 13, 2023
@CB-HAL
Copy link

CB-HAL commented Nov 28, 2023

We would also be in favour of such a feature. At the moment we add “(OA edition)” in the title to indicate open access data. An automatic classification with public/non-restricted or the licence information is maybe not always possible. E.g. we use for Open Access data a custom licence, because we have additional information in the licence text. A manual classification is maybe a better solution, similar to the file tags, but the open access badge should mark the whole dataset. It would also be a good idea to have this information in the OAI-PMH export. The CESSDA data catalogue plans to integrate the information of open or restricted data, including this information via the OAI-PMH DDI endpoint would be an appropriate solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Feature: Metadata Type: Suggestion an idea User Role: Guest Anyone using the system, even without an account 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
Status: 🔍 Interest
Development

No branches or pull requests

3 participants