[
https://jira.nuxeo.com/browse/NXP-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Jalon updated NXP-7094:
--------------------------------
Description:
*Technical Story for Timeline with tweets from users I'm connected with :*
* I call UserAffinityService that associate my account with the "usernameA"
with predicate "follow_tweet"
** this create a relation unidirectional between me and "usernameA"
* A a dispatcher instance implements an interface that specifies a method that :
** takes an event
** return a list of timeline ids
* I create a specific dispatcher instance for my use case. Let's call it
"Tweet_Follower_dispatcher".
** if the document is a tweet
** I execute a query to get all user connected to the author with the predicate
tweet_follower (from the userAffinityService)
** for each user returned this method returns "${username}_tweet_user" timeline
id. We working now with convention
* For each id returned the dispatcher service call the Activity Persistence
service to store the event into the given "username_tweet_follower" timelines.
*Technical Story for Timeline with activity from users I'm connected with :*
* I call UserAffinityService that associate my account with the "usernameA"
with predicate "friend"
** this create a relation unidirectional between me and "usernameA" (the
corollary
* I create a specific dispatcher instance for my use case. Let's call it
"Activity_Follower_dispatcher".
** I execute a query to get all user connected to the author with the predicate
friends, colleague, ... (from the userAffinityService)
** for each "username" returned this method returns "${username}_activity_user"
timeline id.
* For each id returned the dispatcher service call the Activity Persistence
service to store the event into the given "username_activity_follower"
timelines.
*Technical Story for Timeline with activity from a specific social workspace
called "SocialWorkspaceA" :*
* I create a specific dispatcher instance for my use case. Let's call it
"Activity_Follower_dispatcher_for_social_workspace".
** If the event is a document centric event and if the document is a child of a
social workspace (with the facet "social_workspace"
** the method return the timeline id
"${SocialWorkspaceAID}_activity_social_workspace"
*Technical Story for Timeline with activity from users members of a specific
social workspace called "SocialWorkspaceA" :*
* I create a specific dispatcher instance for my use case. Let's call it
"Activity_Follower_dispatcher_for_social_workspace_member".
** I get all social workspace the author belongs. For social workspace I return
"${socialworkspaceid}_activity_social_workspace_members" timeline id
** Membership of a social workspace must be resolved by a relation between the
user and the social workspace.
Member group and Administration group for a social workspace should be
virtual groups
*I would like to fiter some events type, for instance I don't want into the
time line all the modification events if one of my friends save all the time
with WSS:*
* the dispatcher "Activity_Follower_dispatcher" can look into the user
preferences events that must be filtered ?
was:
*Technical Story for Timeline with tweets from users I'm connected with :*
- I call UserAffinityService that associate my account with the "usernameA"
with predicate "follow_tweet"
- this create a relation unidirectional between me and "usernameA"
- A a dispatcher instance implements an interface that specifies a method that :
- takes an event
- return a list of timeline ids
- I create a specific dispatcher instance for my use case. Let's call it
"Tweet_Follower_dispatcher".
- if the document is a tweet
- I execute a query to get all user connected to the author with the
predicate tweet_follower (from the userAffinityService)
- for each user returned this method returns "${username}_tweet_user"
timeline id. We working now with convention
- For each id returned the dispatcher service call the Activity Persistence
service to store the event into the given "username_tweet_follower" timelines.
*Technical Story for Timeline with activity from users I'm connected with :*
- I call UserAffinityService that associate my account with the "usernameA"
with predicate "friend"
- this create a relation unidirectional between me and "usernameA" (the
corollary
- I create a specific dispatcher instance for my use case. Let's call it
"Activity_Follower_dispatcher".
- I execute a query to get all user connected to the author with the
predicate friends, colleague, ... (from the userAffinityService)
- for each "username" returned this method returns
"${username}_activity_user" timeline id.
- For each id returned the dispatcher service call the Activity Persistence
service to store the event into the given "username_activity_follower"
timelines.
*Technical Story for Timeline with activity from a specific social workspace
called "SocialWorkspaceA" :*
- I create a specific dispatcher instance for my use case. Let's call it
"Activity_Follower_dispatcher_for_social_workspace".
- If the event is a document centric event and if the document is a child of
a social workspace (with the facet "social_workspace"
- the method return the timeline id
"${SocialWorkspaceAID}_activity_social_workspace"
*Technical Story for Timeline with activity from users members of a specific
social workspace called "SocialWorkspaceA" :*
- I create a specific dispatcher instance for my use case. Let's call it
"Activity_Follower_dispatcher_for_social_workspace_member".
- I get all social workspace the author belongs. For social workspace I
return "${socialworkspaceid}_activity_social_workspace_members" timeline id
- Membership of a social workspace must be resolved by a relation between
the user and the social workspace.
Member group and Administration group for a social workspace should be
virtual groups
*I would like to fiter some events type, for instance I don't want into the
time line all the modification events if one of my friends save all the time
with WSS:*
- the dispatcher "Activity_Follower_dispatcher" can look into the user
preferences events that must be filtered ?
> Define stories around timeline feature
> --------------------------------------
>
> Key: NXP-7094
> URL: https://jira.nuxeo.com/browse/NXP-7094
> Project: Nuxeo Enterprise Platform
> Issue Type: User story
> Reporter: Benjamin Jalon
> Assignee: Benjamin Jalon
> Labels: timeline_work
> Fix For: 5.4.3
>
>
> *Technical Story for Timeline with tweets from users I'm connected with :*
> * I call UserAffinityService that associate my account with the "usernameA"
> with predicate "follow_tweet"
> ** this create a relation unidirectional between me and "usernameA"
> * A a dispatcher instance implements an interface that specifies a method
> that :
> ** takes an event
> ** return a list of timeline ids
> * I create a specific dispatcher instance for my use case. Let's call it
> "Tweet_Follower_dispatcher".
> ** if the document is a tweet
> ** I execute a query to get all user connected to the author with the
> predicate tweet_follower (from the userAffinityService)
> ** for each user returned this method returns "${username}_tweet_user"
> timeline id. We working now with convention
> * For each id returned the dispatcher service call the Activity Persistence
> service to store the event into the given "username_tweet_follower" timelines.
> *Technical Story for Timeline with activity from users I'm connected with :*
> * I call UserAffinityService that associate my account with the "usernameA"
> with predicate "friend"
> ** this create a relation unidirectional between me and "usernameA" (the
> corollary
> * I create a specific dispatcher instance for my use case. Let's call it
> "Activity_Follower_dispatcher".
> ** I execute a query to get all user connected to the author with the
> predicate friends, colleague, ... (from the userAffinityService)
> ** for each "username" returned this method returns
> "${username}_activity_user" timeline id.
> * For each id returned the dispatcher service call the Activity Persistence
> service to store the event into the given "username_activity_follower"
> timelines.
> *Technical Story for Timeline with activity from a specific social workspace
> called "SocialWorkspaceA" :*
> * I create a specific dispatcher instance for my use case. Let's call it
> "Activity_Follower_dispatcher_for_social_workspace".
> ** If the event is a document centric event and if the document is a child of
> a social workspace (with the facet "social_workspace"
> ** the method return the timeline id
> "${SocialWorkspaceAID}_activity_social_workspace"
> *Technical Story for Timeline with activity from users members of a specific
> social workspace called "SocialWorkspaceA" :*
> * I create a specific dispatcher instance for my use case. Let's call it
> "Activity_Follower_dispatcher_for_social_workspace_member".
> ** I get all social workspace the author belongs. For social workspace I
> return "${socialworkspaceid}_activity_social_workspace_members" timeline id
> ** Membership of a social workspace must be resolved by a relation between
> the user and the social workspace.
> Member group and Administration group for a social workspace should be
> virtual groups
> *I would like to fiter some events type, for instance I don't want into the
> time line all the modification events if one of my friends save all the time
> with WSS:*
> * the dispatcher "Activity_Follower_dispatcher" can look into the user
> preferences events that must be filtered ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
