Discovery app
The new content curation system that leverages OHC Search.
Dee Beck, Peter LaQuerre, Susan Snipes
Information Development�Information Architecture and Design
Discussion Points
A little context
The Discovery team
Dee Beck, Information Architect
Susan Snipes, UX Manager
Mark Lindros, Enterprise Architecture
Susan Koehler, Product Manager
Peter LaQuerre, Project Owner
Teresa Gelerter, Project Manager
Demo�Customer-facing Discovery Pages
With fresh Redwood styling, Discovery pages take advantage of powerful Redwood components like Smart Filters & Search.
Susan Snipes
Senior Manager
UX Design and Strategy
Customer-facing Discovery pages
Examples
Demo�Authoring with the Discovery app
Discovery leverages OHC Search to automate and simplify the authoring workflow.
Susan Snipes
Senior Manager
UX Design and Strategy
Authoring with the Discovery app
Example
Advantages of Discovery
How Discovery delights our customers and makes your job easier.
Discover
Users can easily find content on the site
•
Users encounter new content they didn’t know existed.
Style
Redwood templates�bring consistency and engaging page designs.
•
Redwood components take the �customer experience �to the next level.
Search
OHC Search �powers Discovery and frees you from �tedious data entry.
•
Unifies customers �search experience �within Discovery pages.
Simple
By leveraging search, �over 80% of �Discovery pages �are built automatically.
•
With plug-and-play components �you can quickly choose the right presentation for your product.
SEO
Gives you time to focus on your content and make it easier to find.
Differences Between Current Interface Pages and Discovery Pages
Metadata
Metadata lets you to take full advantage of the filtering and search features in Discovery.
Adding metadata to your content makes it more discoverable.
Metadata improves search results across the board: OHC, search integrations within Oracle, and other places that use metadata, such as OHC Learn and Architecture Center.
Consistent, yet flexible
Choose from a common, standard set of product page components.
Each page component presents users with specific asset types or role-based content.
Some components are automatically populated based on content metadata; others are manually curated, so you can still customize specific components for your product.
How metadata is used in Discovery
Most of the metadata is standard metadata you use now; for example:
Some metadata will require updating your content when it is supported:
Other metadata is specific to content types:
Before and After�A Comparison of Interface & Discovery Pages
See how the Analytics Cloud Interface page content�fits into a Discovery page.
Dee Beck
Senior Information Architect�Information Architecture and Design
Interface pages
Before
<PLACEHOLDER FOR COMPARISON SCREEN SHOT>
Discovery pages
After
What can I do now to prepare for Discovery?
Ask the following questions:
Answers to common questions about the Discovery App
When can I move to Discovery?
Do I have to move to Discovery?
Why can’t I keep using the v2 or v3 app?
What tools are available to help me get there?
What if I’m not using self-publishing to generate my HTML?
Discovery Roadmap
M1
Create Product Welcome Pages with Initial Capabilities
M2
Create Landing Welcome Pages and Additional Components
M3
Publish via Jarvis��
M4
Integrate with OHC Search��
M5
MVP with �Select Products��
Personalization Roadmap
M1 �Basic product �operations
2021Q2-Q3
Log in and account creation prompts
Add and remove products to profile configuration
Use product data to influence search results
Personalized products on OHC home page
M2 �Recent activities��
Recently viewed content
Recent searches
M3 �Favorites��
All basic Favorites features
Allow user to set or override default language in profile
Default to profile-driven search filters
M4 �Advanced �product �operations
Most features dependent on Discovery
What's new �(per product)
What's popular� (at variety of levels)
Section state persistence on product Discovery pages
Add products to profile through �OHC UI
See visual indicator of tracked products
M5 �Role support��
Add role support to profile
Add role to product mapping support
Use role data to influence search results
M6 �Recommendations �and �preferences
Prompt user if content is available in their preferred language
User-driven organization in Favorites
Personalized recommendations on suite, product, etc. pages
Related content recommendations
M7 �User activities �and access�
Prompt user to add products to profile based on activity
Prompt user to add roles to profile based on activity
Mark new items as "seen"
Restricted access for certain content
Thank you