Bug #5831


Address "inherited" access policy on data entities

Added by ben leinfelder about 11 years ago. Updated about 11 years ago.

morpho - general
Target version:
Start date:
Due date:
% Done:


Estimated time:


There is an "inherit from metadata" choice when editing data access policy. This worked when we knew Metacat was handling the package and would enforce the EML rules for everything in the datapackage. But DataONE doesn't have the same notion -- all the obejcts fend for themselves using whatever SM.AccessPolicy they have.

My inclination is to remove this option but that raises some concerns:
-what should the default policy be for data files? (I say private)
-would it be more convenient to let people duplicate their sciMeta access rules to the sciData objects?

Related issues

Blocks Morpho - Bug #5824: Call CN.setAccessPolicy() when editing accessResolvedben leinfelder01/25/2013

Actions #1

Updated by ben leinfelder about 11 years ago

I think the best approach is to remove the "inherit" choice in the entity access screen so that we do not give the user false expectations where they think that if they edit the sciMeta access the data access will follow suit.

For new data entities I think we should copy the sciMeta access rules when the data import wizard completes and apply them to the data object. From then on, modifications to either are completely independent.

Actions #2

Updated by ben leinfelder about 11 years ago

Removed inherit option from the data entity access control screen.

Need to check if the data import wizard will copy the access rules from the EML.

Actions #3

Updated by ben leinfelder about 11 years ago

The data table import copies the access rules, but the other entity import does not.

Actions #4

Updated by ben leinfelder about 11 years ago

Actually -- more investigation is needed here. They seem to be treated the same but I am seeing different results as I test the import.

Actions #5

Updated by ben leinfelder about 11 years ago

Both dataTable and otherEntity now use the EML's SM (including AccessPolicy) as a template for their entity SM. This is a one-time thing at the time of data import. Subsequent changes to the EML's access policy will not cascade to the data entities in the package.

Actions #6

Updated by Redmine Admin almost 11 years ago

Original Bugzilla ID was 5831


Also available in: Atom PDF