[MGNLPER-21] Fetch and render 'item type', 'last editor' and 'last edited date' properties for JCR and REST searches Created: 02/May/18  Updated: 21/Aug/18  Resolved: 15/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:
Issue split
split to MGNLPER-43 Periscope data binding for REST Closed
Relates
relates to MGNLPER-46 Convert SearchResult#lastModified fro... Closed
relation
is related to MGNLPER-19 Introduce SearchResultSupplier via REST Closed
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)
Epic Link: Periscope back-end MVP
Sprint: Basel 152, Basel 153
Story Points: 5

 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.


Generated at Mon Feb 12 10:27:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.