[MGNLPER-43] Periscope data binding for REST Created: 06/Aug/18 Updated: 28/Aug/18 Resolved: 24/Aug/18 |
|
| Status: | Closed |
| Project: | Periscope |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Maxime Michel |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 back-end MVP | ||||||||
| Sprint: | Basel 153, Basel 154 | ||||||||
| Story Points: | 3 | ||||||||
| Description |
|
The goal is to add metadata in the form of new columns as seen on the Zeplin mockup. (Doing design work is not part of this ticket, though.) Getting the properties from JCR is straightforward enough, but the implementation should be generic enough to support searches over REST as well, in particular over our Confluence documentation. Magnolia documentation will not be listed by default (for instance to a Migros employee), but will serve as an example on how REST datasets can be integrated. |