/
Task 3.1: Combining acquisitions units: most permissive wins

Task 3.1: Combining acquisitions units: most permissive wins

This task is designed to gather feedback on the behaviour when multiple acquisition units are assigned to the same resource (agreement or license)

Using the spreadsheet https://docs.google.com/spreadsheets/d/1aPzKeLSUv7_YiRJ2teH7OjeZ_BOYIQruTW7ta6I_hOM/edit?usp=sharing please give feedback on:

  • Any confusion about how assigning multiple acquisition units works

  • Missing information or documentation you'd like to see

  • Anything else

When creating acquisition units and agreements or licenses, please treat the names given in the instructions (Bodleian Team, Cantab Team, Science Database etc.) as suggestions. In order to avoid clashing with others carrying out the same UAT it’s better to create your own unique names for units and agreements.

Although the instructions below are for Agreements, if you are more familiar with the Licenses application you can do a similar exercise with licenses

  1. Login to Snapshot or Snapshot-2 or Eureka Snapshot Folio with the username/password: diku_admin / admin

  2. Navigate to Settings → Acquisition Units

  3. Create a new acquisition unit called "Bodleian Team" with the checkboxes for View, Edit, Create and Delete checked

  4. Create a new acquisition unit called “Cantab Team” with only Edit, Create and Delete checked

  5. Assign your user with the role-erm-admin permission set / “ERM Admin” role to both the Bodleian Team and Cantab Team acquisition units

  6. Logout, and log back in as your user

  7. Navigate to the Agreements app

  8. Create a new agreement called "Science Database Package 2026"

  9. In the agreement edit screen, locate the acquisition units field and assign both the "Bodleian Team" and “Cantab Team” acquisition units to this agreement

  10. Save the agreement and in the agreement view, locate the Acquisition units accordion and verify that both the Bodleian and Cantab Teaem acquisition units are displayed

  11. Log out and log back in as diku_admin

  12. Navigate to the Agreements app

  13. Search for the agreement, and verify that although diku_admin is not a member of the “Bodleian Team” (which protects View permissions), you can still view the agreement (because it also has the Cantab Team applied which does not restrict View, and most permissive wins)

  14. Verify that the diku_admin user cannot edit or delete the agreement (because both acquisition teams applied protect these functions and so only members of one of these teams can edit/delete the agreement)

Remember, the point of this task is to allow you to explore the functionality available, so feel free to vary the task and add any feedback you have to the spreadsheet.