Any Affinity user is able to create a protein request by clicking “Request Proteins” in the top navigation menu
Proteins can be requested in one of three methods. Each of these methods' forms can be filled out manually, or a template can be downloaded and later imported.
The default method, By Protein, allows the user to specify any number of proteins, the amount needed in mg, and optionally a due date and any comments associated with the request.
Alternatively, users may want to request protein which is not yet registered. To this end, the user can request either By Clone or By Plate. Requesting by clone requires the user to specify a clone and one or more isotypes along with the desired amount and optional due date and comment. If more than one isotype is specified, each combination of clone/isotype will be requested separately.
The final method of requesting proteins is by plate. In this case, the user specifies a clone plate already registered in Affinity, one or more isotypes per plate, a desired amount, and an optional due date and comment. A request task will be generated for each combination of clones found in the specified plate combined with each isotype. For example, a plate with 94 clones with two isotypes specified will generate 188 unique request tasks.
Protein Request Index
Once a request is submitted, it can be found on the Protein Requests page. Each request is assigned a randomized unique ID. If the administrative setting is configured to do so, email addresses in the Protein Request Email List will also be notified at this time.
On the Protein Request Index page, the user can mark a request as complete (or undo this by marking it as incomplete), or cancel the request entirely. Filters can also be applied to view only incomplete, complete, or all requests.
Clicking the ID with direct the user to the Protein Request Details page.
Protein Request Details
The protein request details page contains all information associated with the request, and is updated as the request passes through the workflow. The requested due date and postponed to columns are populated when a request is postponed - the Due Date column throughout the production request workflow will display the new postponed date, however the request details page can be checked to determine what the original requested due date was.
