To manage your resource allocation processes, there is a minimum set of data that XRAS needs to know. At the moment, you will need to provide some of this information to the XRAS team, but we are working to provide interfaces that will allow you to enter and edit these values. You will find most of these interfaces by selecting “Client Settings” under the XRAS gear menu.
| Table of Contents |
|---|
Data Provided via the XRAS Team
...
Initial Allocation Administrator (required). When first configuring XRAS, you must designate someone from your organization to be an Allocation Admin. Once that person has been given administrative access to XRAS Admin, they can grant admin access to others.
Allocations Process and Client information (required). Your institution’s name; your preferred abbreviation for your institution; your institution’s logo; your institution’s contact help email. The abbreviation is displayed on the Submit, Review, and Admin interfaces and used in the default URLs (https://submit-orgAbbrev.xras.org, https://review-orgAbbrev.xras.org, https://admin-orgAbbrev.xras.org). Even if hosting your own submit interface, we will still create and host the Review and Admin sites for you.
Allocation Process Manager (required for Notifications). An email address or email list to which XRAS will send notifications targeted for your site’s allocation administrators.
Action Types. The By default, XRAS will include the standard set of actions with which users make requests or manage their allocations. XRAS currently recognizes new and renewal requests as well as transfer, extension, supplement, appeal, and advance actions, as well as actions to allow researchers to submit progress reports and final reports. Review Form Fields. You can define the template and field types (text area, calendar, etc.) that your reviewers need to complete when entering a review. You can customize the form per allocation type and action type. You will likely provide these details once you’ve customized XRAS with your allocation types and other detailsAny desired customization to the display names of these actions, as well as additional optional actions, should be discussed with the XRAS team.
Fields of Science. If your institution requires selecting a primary and, optionally, a secondary field of science when submitting a project allocation request, you can provide a custom list of fields and their abbreviations.
Default resource reviewers. You can configure XRAS to speed up the review process of an allocation request by defining default reviewers for requests asking for a given resource. If you are interested in this feature, please contact at allocations@access-ci.org. After a final submission, designated resource default reviewers are automatically assigned to those submissions that requested those particular resources. These reviewers are notified by email when they receive assignments.
Client Settings
The following settings can be customized to your site’s preferences by you or another XRAS Admin. These features are available under the XRAS gear menu by selecting “Client Settings.” Further customization can be managed via the Rules interfaces.
...
Finally, you must ensure that your resource(s) in the Cyberinfrastructure Description Repository (CIDeR) have a public page or other persistent identifier associated with them.
...
Available Resources. For each allocation type, you must specify which of your resources can be requested in opportunities of that type. To associate resources with a given allocation type, you must configure those settings in the Cyberinfrastructure Description Repository (CIDeR). See the CIDeR appendix for instructions. At any time, you can check which resources are being offered as part of an allocation type by using the Available Resources tab on the Allocation Type page.
...
You can customize the document types associated with your allocations policies. The Document Types interface under Client Settings allows you to add and remove document types that can be associated with your different allocation types. The “Display Name” entered for the document will be shown in Submit, Review, and Admin components. (To define which documents are required or optional for each allocation type, use the Rules interface for Required/Optional Documents.)
Grant Types
You can provide another level of categorization to your projects with Grant Types. For example, you may have a “Small” allocation type that you use for many purposes. By defining Grant Types, you can have the submission form ask requesters to state a kind or purpose the Small allocation. The Small allocation might be for “Classroom” use, for “Software Development,” or other purpose that you want to track. Grant Types are different from Category Types in than Grant Types are external facing (selected by researchers and requesters), while Category Types are internal facing (used by administrators and reviewers to support the allocations workflow).
Person Status Types
When creating new users to be associated with an allocation request, a user’s status type (Graduate Student, Faculty, ...) can be selected. You can use these person status types in XRAS rules to define, for example, who is eligible to submit an allocation request. XRAS allows admins to create a comprehensive list of categories a user may fall under, such as “Faculty,” “University Research Staff,” and “Graduate Student.” These values should match those used in your local account management system and passed via the Identity Service endpoints to XRAS.
...
You can specify an optional allocations policy documentation page that you would like to be visible to your allocation reviewers in the XRAS Review UI.
Meeting Review Tags
The optional tags that are available for use in the Meeting UI App of XRAS Review are controlled via this tool. You can add new tags and activate /inactive or inactivate tags that are already defined. You can define tags to help manage the handling of requests during a meeting. For example, you might define tags for “approved in full” or “rejected” to help designate these outcomes quickly, instead of typing out notes.
Reviewer Agreement
The Reviewer Agreement tool allows you to create an Agreement that Reviewers will be required to agree to when logging into XRAS Review. They will be unable to use Review until they check the “I agree” checkbox.
When creating an agreement you can specify the text that the user must agree to, the length of time the agreement is good for (listed in days), and a checkbox that controls if the agreement requirement is active or not.
Custom Review Forms
By default, XRAS defines a review form with a single long-text field for all action types. XRAS provides a user interface to let you define and manage customized review forms for use on XRAS Review. These forms allow you to add multiple types of custom questions for reviewers to fill out as part of their review.
When creating a new Custom Review Form you will be asked to specify which combination of Action Type, Allocation Type, and Review Phase you want the review form to apply to. You only need to specify one of these to create a review form and each additional selection will increase the specificity of the rule. For example if you choose “New” for the action type, the form will appear for all requests that have an action type of “New”. If you specify “New” for the action type and “Research” for the allocation type, the custom form will only appear for requests that match both of those options.
There are A Custom Review Form has two general options for a Custom Review Form: “Form Active” and “Uploads Enabled”. Checking the “Form Active” box will allow the form to display for reviewers in XRAS Review. Checking the “Allow Uploads” box allows reviewers to upload documents as part of their review.
...