IRB Offices
This tutorial shows you how to add a selector UI element to an IRB administrative office to enable selection of the correct IRB Exchange account from the ones you've configured in your store.
In Huron IRB, the site may have multiple IRB offices configured in the Admin Office custom data type. In this situation, each submission is assigned to a particular IRB office. Having separate offices limits IRB staff's visibility of submission data by showing a submission only to staff members associated with the IRB office assigned to the submission.
When using the IRB Exchange, submissions are uploaded to and downloaded from the IRB Exchange using an account that is linked to the IRB office assigned to the submission. Therefore administrators must select the IRB Exchange account name to assign to each IRB office in your site that wishes to participate on the IRB Exchange.
When This Applies
This tutorial is targeted at customers who have implemented IRB offices, but do not plan on installing the Committee Meeting 8.1.3 module. Committee Meeting 8.1.3 contains all the necessary code and configuration for IRB offices to integrate with the IRB Exchange. Customers who plan on installing Committee Meeting 8.1.3 may skip this tutorial.
An alternative for sites with only one IRB office or without IRB offices implemented is to rely on the store's default IRB Exchange account for all operations that interact with the IRB Exchange.
What's Involved
Much like adding the IRB Exchange account selector to institutional profiles, adding the IRB Exchange account name selector to IRB offices involves these parts:
- Creating a string attribute to store the IRB Exchange account name on the IRB office.
- Binding a hidden control on the view used on IRB office to the attribute you create.
- Adding a SymLink on the view used on IRB office for the IRB Exchange account name selector.
Adding the SymLink
Office Type = Institutional Review Board
to hide the IRB Exchange account name selector for admin offices of other solutions.
SymLink HTML Example:
<img _atei_dontuse="Target = Applications:/IrbExchange/AccountNameChooser" alt="Applications:/IrbExchange/AccountNameChooser" class="group" layoutid="SymlinkControl:6B3BD3D7B915E44598E7BD0E81387A6E" linktarget="Applications:/IrbExchange/AccountNameChooser" staticqs="sourceAttribute=customAttributes.iRBExchangeAccountName&updateFormField=_AdminOffice.customAttributes.iRBExchangeAccountName" />
In this example, the staticqs attribute has some important metadata used by the Site Designer page.
sourceAttribute
should be set to the fully qualified attribute path to the string attribute you create.updateFormField
should be set to the fully qualified attribute path to the string attribute you create, starting with the internal type name of your IRB office type.