Experience Tour

AR Experience Tour

Actors

User, Museum experience provider Description

This use case describes the active configuration or choice of an experience channel. The channel may cover the likely user trajectory, or it may also specify the route such as a museum tour. Pre-conditions User has access to both an AR device and a means of choosing / constructing channels based on both profile and options. Channel elements or brokers for doing this are accessible through a search option. User has already narrowed down their interest to a particular “museum” of channels Flow of events

 User visits a museum (real or virtual) and browses / searches for channels of interest that are “catalogued” as part of the museum User chooses options for configuration of a personal channel User embarks on a partly or wholly planned trajectory and channel experiences are fed to the user’s device in anticipation of their location and attention. The experiences may also include trajectory and attention guidance if the “history trail” is largely pre-planned. 

Post-conditions

User has had a “museum experience” personalized to their interests with or without a physical museum or physically constructed exhibits Comments  This is the use case of a visitor at a cultural heritage site being able to use discovery to configure a channel.

Christine's feedback on this is that AR is already a channel. See text of notes taken during May 16 meeting on this topic.

In Junaio, a channel is an experience. Christine recommends not calling this a channel for the purpose of the use case.

Josh, when you say channel what do you mean?

A channel is a pre-defined query.

Filtering for a large amount of content for specific type of content.

In the case of AR Experiences, the user’s immediate context (position and orientation, focus of attention) is one of the filters. The user may specify additional filters (e.g., show me all the content that pertains to a specific era/epoque,

Experience developers can design AR Experiences that follow a route or compose a narrative. The guest/visitor of the venue can look for the experience that interests them most. This is Discovery.

Based on the query, they can say “I’m interested in this, What is here?”. Then, based on results, the user chooses.

There may be content that is not threaded in a narrative and can be discovered. There is also content that is provided with a notion of sequence (spatial or temporal) designed by the experience creator (orchestrator/director).

We are asking where the line is drawn between a Discovery service that does the query and the Recommender “engine” that (based on pre-configured user preferences) ranks or proposes a subset of all that it has found. This is a useful distinction to make.

The user may have a different relationship with a Recommender engine than that which it has with the Discovery service. The recommendation service/recommender engine may be offered as an integrated service with discovery, or separately.

Two reasons to distinguish these components:

- configure them separately

- different business relationships (manage more/less user information to provide its service)