Module: Pipeline::InboxGroupedBySubmission

Included in:
CherrypickingPipeline
Defined in:
app/models/pipeline/inbox_grouped_by_submission.rb

Overview

A pipeline that has its inbox grouped by submission needs to provide specific paging capabilities. All requests for a submission must appear on the same page, i.e. if a submission has 200 requests and there are only 100 allowed per page, then all of these requests must appear on a page and not across two.

Class Method Summary collapse

Class Method Details

.included(base) ⇒ Object 



7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
 
# File 'app/models/pipeline/inbox_grouped_by_submission.rb', line 7

has_metadata do
  # NOTE: The following attribute is not required for Microarray Genotyping.
  # I think this might be broken and suggests that there should be separate classes for project: one for
  # next-gen sequencing that includes this attribute in it's metadata, and one for microarray genotyping
  # that doesn't.
  include ProjectManager::Associations
  include BudgetDivision::Associations

  custom_attribute(:project_cost_code, required: true)
  custom_attribute(:funding_comments)
  custom_attribute(:collaborators)
  custom_attribute(:external_funding_source)
  custom_attribute(:sequencing_budget_cost_centre)
  custom_attribute(:project_funding_model, in: PROJECT_FUNDING_MODELS)
  custom_attribute(:gt_committee_tracking_id)

  before_validation do |record|
    record.project_cost_code = nil if record.project_cost_code.blank?
    record.project_funding_model = nil if record.project_funding_model.blank?
  end
end