beckn / beckn/DSEP-Specification

Example jsons for Information discovery usecase

Open
#180 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
21
Forks
20
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
We have the following usecase for which examples need to be created in the examples/information_discovery folder

**Describe the solution you'd like**
Example JSONs need to be created in the examples/information_discovery folder

**Describe alternatives you've considered**
N/A

**Additional context**

We have the following usecases for which examples need to be created in the examples/information_discovery folder. The usecases and visualizations are as below:

### Use case : Discovery and Consumption of “Advisory Content” ( individual byte-sized content)

**Context**: Farmers or Field Level Extension Workers access “byte-sized content” (e.g. videos) for relevant Agri-advisory information on the Network

**Assumption**: Only free content will be fetched and accessed

**A sample illustration**: Moti is a farmer in Odisha. She is a wheat farmer and is struggling with Aphid infestation. She struggles to control it and is looking for effective solutions to address the disease and increase her crop yield. She is introduced to network through Krishi Vigyan Kendra. A farm extension worker Ramesh then uses a network-enabled bot which is plugged into the network. He uses the bot interface to search for remedies and prevention measures for the Aphid infestation. He receives multiple videos from different experts on best practices and fertilizers to address her concerns. He selects a 2-minute video from AgroExpert Solutions and clicks on the "watch it now" option. Moti watches the video and understands the right fertilizers she needs. After watching the video, Moti selects "Get Support" and connects with a farmer associate to address her further questions. After the conversation, Moti gives a rating for the video which she watched.

### Seeker Application: User Interaction Flow
**Personas / Functional Actors**
1. _User (Farm Extension Worker)_:
The individual looking to discover, order, update profile, cancel orders, and review products/services.
2. _System (Application)_:
The Seeker application facilitating all user interactions.
3. _Seller/Vendor_:
The entity providing the product/service listed on the application.

**Discovery of a Product / Service**
_User Actions_: Search or Browse
_Actor_: User
The user clicks on the chatbot and enters keywords related to the desired product/service.

**View Details:**
_Actor_: User
The user enters the keyword(in the chatbot) against the product/service to view detailed information, including descriptions, images, prices, and reviews.
_Actor_: System
Provides search results and brief information of BPP.
_Outcomes_:
The user finds relevant service providers easily.
The user gains comprehensive information to make an informed decision.

**Consumption of a Product / Service**
_Actor_: User
The user views the desired content (Video, PDF, text)
_Actor_: System
Plays the desired video
The system sends a message at the end of the video providing an option to connect to support
_Outcomes_:
The user can easily select videos and view them
The user completes the transaction through a smooth and secure process.

**Accessing Support**
_User Actions_:Access Support:
_Actor_: User
The user receives an option to connect to support in the chatbot at the end of the video.
The user enters the keyword corresponding to support.

**View Seller Contact Details**
_Actor_: User
The user views the seller’s contact details, including email and customer care contact information.

**Initiate Contact**
_Actor_: User
The user contacts the seller or customer care for support.
_Actor_: System
Displays the seller’s contact details and customer care information.
_Outcomes_:
The user accesses the necessary contact details for support.
The user can directly reach out for help with their queries or issues.

**Providing Rating and Submitting Feedback**
_Actor_: User
After receiving the service, the user is prompted to rate their experience on a scale (e.g., 1 to 5 stars).

**Write a Review**
_Actor_: User
The user writes a detailed review about their experience, including pros and cons.

**Submit Feedback**
_Actor_: User
The user submits the rating and review.
_Actor_: System
Collects and stores the rating and review.
Sends feedback to the appropriate channels (e.g., product team, customer service).
_Outcomes_:
The user shares their experience with other potential customers.
The business gains valuable insights to improve their products/services.
The user feels heard and valued by the business.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the existing files in examples/information_discovery and the repository's example JSON conventions. Create examples covering the discovery, consumption, support, seller-contact, rating, and feedback flows described in the issue, with the completed JSONs placed in that folder.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.