Locally FAIR Data#12319
Conversation
used when dataverse.feature.add-publicobject-solr-field is not set
# Conflicts: # src/main/java/edu/harvard/iq/dataverse/search/SolrIndexServiceBean.java
cmbz
moved this from This Sprint 🏃♀️ 🏃
to Ready for Review ⏩
in IQSS Dataverse Project
|
2026-05-20: @qqmyers could you please take a look at these merge conflicts? |
|
@qqmyers Please resolve the conflicts |
# Conflicts: # src/main/java/edu/harvard/iq/dataverse/api/Dataverses.java # tests/integration-tests.txt
stevenwinship
moved this from Ready for Review ⏩
to In Review 🔎
in IQSS Dataverse Project
|
UI looks a little funny But I'm approving the code. 
|
github-project-automation
Bot
moved this from In Review 🔎
to Ready for QA ⏩
in IQSS Dataverse Project
|
FWIW: Spacing is fixed. Looks like the existing unpublished label was top aligned (and therefore misaligned with any affiliation) and only the unpublished label had any margin. Also fixed an unrelated minor bug where a 44px size was misspelled as 44p. |
pdurbin
left a comment
pdurbin
left a comment
There was a problem hiding this comment.
Just a quick review for now about tests. I'll start diving in.
@qqmyers I requested access to this one. It's currently private. |
- native API section no longer a code block - added cross links - link to feature flag - fix bullets - adjust case for consistency
| dataverse-management | ||
| dataset-management | ||
| tabulardataingest/index | ||
| locally-fair |
There was a problem hiding this comment.
@DieuwertjeBloemen and @wshahn agree with me that Locally FAIR shouldn't be so high up and prominent in the User Guide. See https://dataverse.zulipchat.com/#narrow/channel/446770-docs/topic/where.20to.20put.20Locally.20FAIR.20docs/near/601213586
6 participants
What this PR does / why we need it: Implements the functionality described in "Locally FAIR" Data: Restricting Data Visibility in Dataverse Installations, allowing the visibility and accessibility of published collections and their published datasets/datafiles to be limited to specific groups.
Which issue(s) this PR closes:
Special notes for your reviewer: https://docs.google.com/document/d/1PPmPsAX8sbQYYdrU5s0Xc2d9YXw_5ROwkKaajT194P4/edit?usp=sharing and https://docs.google.com/document/d/1KBqRIkhRdJWCSs6wIRrnreJNLqWJoISIlqOZmDSTI9Q/edit?usp=sharing are additional resources.
Suggestions on how to test this: There are IT tests. For the UI, a superuser can add a user/group from the Collection/General Info pane and, once that's done, only the selected users should see new content in the collection. Reindexing would make existing published items disappear from search for unauthenticated users.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?: inc.
Additional documentation:
Entry point for docs: https://dataverse-guide--12319.org.readthedocs.build/en/12319/installation/config.html#dataverse-feature-allow-locally-fair-data