Bug #5881


How can we change the access policy for the resource map document

Added by Jing Tao about 11 years ago. Updated almost 11 years ago.

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


Estimated time:


When we create a data package with a data object by the new data package wizard and entity wizard, a resource map document will be generated as well.

Morpho has explicit ways to change the the access policy for the metadata and data objects. There is no explicit ways to modify the access policy for the resource map document. I guess we has implicit way for the resource map - it will be modified when you modify the access rules for the metadata object (eml document). However, this doesn't work. After i successfully modified the metadata's access policy, the resource map doesn't change.

Actions #1

Updated by Matt Jones about 11 years ago

Making it match the EML document is the best course for now I think. It will be confusing to have a separate approach for packages than EML.

Actions #2

Updated by ben leinfelder about 11 years ago

Now setting the ORE permissions when setting EML permissions on the CN. Using the naming convention where "resourceMap_" is prepended to the EML identifier. This is fragile. Perhaps we can look up the ORE identifier from the CN since it has query capabilities that should expose this information.

Actions #3

Updated by Jing Tao almost 11 years ago

I just tested to change a local data package's access policy. The resource map file still keeps the same. In other word, changing the local eml document's access policy doesn't change the local resource map file.

Actions #4

Updated by ben leinfelder almost 11 years ago

I hadn't written code to do that since I thought no one would ever see it, but if we save a local package to the network, those access rule will apply. I will add code to the local data store to handle local setAccess for ORE. Thank you

Actions #5

Updated by ben leinfelder almost 11 years ago

Now saving the ORE systemMetadata changes locally when setting access policy and replication policy.

Actions #6

Updated by Redmine Admin almost 11 years ago

Original Bugzilla ID was 5881


Also available in: Atom PDF