Implement discoverability rules for search/browse in 4.0 (permissions)

[eaquigley]

---

Author Name: Philip Durbin (@pdurbin)
Original Redmine Issue: 3464, https://redmine.hmdc.harvard.edu/issues/3464

Original Assignee: Philip Durbin

---

The rules are being finalized here: https://trello.com/c/CkRb3dYl/49-define-search-browse-permissions-discoverability-rules

In previous discussions around Lucene, we started looking at these links to help us implement the rules we want:

• http://www.javaranch.com/journal/2009/02/filtering-a-lucene-search.html
• http://lucene.apache.org/core/3_0_3/api/all/org/apache/lucene/search/Filter.html
• http://lucene.apache.org/core/3_5_0/api/all/org/apache/lucene/search/TermsFilter.html

---

Related issue(s): #341, #380
Redmine related issue(s): 3430, 3756, 3795

---

[eaquigley]

---

Original Redmine Comment
Author Name: Philip Durbin (@pdurbin)
Original Date: 2014-04-28T20:40:05Z

---

The main reason we moved this out of beta is that permissions are not fully implemented. For now, we're looking the creator of dataverse or dataset to decide whether or not it should be discoverable before it has been published. See also #3795 which has a lot of permissions-related code.

The main commit where we starting using the Solr JOIN feature is this one:

some discovery rules for search/browse #3464 · 2505cb7 · IQSS/dataverse - 2505cb7

See also http://lucene.472066.n3.nabble.com/document-level-security-filter-solution-for-Solr-td4126992.html#a4127576

[pdurbin]

Some thinking from https://docs.google.com/spreadsheet/ccc?key=0AvqMYwdHFZghdFNpVDNvcnh4cTZ5amFwdkExcDU1Q1E&usp=sharing

Please note that "Anonymous" also covers "logged in but no explicitly granted read or write access".

[pdurbin]

For Beta 9 anyway, we are not inheriting permissions from parent dataverse because permissionRoot was hard-coded to true in fb7e65f

In the Google Spreadsheet I added a new sheet for Beta 2 and will attached a screenshot below to show the expected behavior.

Passing to QA.

[pdurbin]

Also, "unpublished" can mean "deaccessioned" so in the screenshot below, when it says "yes" for either "draft" or "deaccessioned", this should mean that people with ViewUnpublishedDataset permission should be able to them:

This screenshot comes from https://docs.google.com/document/d/1lFcwjtdGIqqQLYYnwtTI2GZNzmzYlrnMk2omGcXO9oY/edit?usp=sharing

[esotiri]

Created View unpublished DV and DS role, assigned the role to user and iterated through the list of cases from the google spreadsheet:
Anonymous/Logged In But No Explicit Access > ok
ViewUnpublishedDataverse on self > ok
ViewUnpublishedDataverse on parent > on
ViewUnpublishedDataverse on grandparent > ok
ViewUnpublishedDataset on self > ok
ViewUnpublishedDataset on parent > ok
ViewUnpublishedDataset on grandparent > ok

[esotiri]

I can't test deaccession part of this ticket because of a 500 error on deaccessioning. Opened a new one to fully test the feature #1209