Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ensembl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ensembl-gh-mirror
  • ensembl
  • Merge requests
  • !466

RFAMParser: relax selection criteria on analysis.logic_name

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Marek Szuba requested to merge bugfix/rfamparser_analysis_logic_name into master Jan 08, 2020
  • Overview 0
  • Commits 1
  • Pipelines 1
  • Changes 1

Created by: mkszuba

Description

Update analysis.logic_name selection criteria in RFAMParser to account for ncRNA-related changes made during release 98.

Issue: ENSINT-402

Use case

Due to changes in the structure of the production database, since release 98 the value of analysis.logic_name corresponding to non-coding RNA can be either 'ncrna' (which is what we used before) or 'ncrna_species_name'. Change the SQL query used to map RFAM IDs to Ensembl stable IDs so that it can correctly handle species using the latter syntax, i.e. human, mouse and zebrafish.

Benefits

Will be able to load RFAM xrefs for human, mouse and zebrafish again.

Possible Drawbacks

None I can think of, we should probably rebase feature/xref_sprint against master before merging it in anyway.

Testing

Have you added/modified unit tests to test the changes?

No.

If so, do the tests pass/fail?

N/A

Have you run the entire test suite and no regression was detected?

No, there are no unit tests for RFAMParser. I have, however, tested the updated SQL query against homo_sapiens_core_97_38, homo_sapiens_core_98_38 and homo_sapiens_core_99_38 (the first two on the public MySQL server, the last one on staging); returns a non-empty set on all three.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: bugfix/rfamparser_analysis_logic_name