...
The next step is to note the gap between the above Authorizations and the way the project wants to manage Authorizations. Somehow we need to get from Issues and Holds to Organizations.
Syncing Authorizations
...
Bouncing Off The Organization Wall
Working from the Organization side, the service architect needs to map Organizations to Issues. While there is an owning Organization in the Issue, it doesn't capture the nuance that separate Organizations have access to place and remove Holds. She is already aware that this translates into create and update operations. Perhaps this can be done using an OsidRecord.
organizationIssueRecord | |||
| Method | getHoldCreatorOrganizationIds | ||
|---|---|---|---|
| Description | Gets the list of Organization Ids who can create Holds using this Issue. | ||
| Return | osid.id.IdList | the list of Organization Ids | |
| Compliance | mandatory | This method must be implemented. | |
| Method | getHoldCreatorOrganizations | ||
| Description | Gets the list of Organizations who can create Holds using this Issue. | ||
| Return | osid.personnel.OrganizationList | the list of Organizations | |
| Errors | OPERATION_FAILED | unable to complete request | |
| Compliance | mandatory | This method must be implemented. | |
| Method | getHoldUpdaterOrganizationIds | ||
| Description | Gets the list of Organization Ids who can update Holds of this Issue. | ||
| Return | osid.id.IdList | the list of Organization Ids | |
| Compliance | mandatory | This method must be implemented. | |
| Method | |||
| Description | Gets the list of Organizations who can update Holds of this Issue. | ||
| Return | osid.personnel.OrganizationList | the list of Organizations | |
| Errors | OPERATION_FAILED | unable to complete request | |
| Compliance | mandatory | This method must be implemented. | |