LPX User Stories

DPP LPX has been developed to facilitate the needs of two predominant live event user types: Publishers and Consumer.

The focus for producers is around the publication of live feeds. Consumers can subscribe to and retrieve feeds published by producers.

Examples of users who DPP LPX is designed to help include:

• A creator, who wishes to register their events as available for distribution. The creator does not need to retain any data beyond that used to identify the event(s) they have registered.

  • Remote bureau
  • ENG team
  • Smaller publisher
    
    

• A provider, who wishes to offer a schedule of events available to customers, and can also accept events from creators. The provider must somehow retain or expose a database of events.

  • Large news corp
  • Aggregation service
  • Distribution provider
    
    

• A customer, who wishes to retrieve schedules of future events that may be of interest, in order to elect to receive (“subscribe”) to one or more of them. The customer does not need to retain any data beyond that used to identify the event(s) they wish to consume.

  • News broadcaster
  • Aggregation service

LPX User Stories

The following is a set of example user stories that have been identified for DPP LPX. This is not a finite list and will be expanded in future to support additional use cases:

Event	Publisher	Consumer
Schedule/create live event	As a provider of a live content, I want to schedule an event so that consumers can see it will be available to them	As a consumer of live content, I want to see what events are available from a provider so that I can plan / produce/ broadcast output to users
View live event	As a producer, I want my live content to be searchable by consumers	As a customer, I want to search, view and subscribe to live events so that I can use the provider’s content.
Update event status	As a producer of a live event I need to update the status and details of the event as it progresses so that consumers are aware	As a consumer of a live event I need to know its status so that I can schedule/broadcast/record/stop publishing it/stop planning for it, accordingly in my workflow and output.
View event metadata	As a producer, I want to provide accurate metadata for an event	As a consumer of a live event I need accurate metadata for it, so that I can plan my output and ensure it is correct for my audience
Update event metadata	As a producer, I want to change the metadata I provide for an event so that it remains accurate throughout the event lifecycle	As a consumer I need to ensure metadata remains accurate for my audience and for planning purposes