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

Bulk Validation Error Normalization #1433

Open
Tracked by #1317
BirdMachine opened this issue Jun 28, 2024 · 1 comment
Open
Tracked by #1317

Bulk Validation Error Normalization #1433

BirdMachine opened this issue Jun 28, 2024 · 1 comment
Assignees
Labels
P Pitt dev team

Comments

@BirdMachine
Copy link
Contributor

BirdMachine commented Jun 28, 2024

Created from ISSUE #1417

--> Some (maybe all?) Errors from the initial Validation step can no longer be parsed properly, and a Normalization layer needs to be in place between the Service and rendered UI to somehow normalize them in some way. <---
[Bill]-- The results from the validation endpoint have already been normalized, so no need to add a normalization layer, just use the new normalized format. Coordinate with Gesina @ PSC about the format.

https://github.com/hubmapconsortium/ingest-api/tree/main/src/routes/validation
The Information here is not entirely accurate; the responses look very different when they contain errors. There are numerous kinds of errors that can return and all of them seem to be wrapped up differently. I don't know the different variations we can expect; Is there Documentation on smartAPI or the Hubmap API page (Note: Noticed the link to ingest API's github instead links to ingest UI's) that breaks down the different kind of errors we can expect?

@BirdMachine BirdMachine self-assigned this Jun 28, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Pitt HIVE Jun 28, 2024
@BirdMachine BirdMachine added the P Pitt dev team label Jun 28, 2024
@BirdMachine
Copy link
Contributor Author

sennetconsortium/ingest-api#173 Possibly helpful information here

@shirey shirey moved this from Backlog to Ready in Pitt HIVE Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P Pitt dev team
Projects
Status: Ready
Development

No branches or pull requests

1 participant