Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

Investigate why after upload (onerecord file) data we can see empty taxonomies. #1731

Open
8 tasks done
abaranowska1 opened this issue Feb 12, 2021 · 1 comment
Open
8 tasks done
Assignees
Labels
estimated Story Points: 1 Story points are a unit of measure for expressing an estimate of the overall effort

Comments

@abaranowska1
Copy link

abaranowska1 commented Feb 12, 2021

Description:
After upload data for example from the UWBA provider, we can see empty taxonomies on the SP view. It could be something wrong with the file, but plz investigate what is the reason for this issue.

Selection_999(087)

Dev Signoffs (remove items if not applicable to this issue)

  • Unit test added for the core business features at the minimum
  • Code review passed
  • CI passed successfully
  • CodeQL scan for vulnerabilities in code has passed
  • Docker images have been built and deployed to the dev server

QA Signoffs (remove items if not applicable to this issue)

  • Passes Acceptance Criteria
  • All bug reports fixed/merged/tested

Product Signoff (remove items if not applicable to this issue)

  • Approved for release
@kkaczmarczyk kkaczmarczyk added Story Points: 1 Story points are a unit of measure for expressing an estimate of the overall effort estimated labels Feb 17, 2021
awalkowiak added a commit that referenced this issue Feb 18, 2021
#1731: Delete old taxonomies on upload
@abaranowska1
Copy link
Author

abaranowska1 commented Feb 18, 2021

Tested with success
Verified cases:

  • After uploading for example UWBA one record file there is no empty taxonomies, all works fine after upload.

Selection_999(121)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
estimated Story Points: 1 Story points are a unit of measure for expressing an estimate of the overall effort
Projects
None yet
Development

No branches or pull requests

3 participants