Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ensembl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • 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
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • 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
  • !526

Merged
Created Oct 09, 2020 by Marek Szuba@mks

Feature/lrg xrefs

  • Overview 1
  • Commits 2
  • Changes 2

Created by: magaliruffier

Requirements

  • Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion;
  • Review the contributing guidelines for this repository; remember in particular:
    • do not modify code without testing for regression
    • provide simple unit tests to test the changes
    • if you change the schema you must patch the test databases as well, see Updating the schema
    • the PR must not fail unit testing

Description

Change regex to capture all relevant LRG mappings.

Use case

Input data from HGNC can have multiple entries for 'Locus specific databases' while the current regex assumes it will only ever be LRG data. The regex update ensures we correctly capture the LRG ID when it is available and ignore any other data from that column.

Benefits

If applicable, describe the advantages the changes will have. All the relevant HGNC data for LRGs will be correctly parsed and stored in the xref database

Possible Drawbacks

If applicable, describe any possible undesirable consequence of the changes. NA

Testing

Have you added/modified unit tests to test the changes? The test data was updated to include a wider range of examples for the 'Locus specific databases' column

If so, do the tests pass/fail? Updating the test data without any code change results in the test case failing. With the proposed code change, the test case passes

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

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: feature/LRG_xrefs