Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue/so 3261 value set/mapping set import/export issues #279

Closed

Conversation

AAAlinaaa
Copy link
Contributor

No description provided.

Zoltan Molnar and others added 17 commits October 13, 2018 11:06
1. Ensure changes are correctly reported at the end of import
2. Remove trailing white spaces from the last column in csv import to
ensure ids are read correctly
3. Fix index out of bounds exception in SnomedCompositeImporter
4. Ensure Synonym service is available in SnomedConceptCreateRequest
5. Make sure new reference set appears in the refset view by creating
both inferred and stated is a relationships to appropriate refset parent
concept on import
Fixes security issues reported by GitHub security vulnerability check.
…on_against_invalid_version_id

SO-3219: Add validation against the version branch thats to be created
…y_script_sample_for_UK_reporting_purposes

SO-3264: Create groovy script sample for uk reporting purposes
…unning_validation

SO-3267: Error when running validation
…_dsv_content_header_issue

SO-3300: Fix simple type refset header issues
…mport_issues

SO-3262: Fix various refset import related issues
@AAAlinaaa AAAlinaaa closed this Nov 6, 2018
@cmark cmark deleted the issue/SO-3261-value_set/mapping_set_import/export_issues branch November 6, 2018 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants