Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Name: Enter Policy name.
  2. Description: Enter the policy description for future reference and understanding by other users.
  3. Select the policy type: The user can select one of the following policy types:
    1. TYPE_SUBMISSION: a policy in place during the submission
    2. TYPE_WORKFLOW: a policy in place during the approval workflow
    3. TYPE_INHERITED: a policy that has been inherited from a container (the collection)
    4. TYPE_CUSTOM: a policy defined by the user during the submission or workflow phase
    5. null: if the information is not available
  4. Select the action type: The user can select one of the following actions from the drop-down list:
    1. READ - Ability to view the specific object
    2. WRITE - Ability to edit the specific object
    3. ADD - Ability to add an object to another object (valid for Collections & Communitiesa parent object (e.g. add a Bitstream to a Bundle, add a Bundle to an Item, add an Item to a Collection , add a Collection to a Community, etc.)
    4. REMOVE - Ability to remove an object from another a parent object (valid for Collections and Communitiesi.e. the opposite of "ADD")
    5. ADMIN - Full Admin permissions on the specific object
    6. DELETE - Ability to delete the specific object
    7. WITHDRAWN_READ - Ability to view a withdrawn Item (only valid for Items)
    8. DEFAULT_BITSTREAM_READ - Default "READ" permissions added to any Bitstreams of a newly submitted Item (only valid for Collections)
    9. DEFAULT_ITEM_READ - Default "READ" permissions added to any newly submitted Item (only valid for Collections)
  5. Start date – end date: The user can select a start date and end date for using the policy, should they want to apply it for a fixed period.
  6. The eperson or group granted the permission is the list of users/groups granted authorization under the policy.
  7. Search for an ePerson / Search for a group: Click on the "ePerson" or "group" to search for the entity.
  8. Search field: Enter keywords to search for the ePerson/Group.
  9. ePerson/Group list: Click on the select button against the user/group you want to add to the policy
  10. Submit/Cancel button: Click on the "Submit" button to complete policy creation or click on the Cancel button to cancel the entire process.

...

  1. Name: Enter Policy name.
  2. Description: Enter the policy description for future reference and understanding by other users.
  3. Select the policy type: The user can select one of the following policy types:
    1. TYPE_SUBMISSION: a policy in place during the submission
    2. TYPE_WORKFLOW: a policy in place during the approval workflow
    3. TYPE_INHERITED: a policy that has been inherited from a container (the collection)
    4. TYPE_CUSTOM: a policy defined by the user during the submission or workflow phase
    5. null: if the information is not available
  4. Select the action type: The user can select one of the following actions from the drop-down list:
    1. READ - Ability to view the specific object
    2. WRITE - Ability to edit the specific object
    3. ADD - Ability to add an object to another object (valid for Collections & Communitiesa parent object (e.g. add a Bitstream to a Bundle, add a Bundle to an Item, add an Item to a Collection , add a Collection to a Community, etc.)
    4. REMOVE - Ability to remove an object from another a parent object (valid for Collections and Communitiesi.e. the opposite of "ADD")
    5. ADMIN - Full Admin permissions on the specific object
    6. DELETE - Ability to delete the specific object
    7. WITHDRAWN_READ - Ability to view a withdrawn Item (only valid for Items)
    8. DEFAULT_BITSTREAM_READ - Default "READ" permissions added to any Bitstreams of a newly submitted Item (only valid for Collections)
    9. DEFAULT_ITEM_READ - Default "READ" permissions added to any newly submitted Item (only valid for Collections)
  5. Start date – end date: The user can select a start date and end date for using the policy, should they want to apply it for a fixed period.
  6. The eperson or group granted the permission is the list of users/groups granted authorization under the policy.
  7. Search for an ePerson / Search for a group: Click on the "ePerson" or "group" to search for the entity.
  8. Search field: Enter keywords to search the ePerson/Group.
  9. ePerson/Group list: Click on the select button against the user/group you want to add to the policy
  10. Submit/Cancel button: Click on the "Submit" button to complete policy creation or click on the Cancel button to cancel the entire process.

...