[MGNLPER-127] Add filter to include/exclude external REST content sources Created: 10/Jan/20 Updated: 22/Sep/22 Resolved: 22/Sep/22 |
|
| Status: | Closed |
| Project: | Periscope |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Martin Drápela | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Periscope improvements | ||||||||
| Team: | |||||||||
| Description |
|
Find Bar search results can now display external content (introduced with However, just as we can restrict searches to specific workspaces, the same should be possible for external content provided via REST. This could be done through a new filter option (menu):
This will probably require a new property to define the source name (probably at the path/call level) for the filter in the definition of a REST client (line 4): baseUrl: https://api.pexels.com/v1/
restCalls:
searchTitleIssues:
FindBarFilterExtContentSourceName: Pexels
method: get
entityClass: com.fasterxml.jackson.databind.JsonNode
path: /search
Ideally, a new Find Bar option could be introduced to make it possible for the editors to completely bypass the JCR search supplier (or any custom supplier, if defined) and let them query only external REST-provided content if they need to.
|
| Comments |
| Comment by Mikaël Geljić [ 22/Sep/22 ] |
|
Needs validation (also the "type" filter seems to include all types of suppliers), meanwhile closing this as we will likely prioritize other search improvements. |