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: #10851

Open
DonRichards opened this issue Sep 17, 2024 · 1 comment
Open

Feature Request: #10851

DonRichards opened this issue Sep 17, 2024 · 1 comment
Labels
Type: Feature a feature request

Comments

@DonRichards
Copy link

Overview of the Feature Request

What kind of user is the feature intended for?
Guest

What inspired the request?
Current requirement from submitter.

What existing behavior do you want changed?
Modify embargos to metadata

Any brand new behavior do you want to add to Dataverse?
Add the ability to apply an embargo to just the abstract and not all of the metadata.

Any open or closed issues related to this feature request?
Not from what I've seen.

Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?
No but it has come up as a necessity.

@DonRichards DonRichards added the Type: Feature a feature request label Sep 17, 2024
@qqmyers
Copy link
Member

qqmyers commented Sep 17, 2024

@DonRichards - FWIW: Embargoes only affect files. Metadata (at least currently) is always public after publication.

Depending on your use case, perhaps the Private URL Feature, specifically the anonymized option might help? An admin can configure which metadata fields are withheld so you could include the description/abstract field (and perhaps not the others suggested).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature a feature request
Projects
None yet
Development

No branches or pull requests

2 participants