LRR Queue SOP

Once the template has been selected and applied from the Library Request field to the new Build Request, take the following steps to begin processing the Build Request.

1. Ensure the ID has added the details of the build in the description.
   • It should be visible and easily copy pasted from the description box - no attachments allowed.
2. Open the course project (linked at top) in a new tab. On the course project page:
   • Look for the Review & Approve Design tasks near the bottom of the Course Design section.
   • Briefly review any that have comments.
   • Note the latest date among those.
   • Copy the task link of one that has the latest date (choose one if multiple).
3. In the Task Management subtask:
   • Add a dependency using the Review & Approve Design task link copied from the course:
     • In the Dependencies section near the top, click the plus sign.
     • Ensure pre-text is "Blocked by."
     • Paste the task link into the field, selecting the full Asana task that displays below the pasted link.
   • Assign yourself to the subtask.
   • Set the subtask due date.
     • If the CDG is approved, set the due date approximately 1 week out. (Or to align with the overall Build Request due date.)
     • If the CDG is not approved, align the due date to the Review & Approve Design due date. (You can continue to adjust this date as needed.)
4. Review the content and/or links in the Description field of the build request task.
   • Briefly review for abstract-only items, external links that lack a corresponding Asana permission link, or other items of note. (Some additional issues might be found during more in-depth review in the Build Guide and other subtasks.)
   • If a library resource appears to be no longer available, have a librarian confirm (by direct communication, assigning the Librarian Review task, etc.) that the resource is no longer available.
5. Update the parent task Issues field with any relevant issues as needed.
   • CDG not approved - The CDG was not yet approved upon task submission.
   • Citation corrections needed - The request lacks persistent links and/or correct citations.
   • Pending permissions - External source(s) are included but don't yet have an Allowed status (or haven't been submitted).
   • Large/complicated build - The request is longer or more complicated than the average build.
6. Communicate with the ID, noting any issues. If applicable, inform the ID that we'll start the build and note any adjustments that may be needed to the due date.
   • Thanks for submitting this, ID. We will get started on this once the CDG review is complete.
   • Thanks for submitting this, ID. For the two external resources, can you please link the permission requests beneath the items in the Description field? We will get started on this once those have been cleared and the CDG review is complete.
   • Thanks for submitting this, ID. Unfortunately, the Week 2 resource below is no longer available through the library, so please feel free to submit an LRR research request for help finding a replacement. We'll get started on this once the CDG review is complete. (Paste citation/resource for their reference.)
   • Thanks for submitting this, ID. We will get started. We’ve adjusted the due date a bit to allow for library processing.
7. When a CDG is approved, set subtask due dates as appropriate.
   • Set the Task Management subtask due date for approximately one week from the date the CDG is confirmed as approved (Or to align with the overall Build Request due date).
   • Set remaining subtasks - from Build Guide to Tech Review - to fall in between the current date and the Task Management due date. (You can double up on subtasks when necessary, such as assigning Build Guide/Librarian Review for one date, ID Review/Make Requested Edits for another date, etc.)
8. Once the build request and resource list are finalized, select and copy all relevant build instructions and content from the description area to the Build Guide subtask.
   • Paste the resources list and build instructions into the subtask. Clean up spacing, ensure the request is clear and formatting is consistent, and include additional details or guidance, if needed.
9. Assign subtasks based on the individuals' roles and considering their current workload.
   • Build Guide
     • Assign to the builder
   • Librarian Review
     • Assign to the builder
   • ID Review: Draft Links
     • Assign to the builder
   • Make Requested Edits
     • Assign to the builder
   • ID Review: Draft Links (2)
     • Assign to the builder
   • Tech Review
     • Assign to the tech reviewer