When the data release is standard failed: Couldn't find Study

When the data release is immediate failed: Couldn't find Study

When the data release is delayed for PhD study failed: Expected false to be truthy.

When the data release is delayed but no reasons are provided failed: Expected: "/studies"

When the data release is delayed but no reasons are provided failed: Expected: "/studies"

When the data release is delayed but no reasons are provided failed: Expected: "/studies"

When the data release is delayed but no reasons are provided failed: Expected: "/studies"

When the data release is delayed and the reasons are provided failed: Couldn't find Study

When the data release is delayed and the reasons are provided failed: Couldn't find Study

When the data release is delayed and the reasons are provided failed: Couldn't find Study

The job was canceled because "_2_1" failed.

3 source plates should be ordered by bed number and scanner has CR suffix failed: undefined method `reject' for nil:NilClass

Robot minimum volumes should be considered failed: undefined method `reject' for nil:NilClass

Source volumes should be updated once failed: undefined method `reject' for nil:NilClass

Robot minimum volumes should be considered for water failed: undefined method `reject' for nil:NilClass

Barcode scanners with carriage return should not submit page until end failed: undefined method `reject' for nil:NilClass

A study is created and it appears in Pending ethical approval true failed: Couldn't find Study

A study is created and it appears in Pending ethical approval true failed: Couldn't find Study

A study is created and it appears in Pending ethical approval true failed: Couldn't find Study

A study is created and it appears in Pending ethical approval true failed: Couldn't find Study

A study is created and it appears in Pending ethical approval true failed: Couldn't find Study

Cherrypicking pipeline where the number of plates exceeds the max beds for the robot behaves like a cherrypicking procedure running the cherrypicking pipeline Failure/Error: plates_with_samples = plates.reject { |_pid, rows| rows.values.map(&:values).flatten.all?(&:empty?) } NoMethodError: undefined method `reject' for nil:NilClass Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:339

Cherrypicking pipeline where picking by ng/µl for a tecan robot when robot is using 8-Trough buffer (Tecan v2) behaves like a cherrypicking procedure running the cherrypicking pipeline Failure/Error: plates_with_samples = plates.reject { |_pid, rows| rows.values.map(&:values).flatten.all?(&:empty?) } NoMethodError: undefined method `reject' for nil:NilClass Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:273

Cherrypicking pipeline where picking by ng/µl for a tecan robot when robot is using 96-Trough buffer (Tecan v1) behaves like a cherrypicking procedure running the cherrypicking pipeline Failure/Error: plates_with_samples = plates.reject { |_pid, rows| rows.values.map(&:values).flatten.all?(&:empty?) } NoMethodError: undefined method `reject' for nil:NilClass Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:165

Cherrypicking pipeline where there is a control plate and multiple destinations when the number of plates exceeds number of beds (Several runs) behaves like a cherrypicking procedure running the cherrypicking pipeline Failure/Error: plates_with_samples = plates.reject { |_pid, rows| rows.values.map(&:values).flatten.all?(&:empty?) } NoMethodError: undefined method `reject' for nil:NilClass Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:460

Cherrypicking pipeline where there is a control plate and multiple destinations behaves like a cherrypicking procedure running the cherrypicking pipeline Failure/Error: plates_with_samples = plates.reject { |_pid, rows| rows.values.map(&:values).flatten.all?(&:empty?) } NoMethodError: undefined method `reject' for nil:NilClass Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:435

Cherrypicking pipeline where there is a control plate and a single destination behaves like a cherrypicking procedure running the cherrypicking pipeline Failure/Error: plates_with_samples = plates.reject { |_pid, rows| rows.values.map(&:values).flatten.all?(&:empty?) } NoMethodError: undefined method `reject' for nil:NilClass Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:384

Cherrypicking pipeline where there is a control plate and a single destination when the number of plates exceeds number of beds (Several runs) behaves like a cherrypicking procedure running the cherrypicking pipeline Failure/Error: plates_with_samples = plates.reject { |_pid, rows| rows.values.map(&:values).flatten.all?(&:empty?) } NoMethodError: undefined method `reject' for nil:NilClass Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:403

Cherrypicking pipeline where there are multiple destination plates and the number of plates exceeds the max beds for the robot behaves like a cherrypicking procedure running the cherrypicking pipeline Failure/Error: plates_with_samples = plates.reject { |_pid, rows| rows.values.map(&:values).flatten.all?(&:empty?) } NoMethodError: undefined method `reject' for nil:NilClass Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:367

Cherrypicking pipeline where the number of plates does not exceed the max beds for the robot behaves like a cherrypicking procedure running the cherrypicking pipeline Failure/Error: plates_with_samples = plates.reject { |_pid, rows| rows.values.map(&:values).flatten.all?(&:empty?) } NoMethodError: undefined method `reject' for nil:NilClass Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:329

Cherrypicking pipeline where picking by ng for a tecan robot behaves like a cherrypicking procedure running the cherrypicking pipeline Failure/Error: plates_with_samples = plates.reject { |_pid, rows| rows.values.map(&:values).flatten.all?(&:empty?) } NoMethodError: undefined method `reject' for nil:NilClass Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:320

The job was canceled because "_3_1" failed.

Edit a study add external customer information Failure/Error: expect(page).to have_content('Your study has been updated') expected to find text "Your study has been updated" in "Test\nStudies\nProjects\nAdmin\nUAT\nPipelines\nBatches\nLabwhere Reception\nLab View\nLab search\nReport Fails\nBarcode\nProject\nStudy\nSample\nLabware\nAssetGroup\nRequest\nSupplier\nSubmission\nAll\nStudy 1 Edit\nEdit your study. Required fields are marked with .\nStudy owner name\nSelect an owner...\nProperties\nFaculty Sponsor\nFaculty Sponsor 1\nProgram\nGeneral\nNumber of gigabases per sample (minimum 0.15)\nPrelim ID\nPrelim ID\nReference genome\nReferenceGenome1\nTitleENA requirement\nTitle of the study as would be used in a publication.\nStudy TypeENA requirement\nNot specified\nStudy descriptionENA requirement\nSome study on something\nPlease choose one of the following 2 standard statements to be included with your data submissions (one or the other, depending on the study). If you use the second statement, replace [doi or ref] by a reference or doi for your publication:\n\nThis data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/\n\nOR\n\nThis data has been described in the following article [doi or ref] and its further analysis can be freely submitted for publication. For information on the proper use of data shared by the Wellcome Trust Sanger Institute (including information on acknowledgement), please see http://www.sanger.ac.uk/datasharing/\nIf applicable, include a brief description of any restrictions on data usage, e.g. 'For AIDS-related research only'\nAbstractENA requirement\nBriefly describes the goals, purpose, and scope of the Study. This need not be listed if it can be inherited from a referenced publication. For managed access studies, please bear in mind it’s this text in the Abstract section that will be publicly visible on the EGA website.\nStudy Visibility\nStudy VisibilityENA requirement\nHold\nPublic\nMake this ENA project public immediately.\nDo any of the samples in this study contain human DNA?\nDo any of the samples in this study contain human DNA?\nYes\nNo\nIf they do, you will be required to upload the relevant documents. This does not apply to samples that are going to have the Human DNA removed prior to analysis.\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nYes\nNo\nUsually only applicable to pathogen research when human DNA will not be sequenced and therefore does not require ethical approval.\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nYes\nNo\nAre all the samples to be used in this study commercially available, anonymised cell-lines or DNA/RNA from commercially available, anonymised cell-lines?\nDoes this study require the removal of X chromosome and autosome sequence?\nDoes this study require the removal of X chromosome and autosome sequence?\nYes\nNo\nApplicable for studies where only mtDNA and Y-chromosomal data will be submitted to EGA.\nDoes this study require y chromosome data to be separated from x and autosomal data before archival?\nApplicable for studies where Y-chromosome data will not be submitted to the EGA, or will be submitted separately from autosomal sequence.\nENA Project IDENA (see help)\nThe required PROJECT_ID accession is generated by the Genome Project database at NCBI and will be valid also at the other archival institutions. Enter 0 if the project id is unknown or not assigned.\nENA Study Accession Numbersee help\nData Release accession Number. Will be filled automatically during submission process. Provide ONLY if the project has already been submitted

Edit a study edit open study Failure/Error: expect(page).to have_content('Your study has been updated') expected to find text "Your study has been updated" in "Test\nStudies\nProjects\nAdmin\nUAT\nPipelines\nBatches\nLabwhere Reception\nLab View\nLab search\nReport Fails\nBarcode\nProject\nStudy\nSample\nLabware\nAssetGroup\nRequest\nSupplier\nSubmission\nAll\nStudy 1 Edit\nEdit your study. Required fields are marked with .\nStudy owner name\nSelect an owner...\nProperties\nFaculty Sponsor\nFaculty Sponsor 1\nProgram\nGeneral\nNumber of gigabases per sample (minimum 0.15)\nPrelim ID\nPrelim ID\nReference genome\nReferenceGenome1\nTitleENA requirement\nTitle of the study as would be used in a publication.\nStudy TypeENA requirement\nNot specified\nStudy descriptionENA requirement\nSome study on something\nPlease choose one of the following 2 standard statements to be included with your data submissions (one or the other, depending on the study). If you use the second statement, replace [doi or ref] by a reference or doi for your publication:\n\nThis data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/\n\nOR\n\nThis data has been described in the following article [doi or ref] and its further analysis can be freely submitted for publication. For information on the proper use of data shared by the Wellcome Trust Sanger Institute (including information on acknowledgement), please see http://www.sanger.ac.uk/datasharing/\nIf applicable, include a brief description of any restrictions on data usage, e.g. 'For AIDS-related research only'\nAbstractENA requirement\nBriefly describes the goals, purpose, and scope of the Study. This need not be listed if it can be inherited from a referenced publication. For managed access studies, please bear in mind it’s this text in the Abstract section that will be publicly visible on the EGA website.\nStudy Visibility\nStudy VisibilityENA requirement\nHold\nPublic\nMake this ENA project public immediately.\nDo any of the samples in this study contain human DNA?\nDo any of the samples in this study contain human DNA?\nYes\nNo\nIf they do, you will be required to upload the relevant documents. This does not apply to samples that are going to have the Human DNA removed prior to analysis.\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nYes\nNo\nUsually only applicable to pathogen research when human DNA will not be sequenced and therefore does not require ethical approval.\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nYes\nNo\nAre all the samples to be used in this study commercially available, anonymised cell-lines or DNA/RNA from commercially available, anonymised cell-lines?\nDoes this study require the removal of X chromosome and autosome sequence?\nDoes this study require the removal of X chromosome and autosome sequence?\nYes\nNo\nApplicable for studies where only mtDNA and Y-chromosomal data will be submitted to EGA.\nDoes this study require y chromosome data to be separated from x and autosomal data before archival?\nApplicable for studies where Y-chromosome data will not be submitted to the EGA, or will be submitted separately from autosomal sequence.\nENA Project IDENA (see help)\nThe required PROJECT_ID accession is generated by the Genome Project database at NCBI and will be valid also at the other archival institutions. Enter 0 if the project id is unknown or not assigned.\nENA Study Accession Numbersee help\nData Release accession Number. Will be filled automatically during submission process. Provide ONLY if the project has already been submitted to EBI.\nStudy na

Edit a study when data release strategy is Not Applicable does not error when setting strategy to Open Failure/Error: expect(page).to have_content('Your study has been updated') expected to find text "Your study has been updated" in "Test\nStudies\nProjects\nAdmin\nUAT\nPipelines\nBatches\nLabwhere Reception\nLab View\nLab search\nReport Fails\nBarcode\nProject\nStudy\nSample\nLabware\nAssetGroup\nRequest\nSupplier\nSubmission\nAll\nStudy: Never Edit\nEdit your study. Required fields are marked with .\nStudy owner name\nSelect an owner...\nProperties\nFaculty Sponsor\nFaculty Sponsor 1\nProgram\nGeneral\nNumber of gigabases per sample (minimum 0.15)\nPrelim ID\nPrelim ID\nReference genome\nReferenceGenome1\nTitleENA requirement\nTitle of the study as would be used in a publication.\nStudy TypeENA requirement\nNot specified\nStudy descriptionENA requirement\nSome study on something\nPlease choose one of the following 2 standard statements to be included with your data submissions (one or the other, depending on the study). If you use the second statement, replace [doi or ref] by a reference or doi for your publication:\n\nThis data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/\n\nOR\n\nThis data has been described in the following article [doi or ref] and its further analysis can be freely submitted for publication. For information on the proper use of data shared by the Wellcome Trust Sanger Institute (including information on acknowledgement), please see http://www.sanger.ac.uk/datasharing/\nIf applicable, include a brief description of any restrictions on data usage, e.g. 'For AIDS-related research only'\nAbstractENA requirement\nBriefly describes the goals, purpose, and scope of the Study. This need not be listed if it can be inherited from a referenced publication. For managed access studies, please bear in mind it’s this text in the Abstract section that will be publicly visible on the EGA website.\nStudy Visibility\nStudy VisibilityENA requirement\nHold\nPublic\nMake this ENA project public immediately.\nDo any of the samples in this study contain human DNA?\nDo any of the samples in this study contain human DNA?\nYes\nNo\nIf they do, you will be required to upload the relevant documents. This does not apply to samples that are going to have the Human DNA removed prior to analysis.\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nYes\nNo\nUsually only applicable to pathogen research when human DNA will not be sequenced and therefore does not require ethical approval.\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nYes\nNo\nAre all the samples to be used in this study commercially available, anonymised cell-lines or DNA/RNA from commercially available, anonymised cell-lines?\nDoes this study require the removal of X chromosome and autosome sequence?\nDoes this study require the removal of X chromosome and autosome sequence?\nYes\nNo\nApplicable for studies where only mtDNA and Y-chromosomal data will be submitted to EGA.\nDoes this study require y chromosome data to be separated from x and autosomal data before archival?\nApplicable for studies where Y-chromosome data will not be submitted to the EGA, or will be submitted separately from autosomal sequence.\nENA Project IDENA (see help)\nThe required PROJECT_ID accession is generated by the Genome Project database at NCBI and will be valid also at the other archival institutions. Enter 0 if the project id is unknown or not assigned.\nENA Study Accession Numbersee help\nData Release accession Number. Will be filled automatically during submission pr

cherrypick for fluidigm pipeline - micro litre required volume is 13 Failure/Error: find_all(:checkbox).each { |checkbox| expect(checkbox).to be_checked } expected `#<Capybara::Node::Element tag="input" path="/HTML/BODY[1]/DIV[1]/SECTION[1]/SECTION[1]/DIV[1]/FORM[1]/TABLE[1]/TBODY[1]/TR[1]/TD[1]/INPUT[2]">.checked?` to be truthy, got false

Labwhere reception displays the correct labwhere error messages Failure/Error: expect(page).to have_content 'LabWhere User does not exist' expected to find text "LabWhere User does not exist" in "Test\nStudies\nProjects\nUAT\nPipelines\nBatches\nLabwhere Reception\nLab View\nLab search\nReport Fails\nBarcode\nProject\nStudy\nSample\nLabware\nAssetGroup\nRequest\nSupplier\nSubmission\nAll\nAsset barcodes can't be blank\nLabwhere Reception\nUser barcode or swipecard\nScan location barcode\nScan plate or tube\nHelp\nWellcome Sanger Institute\nA tool from LIMS and Informatics\nSequencescape 0.0.0 [test] snyk-upgrade-17ffa6e5a5b0a673e8850095173c5fb0@2c6d856\nLOCAL\nfv-az1567-73"

Labwhere reception user can scan plates into the reception Failure/Error: expect(find('.barcode_list')).to have_content plate.human_barcode expected to find text "SQPD-1" in ""

Study roles can be removed Failure/Error: super Capybara::ElementNotFound: Unable to find id "role_list"

Viewing request comments returns an error message Failure/Error: super Selenium::WebDriver::Error::StaleElementReferenceError: stale element reference: stale element not found (Session info: chrome-headless-shell=131.0.6778.69); For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#stale-element-reference-exception

Process completed with exit code 1.

The job was canceled because "_3_1" failed.

The operation was canceled.

Generate a bulk submission spreadsheet Generate a basic spreadsheet Failure/Error: super Capybara::ElementNotFound: Unable to find field "Fragment size required (from)" that is not disabled

Generate a bulk submission spreadsheet with a bait_library submission populates the primer panel column Failure/Error: super Capybara::ElementNotFound: Unable to find select box "Bait library" that is not disabled and Unable to find input box with datalist completion "Bait library" that is not disabled

Generate a bulk submission spreadsheet with a primer panel submission populates the primer panel column Failure/Error: super Capybara::ElementNotFound: Unable to find select box "Primer panel" that is not disabled and Unable to find input box with datalist completion "Primer panel" that is not disabled

Create a study create open study Failure/Error: expect(page).to have_content('Your study has been created') expected to find text "Your study has been created" in "Test\nStudies\nProjects\nAdmin\nUAT\nPipelines\nBatches\nLabwhere Reception\nLab View\nLab search\nReport Fails\nBarcode\nProject\nStudy\nSample\nLabware\nAssetGroup\nRequest\nSupplier\nSubmission\nAll\nStudy Create\nTo register a new study, complete the form below. Required fields are marked with .\nStudy name\nStudy owner name\nSelect an owner...\nProperties\nFaculty Sponsor\nJack Sponsor\nProgram\nProgram1\nNumber of gigabases per sample (minimum 0.15)\nPrelim ID\nPrelim ID\nReference genome\nTitleENA requirement\nTitle of the study as would be used in a publication.\nStudy TypeENA requirement\nStudy Type 1\nStudy descriptionENA requirement\nPlease choose one of the following 2 standard statements to be included with your data submissions (one or the other, depending on the study). If you use the second statement, replace [doi or ref] by a reference or doi for your publication:\n\nThis data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/\n\nOR\n\nThis data has been described in the following article [doi or ref] and its further analysis can be freely submitted for publication. For information on the proper use of data shared by the Wellcome Trust Sanger Institute (including information on acknowledgement), please see http://www.sanger.ac.uk/datasharing/\nIf applicable, include a brief description of any restrictions on data usage, e.g. 'For AIDS-related research only'\nAbstractENA requirement\nBriefly describes the goals, purpose, and scope of the Study. This need not be listed if it can be inherited from a referenced publication. For managed access studies, please bear in mind it’s this text in the Abstract section that will be publicly visible on the EGA website.\nStudy Visibility\nStudy VisibilityENA requirement\nHold\nPublic\nMake this ENA project public immediately.\nDo any of the samples in this study contain human DNA?\nDo any of the samples in this study contain human DNA?\nYes\nNo\nIf they do, you will be required to upload the relevant documents. This does not apply to samples that are going to have the Human DNA removed prior to analysis.\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nYes\nNo\nUsually only applicable to pathogen research when human DNA will not be sequenced and therefore does not require ethical approval.\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nYes\nNo\nAre all the samples to be used in this study commercially available, anonymised cell-lines or DNA/RNA from commercially available, anonymised cell-lines?\nDoes this study require the removal of X chromosome and autosome sequence?\nDoes this study require the removal of X chromosome and autosome sequence?\nYes\nNo\nApplicable for studies where only mtDNA and Y-chromosomal data will be submitted to EGA.\nDoes this study require y chromosome data to be separated from x and autosomal data before archival?\nApplicable for studies where Y-chromosome data will not be submitted to the EGA, or will be submitted separately from autosomal sequence.\nENA Project IDENA (see help)\nThe required PROJECT_ID accession is generated by the Genome Project database at NCBI and will be valid also at the other archival institutions. Enter 0 if the project id is unknown or not assigned.\nENA Study Accession Numbersee help\nData Release accession Number. Will be filled automatically during submission process. Provide ONLY if the project has already been submitted to EBI.\nStudy n

View study properties Multiple requests link to the summary Failure/Error: expect(page).to have_link('2', title: "#{library_tube.human_barcode} failed") expected to find link "2" but there were no matches

View study properties Filtering by asset type Failure/Error: super Capybara::ElementNotFound: Unable to find css "#summary"

View study properties Single requests link directly to the request Failure/Error: expect(page).to have_link('1', title: "#{library_tube.human_barcode} passed") expected to find link "1" but there were no matches

Batches controller reordering requests Failure/Error: expect(request_list.all('tr').first).to eq(third_request) expected: #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[1]/SECTION[1]/SECTION[1]/DIV[1]/DIV[3]/DIV[1]/TABLE[1]/TBODY[1]/TR[3]"> got: #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[1]/SECTION[1]/SECTION[1]/DIV[1]/DIV[3]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]"> (compared using ==) Diff: @@ -1 +1 @@ -#<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[1]/SECTION[1]/SECTION[1]/DIV[1]/DIV[3]/DIV[1]/TABLE[1]/TBODY[1]/TR[3]"> +#<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[1]/SECTION[1]/SECTION[1]/DIV[1]/DIV[3]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">

Manage a study Rename a study Failure/Error: expect(page).to have_content('Updated name') expected to find text "Updated name" in "Test\nStudies\nProjects\nAdmin\nUAT\nPipelines\nBatches\nLabwhere Reception\nLab View\nLab search\nReport Fails\nBarcode\nProject\nStudy\nSample\nLabware\nAssetGroup\nRequest\nSupplier\nSubmission\nAll\nManage Study Original name\nYou can update the approval status for a study here.\nStudy : Original name\nStudy 3232 · Created on November 23, 2024 05:35 · Active\nStudy state\nState\nPending\nActive\nInactive\nContacts\nView Study Contacts\nProperties\nStudy name\nRename the study\nFaculty Sponsor\nFaculty Sponsor 1\nProgram\nGeneral\nNumber of gigabases per sample (minimum 0.15)\nPrelim ID\nPrelim ID\nReference genome\nReferenceGenome1\nTitleENA requirement\nTitle of the study as would be used in a publication.\nStudy TypeENA requirement\nNot specified\nStudy descriptionENA requirement\nSome study on something\nPlease choose one of the following 2 standard statements to be included with your data submissions (one or the other, depending on the study). If you use the second statement, replace [doi or ref] by a reference or doi for your publication:\n\nThis data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/\n\nOR\n\nThis data has been described in the following article [doi or ref] and its further analysis can be freely submitted for publication. For information on the proper use of data shared by the Wellcome Trust Sanger Institute (including information on acknowledgement), please see http://www.sanger.ac.uk/datasharing/\nIf applicable, include a brief description of any restrictions on data usage, e.g. 'For AIDS-related research only'\nAbstractENA requirement\nBriefly describes the goals, purpose, and scope of the Study. This need not be listed if it can be inherited from a referenced publication. For managed access studies, please bear in mind it’s this text in the Abstract section that will be publicly visible on the EGA website.\nStudy Visibility\nStudy VisibilityENA requirement\nHold\nPublic\nMake this ENA project public immediately.\nDo any of the samples in this study contain human DNA?\nDo any of the samples in this study contain human DNA?\nYes\nNo\nIf they do, you will be required to upload the relevant documents. This does not apply to samples that are going to have the Human DNA removed prior to analysis.\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nDoes this study contain samples that are contaminated with human DNA which must be removed prior to analysis?\nYes\nNo\nUsually only applicable to pathogen research when human DNA will not be sequenced and therefore does not require ethical approval.\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nAre all the samples to be used in this study commercially available, unlinked anonymised cell-lines?\nYes\nNo\nAre all the samples to be used in this study commercially available, anonymised cell-lines or DNA/RNA from commercially available, anonymised cell-lines?\nDoes this study require the removal of X chromosome and autosome sequence?\nDoes this study require the removal of X chromosome and autosome sequence?\nYes\nNo\nApplicable for studies where only mtDNA and Y-chromosomal data will be submitted to EGA.\nDoes this study require y chromosome data to be separated from x and autosomal data before archival?\nApplicable for studies where Y-chromosome data will not be submitted to the EGA, or will be submitted separately from autosomal sequence.\nENA Project IDENA (see help)\nThe required PROJECT_ID accession is generated by the Genome Project database at NCBI and will be valid also at the other archival institutions. Enter 0 if the project id is unknown or not assigned.\nENA Study Accession Numbersee help\nData Release accessio

Process completed with exit code 1.

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/