The Benchling Request application is used to seamlessly manage almost any type of assay or task request between organizational teams or users.
Establishes formal request system
Streamlines and standardizes the request fulfillment process
Integrated with ELN, Registry and Workflows
Requestor: The user making the request
Fulfiller: The user fulfilling the request (i.e., who the request is assigned to)
Examples of Common Requests
Scientist A wants to perform an assay on a registered cell line
Production / Process requests:
Scientist B wants the Viral Production Core to produce a viral vector with specific properties
Scientist C wants the DNA Core to sequence a registered plasmid
Scientist D wants the Protein Sciences team to purify a protein
Components of a Request
A Request is currently composed of four main parts:
1) Default Request Fields
Project Name: When a request is made, it will be associated with a project. This project is where this request will inherit its permissions
"Assigned to": Requestors can assign a request to another Benchling user or team, who will receive an email. This means you do not need to create an "assigned to" field during Request schema configuration.
2) Configurable Request Fields
Similar to Registry fields, there are multiple types of fields that can be configured on a Request, including dropdowns.
Avoid using entity links in Request fields for samples, instead use a Sample Table
A configurable action within the request that can be assigned to samples
Can only have tasks if there is a Sample Table in the Request
Can also have fields within tasks
4) Sample Table
If registered entities, batches, or containers are included in request, they can be added to the sample table at the bottom of the request. Usually these are samples that will be produced or otherwise used in the execution of the request
Tasks added to the request can be assigned to samples via check boxes
You can also configure Request Templates to define default values for new requests.