Documentation issueshttps://community.opengroup.org/osdu/documentation/-/issues2020-03-23T18:38:17Zhttps://community.opengroup.org/osdu/documentation/-/issues/57Search convenience queries2020-03-23T18:38:17ZFerris ArgyleSearch convenience queries## Status
- [ ] Proposed
- [ ] Trialing
- [ ] Under review
- [X] Approved
- [ ] Retired
## Context & Scope
R1 implemented map aggregate, zoom, and other convenience methods to address INT and SSIO requests.
## Decision
Deprecate plat...## Status
- [ ] Proposed
- [ ] Trialing
- [ ] Under review
- [X] Approved
- [ ] Retired
## Context & Scope
R1 implemented map aggregate, zoom, and other convenience methods to address INT and SSIO requests.
## Decision
Deprecate platform support for consumer-specific convenience methods other than map aggregates, eg. zoom
## Rationale
## Consequences
## When to revisit
---
# Tradeoff Analysis - Input to decision
## Alternatives and implications
* Deprecate platform support for consumer-specific convenience methods other than map aggregates, eg. zoom
* Retain these
## Decision criteria and tradeoffs
* Over-fitting against INT and SSIO
* Client convenience vs. service burden
## Decision timeline
R3Release 3ethiraj krishnamanaiduethiraj krishnamanaiduhttps://community.opengroup.org/osdu/documentation/-/issues/58Search - Map aggregate functionality (R3)2020-03-23T19:02:07ZFerris ArgyleSearch - Map aggregate functionality (R3)Redesign for generic case rather than putting in code
## Status
- [X] Proposed
- [ ] Trialing
- [ ] Under review
- [ ] Approved
- [ ] Retired
## Context & Scope
* Displays wells on map to ensure return result is as soon as possible; ...Redesign for generic case rather than putting in code
## Status
- [X] Proposed
- [ ] Trialing
- [ ] Under review
- [ ] Approved
- [ ] Retired
## Context & Scope
* Displays wells on map to ensure return result is as soon as possible; restricts # of fields and wells. Allows returning wells based on searches of child data.
* If query is geographic boundary and otherwise minimal, return all wells within that boundary: three fields (well name, unique id, …?)
* This functionality is a popular request, but implemented as special case in the data platform; not clear whether it can be generalized - Alan
## Decision
## Rationale
Supports ISVs required functionality in a way that's not over-fitted for INT and SSIO
## Consequences
## When to revisit
---
# Tradeoff Analysis - Input to decision
## Alternatives and implications
* Retain R2 injection of Elastic spatial filter
* Redesign for generic case rather than putting in code
## Decision criteria and tradeoffs
## Decision timelineRelease 3ethiraj 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 krishnamanaiduhttps://community.opengroup.org/osdu/documentation/-/issues/64Self-service deployability2020-03-23T16:03:50ZFerris ArgyleSelf-service deployabilityFigure out what self-service deployability looks like between R2 and R3
## Status
- [X] Proposed
- [ ] Trialing
- [ ] Under review
- [ ] Approved
- [ ] Retired
## Context & Scope
Infosys will help with what deployment at scale looks l...Figure out what self-service deployability looks like between R2 and R3
## Status
- [X] Proposed
- [ ] Trialing
- [ ] Under review
- [ ] Approved
- [ ] Retired
## Context & Scope
Infosys will help with what deployment at scale looks like, how much is OSDU vs. provider
## Decision
## Rationale
## Consequences
## When to revisit
---
# Tradeoff Analysis - Input to decision
## Alternatives and implications
## Decision criteria and tradeoffs
## Decision timelineRelease 3ethiraj krishnamanaiduethiraj krishnamanaiduhttps://community.opengroup.org/osdu/documentation/-/issues/88Show "permissions required" for all services in documentation in consistent m...2021-06-28T21:11:49ZDebasis ChatterjeeShow "permissions required" for all services in documentation in consistent mannerExample from Search service -
https://community.opengroup.org/osdu/platform/system/search-service/-/blob/master/docs/tutorial/SearchService.md
Scroll at the very end. It shows you that minimum permissions required is "users.osdu.viewer...Example from Search service -
https://community.opengroup.org/osdu/platform/system/search-service/-/blob/master/docs/tutorial/SearchService.md
Scroll at the very end. It shows you that minimum permissions required is "users.osdu.viewers".
Else, when someone gets 401 (Unauthorized) error from a service, he/she does not have much clue to figure out which role/group is missed from his/her user access credentials.
GET {{osduonaws_base_url}}/api/entitlements/v1/groupshttps://community.opengroup.org/osdu/documentation/-/issues/90Storage service documentation - Adding information on records insert limit [D...2021-10-26T10:09:35ZNaufal Mohamed NooriStorage service documentation - Adding information on records insert limit [Document Enhancement]Please see the following link:
https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/docs/tutorial/StorageService.md
We dont have any information related to the limit of record insertion using storage service. I ha...Please see the following link:
https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/docs/tutorial/StorageService.md
We dont have any information related to the limit of record insertion using storage service. I have tried from my end and seeing this message:
PUT: BASE_URL/api/storage/v2/records
```
{
"code": 400,
"reason": "Validation error.",
"message": "createOrUpdateRecords.records: Up to 500 records can be ingested at a time"
}
```
It will be beneficial if the documentation shows this limit.
cc: @debasischttps://community.opengroup.org/osdu/documentation/-/issues/85Storage service documentation - using the term "dataset-name" for explanation...2021-06-28T21:08:24ZDebasis ChatterjeeStorage service documentation - using the term "dataset-name" for explanation of "kind"Please see this link
https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/docs/tutorial/StorageService.md
Explains a few basic concepts like "id", "kind".
**kind**: *(mandatory)* Kind of data being ingested. Must...Please see this link
https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/docs/tutorial/StorageService.md
Explains a few basic concepts like "id", "kind".
**kind**: *(mandatory)* Kind of data being ingested. Must follow the naming convention: `{Data-Partition-Id}:{dataset-name}:{record-type}:{version}`.
The problem is using the term "**dataset**" in second component of "kind".
As you know, right now the term "dataset" is used in a different way (Data Definition such as for File.Generic, File.Collection and also new Services).
Can you plan to make suitable corrections?
Sample "kind" from json files in wiki of Data Loading team.
`"kind": "osdu:wks:work-product-component--WellLog:1.0.0",`
Thank you