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

Ability to Set a Dataset Availability Schedule #934

Closed
posixeleni opened this issue Sep 24, 2014 · 3 comments
Closed

Ability to Set a Dataset Availability Schedule #934

posixeleni opened this issue Sep 24, 2014 · 3 comments
Labels
Feature: Metadata Feature: Permissions Type: Suggestion an idea User Role: Curator Curates and reviews datasets, manages permissions

Comments

@posixeleni
Copy link
Contributor

We have a request from a user (see IRC log: http://irclog.iq.harvard.edu/dataverse/2014-09-24) to support the ability to make a dataset's files publicly available for a certain period of time (start and end date), and then restrict access to the files but keep the metadata public. This is related to Issue #343 which will allow for a user to set an embargo period date (when to make a dataset go from unpublished or restricted to published and available) but deserves a separate ticket since this feature is about how long a dataset's files should be made publicly available.

@posixeleni posixeleni added UX & UI: Design This issue needs input on the design of the UI and from the product owner Type: Suggestion an idea labels Sep 24, 2014
@posixeleni posixeleni added this to the 4.1 milestone Sep 24, 2014
@aschenbach
Copy link

Hello DVN Specialists,

It would be good to have the owner of any Dataverse project to manage the downloadable data files as well as the super admin account, this registered curator user account can set a time frame to which these data files can be locked from public access. Maybe a calendar type clickable object starting date to a closing date. I also think this lock time frame will need to be flexible as well. This feature can be turned on and off any any given notice, maybe by default all files can be made publicly accessible otherwise instructed. Even when the downloadable data files are locked from public access, the metadata of the ingested study can still be viewable by the general public which is the current practice in DVN version 3.6.x. This is perfect.

My colleagues are a bit picky than i am, they also would like to see if this message area on the "Data & Analysis" tab be able to allow this curator or admin user the ability to change this text message and allow this text area to become a edible text message box: "Access to some or all of these files are restricted. See the Comments tab for more information." instead showcasing this system message. Perhaps, another edible text area where a curator person would enter in some descriptive verbiage pertaining to the reasons why these files are locked. i realized that this system message can be altered in a text file but it will affect all studies which we may not wish to show in every locked study. A customizable message for each individual study would be nice if and when the downloadable study files are lock during Embargoing.

Here are some of the key questions my colleagues are asking me. i am unclear as to the following questions can be translated into Trello card or programmable features inside Dataverse on this Embargo business.

what are some benefits or limitations there are with that feature in DVN?
For example does DVN has an admin report you can run an embargoed data?
Can we set up policies in DVN where embargoes can only last for a specified amount of time?

warm Wishes,
flo

@posixeleni
Copy link
Contributor Author

Hi @aschenbach,

Thanks so much for adding all this helpful background use case and feature suggestion information #934 (comment) to this ticket. Once we start scheduling the work for 4.1 we will definitely be looking at your comments and feedback closely and by then should hopefully be able to start answering some of the questions you included.

Best regards,
Eleni

@scolapasta scolapasta modified the milestones: In Review - Long Term, In Review - Short Term May 8, 2015
@mheppler mheppler added Feature: Metadata Feature: Permissions and removed UX & UI: Design This issue needs input on the design of the UI and from the product owner labels Jan 27, 2016
@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@pdurbin pdurbin added User Role: Curator Curates and reviews datasets, manages permissions and removed zTriaged labels Jun 30, 2017
@djbrooke djbrooke closed this as completed Dec 3, 2017
@pdurbin
Copy link
Member

pdurbin commented Dec 4, 2017

If anyone is curious why this issue was closed, please see #4052 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Metadata Feature: Permissions Type: Suggestion an idea User Role: Curator Curates and reviews datasets, manages permissions
Projects
None yet
Development

No branches or pull requests

6 participants