Documentation issueshttps://community.opengroup.org/osdu/documentation/-/issues2020-03-23T18:35:20Zhttps://community.opengroup.org/osdu/documentation/-/issues/54Ingestion reference data validation2020-03-23T18:35:20ZFerris ArgyleIngestion reference data validation## Status
- [ ] Proposed
- [ ] Trialing
- [x] Under review
- [ ] Approved
- [ ] Retired
### History
This was approved in [January OSDU R2 Decisions review](https://docs.google.com/presentation/d/13muxPb8gnZ8P_mwFvGu0K3rWaqoHD5z5uNx2-Lb...## Status
- [ ] Proposed
- [ ] Trialing
- [x] Under review
- [ ] Approved
- [ ] Retired
### History
This was approved in [January OSDU R2 Decisions review](https://docs.google.com/presentation/d/13muxPb8gnZ8P_mwFvGu0K3rWaqoHD5z5uNx2-LbmN2k/edit#slide=id.g7628e71997_0_358) and has since been revisited.
## Context & Scope
* Currently we are only validating manifests, not reference targets; we should validate that reference data to which an SRN refers exists, as well as other relationships
* How should this work? OpenDES model is to load and cleanup after based on batch scan checks; OSDU philosophy tends to be to only allow valid data in; if they’re doing as part of pre-processing, then capture as long-term backlog issue.
## Decision
## Rationale
## Consequences
Implementation Tasks:
* Gap Fit: Understand how validation is done today (ex, is it well formed JSON)
* Create an ADO story
* Dependency on Schema Service developed by SLB Pune Team
* Ethiraj to update on readiness
* Cross-Cloud Testing and Validation
## When to revisit
---
# Tradeoff Analysis - Input to decision
## Alternatives and implications
Propose postponing post-R2; this implies that bad data can be loaded.
## Decision criteria and tradeoffs
## Decision timelineRelease 2JoeJoehttps://community.opengroup.org/osdu/documentation/-/issues/48OpenDES record/resource id and group semantics (SRN)2020-03-23T18:36:07ZFerris ArgyleOpenDES record/resource id and group semantics (SRN)## Status
- [ ] Proposed
- [ ] Trialing
- [ ] Under review
- [X] Approved
- [ ] Retired
## Context & Scope
SRN has record/resource id and group encapsulated, whereas GUID doesn’t - Alan
## Decision
Add semantics to OpenDES for record...## Status
- [ ] Proposed
- [ ] Trialing
- [ ] Under review
- [X] Approved
- [ ] Retired
## Context & Scope
SRN has record/resource id and group encapsulated, whereas GUID doesn’t - Alan
## Decision
Add semantics to OpenDES for record/resource id and group
## Rationale
## Consequences
Implementation Tasks:
* Review and formalize the gap fit
* Add a service to map the SRN to the identifier to the ingestion workflow in OpenDES
* Add test
* Define new services to fill gap
## When to revisit
---
# Tradeoff Analysis - Input to decision
## Alternatives and implications
## Decision criteria and tradeoffs
## Decision timelineRelease 2ethiraj krishnamanaiduethiraj krishnamanaiduhttps://community.opengroup.org/osdu/documentation/-/issues/47Search - Return entities name2020-03-23T18:39:10ZFerris ArgyleSearch - Return entities name## Status
- [ ] Proposed
- [ ] Trialing
- [ ] Under review
- [X] Approved
- [ ] Retired
## Context & Scope
## Decision
Retain name for all return entities: these are there in R1, but weren’t in R0 in some cases
## Rationale
Support...## Status
- [ ] Proposed
- [ ] Trialing
- [ ] Under review
- [X] Approved
- [ ] Retired
## Context & Scope
## Decision
Retain name for all return entities: these are there in R1, but weren’t in R0 in some cases
## Rationale
Supports ISVs currently implemented functionality.
## Consequences
None.
Implementation Tasks:
* Test according to the definition of done (Write test cases)
* Add a user story to the project ADO
## When to revisit
---
# Tradeoff Analysis - Input to decision
## Alternatives and implications
## Decision criteria and tradeoffs
## Decision timelineRelease 2ethiraj krishnamanaiduethiraj krishnamanaidu