-
Notifications
You must be signed in to change notification settings - Fork 535
6300/6396 additional dataset metadata via search api #6441
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
Merged
kcondon
merged 14 commits into
develop
from
6300-additional-dataset-metadata-via-search-api
Dec 11, 2019
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
41a97ee
Merge branch 'develop' into 6300-additional-dataset-metadata-via-sear…
sekmiller 3b91f16
Merge branch 'develop' into 6300-additional-dataset-metadata-via-sear…
sekmiller 387615b
Merge branch 'develop' into 6300-additional-dataset-metadata-via-sear…
sekmiller 3245eee
Merge branch 'develop' into 6300-additional-dataset-metadata-via-sear…
sekmiller 96b810d
#6300 Add more detail to dataset search results
sekmiller d5116ef
Merge branch 'develop' into 6300-additional-dataset-metadata-via-sear…
sekmiller ad3accf
#6300 add Version Numbers to Search API
sekmiller f5435c1
Merge branch 'develop' into 6300-additional-dataset-metadata-via-sear…
sekmiller b379994
#6300 Add unit tests for additional data provided
sekmiller 81838e6
Merge branch 'develop' into 6300-additional-dataset-metadata-via-sear…
sekmiller dba46e8
6300 remove reference to parameter
sekmiller a33bcdd
6300 Adding example of additional DS info
sekmiller 1278522
add release note about `query_entities` #6300 #6396
pdurbin 6851c28
add a use case to release note #6300 #6396
pdurbin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| ## Major Use Cases | ||
|
|
||
| Newly-supported use cases in this release include: | ||
|
|
||
| - Search API users will see additional fields in the JSON output #6300 #6396 | ||
|
|
||
| ## Notes for Tool Developers and Integrators | ||
|
|
||
| ### Search API | ||
|
|
||
| The boolean parameter `query_entities` has been removed from the Search API. | ||
|
|
||
| The former "true" behavior of "whether entities are queried via direct database calls (for developer use)" is now always true. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If "true" vs. "false" for
query_entitieshas no affect in this pull request, the documentation should be changed to reflect this. Here's a screenshot of how it's documented as of 4.18.1:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the parameter list (removed the reference to query_entities) and added an example with the new data items shown.