Final Demo Plan

Assignments

• Presenters: Enes Hamza Üstün, Akif Emre Biçen, Alper Vural, Efe Özavcı (ya da Beyza)
• Application Controller: Mustafa Öztürkmen
• Note Taker: Furkan Kaan Biçer, Beyza (ya da Efe)
• Timer: İbrahim İlter

1- Web: Exploration, Interaction & Reporting

User Profile

Emir Kaya Sociology Student at Istanbul University Age: 22 Emir is researching neighborhood memory and everyday urban life in Istanbul. He uses the desktop website to discover stories around different districts, especially stories related to migration, old street culture, and changing urban spaces. While exploring the app, he likes meaningful stories, comments on them, saves them for later, and reports inappropriate or irrelevant content when he encounters it.

Story Context

Emir finds a story about children playing in the streets of Fatih during the 1970s. He reads the story, likes it, writes a comment, and saves it. Later, while scrolling through the feed, he sees an unrelated and inappropriate story and reports it.

Assumptions / Pre-conditions

• Emir already has an account and is logged in.
• There are already several approved stories in the system.
• At least one story exists that can be reported for inappropriate or irrelevant content.
• Dektop web app is ready on the map/feed page.

Flow

1. He navigates to https://localhistorymap.app — the map page opens.
2. He navigates the map to the Balat area and clicks a story marker.
3. A popup appears — he clicks "View Timeline".
4. The timeline page opens, showing stories within 1 km of that pin, sorted chronologically.
5. He sets the date filter to 1970–1979 and applies it.
6. "Balat Sokaklarında Çocukluk" appears as the matching story.
7. He clicks the story card — the story detail page opens.
8. He reads the full story.
9. He clicks the Like button.
10. He scrolls to comments, writes a short comment, and submits.
11. He clicks the Save button.
12. He clicks the browser back button — returns to the timeline.
13. He navigates to the map via the site header.
14. He spots another marker in the Balat area — clicks it and sees "Random Advertisement Post".
15. He opens the story detail page.
16. He clicks the Report button, selects "Irrelevant or inappropriate content", and submits.
17. He sees a confirmation notification.

---

2- Web: Creating a Multi-Pin Route Story with Audio Transcription

User Profile

Mehmet Rıza Demir Retired Public Officer Age: 73 Mehmet Rıza has lived in Istanbul for most of his life. He recently lost his wife, Ayşe, and wants to preserve the memory of the places they used to visit together. Since he finds it easier to tell memories by speaking rather than typing, he decides to record his story using the application’s audio recording feature. The system automatically transcribes his voice into text, allowing him to review and publish the story as a route-based memory.

Story Context

Mehmet Rıza creates a multi-location story called “Ayşe ile Bir İstanbul Yürüyüşü.” Instead of typing the whole story manually, he records his voice while describing the places he and his wife used to visit together. The system automatically transcribes the recording into text. After reviewing the transcription, he adds multiple pins to represent the route and publishes the story.

Assumptions / Pre-conditions

• Mehmet Rıza already has an account and is logged in.
• He is using the web application.
• The application supports creating stories with multiple location pins.
• The application supports audio recording.
• The system can automatically transcribe recorded audio into editable text.
• Mehmet Rıza may review and edit the transcription before publishing.
• The demo audio/story content is prepared before the demo.

Flow

1. He opens the web application.
2. He clicks the "Create Story" or "Share a Story" button.
3. He enters the story title.
   • Example title: Ayşe ile Bir İstanbul Yürüyüşü
4. Instead of writing the story manually, he chooses the audio recording option.
5. He records himself telling the memory.
6. He stops the recording.
7. The system automatically transcribes the audio into text.
8. He reviews the generated transcription.
9. He makes a small correction if necessary.
10. He chooses the option to add multiple locations.
11. He places the first pin on the map.
    • Example: a museum they used to visit.
12. He places the second pin.
    • Example: a street or square where they used to meet.
13. He places the third pin.
    • Example: a seaside walking path.
14. He places the fourth pin.
    • Example: a scenic viewpoint or tea garden.
15. He checks that the pins are displayed as a route/journey.
16. He selects an approximate date or date range for the memory.
17. He uploads one or more photos.
18. He publishes the story.
19. He sees the success notification.
20. He opens the map and verifies that each pin appears on the map.
21. He clicks one of the route pins and sees that it opens the same route-based story.

---

3- Mobile: Discovering the Shared Route Story and Planning a Visit

User Profile

Can Arslan Architecture Student at Mimar Sinan Fine Arts University Age: 24 Can is interested in Istanbul’s historical neighborhoods, old buildings, and urban walking routes. He wants to plan a weekend trip with his friend, but instead of choosing a standard tourist route, he wants to discover a route with a personal memory behind it. While browsing the mobile app, he finds Mehmet Rıza’s route-based story and decides to use it as inspiration for his own walking plan.

Story Context

Can discovers Mehmet Rıza’s story, “Ayşe ile Bir İstanbul Yürüyüşü.” He notices that the story was originally recorded as audio and then transcribed by the system. He is affected by the story because it feels like a spoken memory preserved as a route. The story connects personal loss, urban culture, and walkable places in Istanbul. He saves the story, likes it, comments on it, and decides to follow the same route with his friend.

Assumptions / Pre-conditions

• Can already has an account and is logged in.
• Mehmet Rıza’s route story has already been published.
• The story is visible from the mobile application.
• The mobile app can display stories with multiple pins.
• The route pins open the same route-based story.

Flow

1. He opens the mobile app.
2. He searches for stories in Istanbul.
3. He filters or browses stories that include route/journey-style memories.
4. He sees “Ayşe ile Bir İstanbul Yürüyüşü” on the map or feed.
5. He opens the story preview.
6. He clicks "Read Story."
7. He reads the story and views the photos.
8. He checks the multiple pins on the map.
9. He realizes that the story forms a walkable cultural route.
10. He saves the story for later.
11. He likes the story.
12. He writes a short comment.
    • Example: This route feels very meaningful. I would like to visit these places with my friend.
13. He decides to use this route as a weekend plan.
14. He returns to the map and briefly shows the route pins again.

---

Demo Structure & Script

Overview

This demo presents three connected user scenarios:

• Mobile Exploration & Moderation: one user discovers a story, interacts with it, and reports inappropriate content.
• Web Contribution: another user creates a multi-pin route story by recording his voice and using automatic transcription.
• Mobile Route Discovery: a third user discovers that same route-based story and uses it to plan a real-life visit.

The demo is guided by a Main Host. The Main Host explains the platform, introduces each scenario, describes the demonstrated features, and manages transitions. The three user roles only roleplay their own user journeys.

---

Demo Timeline

Time	Speaker(s)	Section	Talking Points	Actions
0:00–0:25	Ana Sunucu	Introduction	Briefly introduce the platform as a cultural memory application. Mention that the demo will show three connected user journeys: exploration, contribution, and rediscovery.	Keep landing page or map page open.
0:25–0:40	Ana Sunucu	Scenario 1 Transition	Introduce the first scenario: a mobile user exploring stories, interacting with them, and reporting irrelevant content.	Switch to mobile app.
0:40–1:05	Kişi 1	Mobile – User Setup	Speak as Emir. Explain that he is researching old Istanbul neighborhoods and wants to find stories about everyday urban life.	Open mobile app as Emir.
1:05–1:35	Kişi 1	Mobile – Filtering & Search	Explain while using the app: he searches for Istanbul stories and filters them by date, location, or media type to find relevant memories.	Apply search/filter options.
1:35–2:00	Kişi 1	Mobile – Story Preview & Reading	Explain that he found a story about childhood in Fatih and wants to read more than the preview.	Tap a story marker/card, open preview, then tap "Read Story."
2:00–2:25	Kişi 1	Mobile – Interaction	Explain that the story is useful for his research, so he likes it, comments on it, and saves it for later.	Like the story, add comment, save story.
2:25–2:50	Kişi 1	Mobile – Reporting	Explain that while scrolling through the feed, he sees an irrelevant post and reports it because it does not fit the platform’s cultural memory purpose.	Return to feed, scroll, report unsuitable story, submit report.
2:50–3:05	Ana Sunucu	Scenario 2 Transition	Briefly state that the first scenario showed mobile discovery and interaction. Introduce the second scenario: a user contributing an oral memory as a multi-location route story.	Switch to web application.
3:05–3:30	Kişi 2	Web – User Setup	Speak as Mehmet Rıza. Explain that he wants to preserve the places he visited with his late wife, Ayşe, and that speaking is easier for him than typing.	Show web map/homepage while logged in.
3:30–3:50	Kişi 2	Web – Start Creating Story	Explain that this memory belongs to several places, not only one location, so he will create a route-based story.	Click "Create Story" / "Share a Story." Enter title.
3:50–4:25	Kişi 2	Web – Audio Recording	Explain that he will record the story instead of typing it manually. Speak the prepared short memory line.	Start recording, speak briefly or use prepared recording, stop recording.
4:25–4:55	Kişi 2	Web – Auto Transcription	Explain that the system turned his voice into text and that he can review or correct the transcription before publishing.	Show generated transcript. Make a small correction if needed.
4:55–5:35	Kişi 2	Web – Multiple Pins / Route	Explain that he is adding multiple pins because each stop represents a different part of his memory with Ayşe.	Add route pins.
5:35–5:55	Kişi 2	Web – Date & Media	Explain that he does not remember the exact date, so he selects an approximate date range and adds a photo to make the memory richer.	Select date/date range. Upload photo.
5:55–6:15	Kişi 2	Web – Publish & Verify	Explain that after publishing, each pin on the route should open the same story.	Publish, show success, return to map, click one route pin.
6:15–6:30	Ana Sunucu	Scenario 3 Transition	Briefly state that Mehmet Rıza’s memory is now visible to other users. Introduce the third scenario: another mobile user discovering this route and turning it into a plan.	Switch to mobile app.
6:30–6:55	Kişi 3	Mobile – User Setup	Speak as Can. Explain that he wants to plan a meaningful weekend walk with his friend instead of choosing a standard tourist route.	Open mobile app as Can.
6:55–7:20	Kişi 3	Mobile – Discover Route Story	Explain that he searches for Istanbul route stories and finds “Ayşe ile Bir İstanbul Yürüyüşü.”	Search/filter Istanbul stories. Open Mehmet Rıza’s story.
7:20–7:40	Kişi 3	Mobile – Route as Plan	Explain that the story feels personal but also gives him a walkable cultural route through the city.	Show story, photos, transcript, and multiple map pins.
7:40–7:50	Kişi 3	Mobile – Interaction	Explain that he saves the route, likes it, and comments because he wants to follow the same path with his friend.	Save, like, and comment on the story.
7:50–8:00	Ana Sunucu	Closing	Briefly summarize the demo: users can explore memories, contribute oral stories, create route-based narratives, interact with content, and support moderation.	Keep final route story visible on map.

Notes for Presentation Quality

• The Main Host should handle all technical explanations and transitions.
• Roleplay users should avoid explaining features directly.
• Roleplay users should only speak as their personas.
• Prepare the story text and audio beforehand.
• Keep the recorded audio short, around 15–20 seconds.
• Show the automatic transcription clearly, but do not spend too much time editing it.
• Spend the most time on the multiple-pin route feature because it is the visually strongest new feature.
• In the first mobile scenario, keep the report action short and clean.
• In the final mobile scenario, emphasize that Mehmet Rıza’s personal memory becomes a route that another user can follow.
• End the demo on the route map view because it visually summarizes the contribution and discovery flow.

---

Demo Data Strategy

User Roles

• Main Host

  • Not a system user.
  • Used only for opening, transitions between scenarios, and final closing.
  • Does not perform application actions.

• Kişi 1 — Explorer / Moderator User (Mobile): Emir Kaya

  • Pre-existing authenticated account.
  • Used to demonstrate:
    • Mobile browsing
    • Search and filtering
    • Story preview and full story reading
    • Like, comment, and save interactions
    • Reporting irrelevant or inappropriate content

• Kişi 2 — Contributor User (Web): Mehmet Rıza Demir

  • Pre-existing authenticated account.
  • Used to demonstrate:
    • Story creation from web
    • Audio recording
    • Automatic transcription
    • Transcription review/editing
    • Multi-pin route story creation
    • Approximate date range selection
    • Media upload
    • Publishing a story

• Kişi 3 — Route Explorer User (Mobile): Can Arslan

  • Pre-existing authenticated account.
  • Used to demonstrate:
    • Discovering a route-based story from mobile
    • Reading a story created by another user
    • Viewing multiple pins belonging to the same story
    • Saving, liking, and commenting on the route story
    • Using a memory route as inspiration for a real-life walking plan

---

Pre-populated Data

The system contains multiple historical and cultural memory stories located in Istanbul.

Stories are distributed across different:

• Neighborhoods
• Decades
• Media types
• Story types

Each story includes:

• Title
• Short preview text
• Full story content
• Historical date or approximate date range
• Location pin
• At least one image or media item

This allows immediate demonstration of:

• Map-based exploration
• Feed-based browsing
• Story preview vs full story view
• Search and filtering
• Content interaction
• Moderation/reporting flow

---

Scenario-Specific Data

Scenario 1 — Mobile Exploration, Interaction & Reporting

The system contains at least one meaningful story for Kişi 1 to discover.

Story for Interaction

• Title: Fatih Sokaklarında Çocukluk
• Location: Fatih, Istanbul
• Historical period: 1970s
• Content type: Text + image
• Purpose in demo:
  • Shows story discovery through mobile browsing/filtering.
  • Shows preview and full story reading.
  • Allows Kişi 1 to like, comment, and save the story.

Example Story Text

1970’lerde Fatih’te çocuk olmak, sokakların oyun alanı olduğu bir hayat demekti. Arabaların az geçtiği dar sokaklarda top oynar, akşam ezanı okununca evlere dağılırdık. Mahallede herkes birbirini tanırdı; kapılar açık, sohbetler sokakta olurdu.

Example Comment by Kişi 1

This story is very useful for understanding everyday neighborhood life in old Istanbul.

---

Reportable Content

The system also contains one intentionally irrelevant or inappropriate post for the reporting demonstration.

Reported Story

• Title: Random Advertisement Post
• Content: Unrelated promotional/spam-like content
• Purpose in demo:
  • Shows that users can report content that does not fit the platform’s cultural memory purpose.
  • Demonstrates community-supported moderation.

Example Report Reason

Irrelevant or inappropriate content

---

Demo-Created Data

Scenario 2 — Web Contribution with Audio Transcription and Multi-Pin Route

During the web demo, Kişi 2 creates a new story.

Created Story

• Author: Mehmet Rıza Demir
• Title: Ayşe ile Bir İstanbul Yürüyüşü
• Platform: Web
• Input method: Audio recording
• Generated content: Auto-transcribed text
• Story type: Multi-pin route story
• Historical date: Approximate date range
• Media: At least one uploaded photo

Audio Recording Content / Auto-Generated Transcript

Bu rota, eşim Ayşe ile yıllar boyunca yaptığımız küçük İstanbul yürüyüşlerinden kalan bir hatıra. İlk durağımız genelde sevdiğimiz bir müze olurdu. Sonra deniz kenarına iner, uzun uzun yürürdük. Bazen konuşmadan sadece manzaraya bakardık. Yürüyüşün sonunda da küçük bir çay bahçesinde otururduk. Bu yerlerin her biri bizim için ayrı bir anı taşıyor. Şimdi bu rotayı paylaşmak istiyorum; belki başka insanlar da bu yürüyüşü yaparken kendi anılarını biriktirir.

Route Pins

The story should contain multiple pins representing a route.

Example route stops:

1. Museum stop
2. Old meeting point
3. Seaside walking path
4. Scenic viewpoint / tea garden

Each pin belongs to the same story. Clicking any pin should open “Ayşe ile Bir İstanbul Yürüyüşü.”

Purpose in Demo

This created data demonstrates:

• Voice-based story creation
• Automatic transcription
• Reviewable/editable transcript
• Multi-location story structure
• Route-based memory preservation
• Approximate historical dating
• Media-enriched storytelling
• Publishing and immediate map visibility

---

Cross-Scenario Continuity

The story created by Kişi 2 is reused in Scenario 3.

Scenario 3 — Mobile Discovery of the Created Route Story

After Kişi 2 publishes “Ayşe ile Bir İstanbul Yürüyüşü,” the same story becomes visible to Kişi 3 in the mobile app.

Kişi 3 discovers the story through:

• Map browsing
• Feed browsing
• Search/filtering for Istanbul route stories

Kişi 3 then:

• Opens the story preview
• Reads the full story
• Views the auto-transcribed text
• Views the uploaded photo
• Checks the multiple route pins
• Saves the story
• Likes the story
• Comments on it
• Decides to follow the route with his friend

Example Comment by Kişi 3

This route feels very meaningful. I would like to visit these places with my friend.

---

Cross-Platform Consistency

The demo-created story is created on the web interface and later discovered on the mobile application.

This demonstrates:

• Shared backend between platforms
• Cross-platform data consistency
• Published stories becoming available across devices
• Multi-pin route rendering on both web and mobile
• Consistent story interaction features across platforms

---

Edge Case Data

The demo should include or simulate the following edge cases:

Approximate Date Range

Some stories do not have exact dates.

Used to demonstrate:

• Flexible historical dating
• Date range selection during story creation
• Filtering stories with approximate dates

Example:

1960s–1970s

---

Auto-Generated Transcript Review

The system should show that automatic transcription is reviewable.

Used to demonstrate:

• Audio-to-text conversion
• User control over generated text
• Small correction before publishing

Example:

• Recorded phrase is automatically transcribed.
• Kişi 2 briefly reviews the text.
• If necessary, he corrects one word or punctuation mark.

---

Multi-Pin Story Behavior

The route story should have more than one location pin.

Used to demonstrate:

• One story connected to several locations
• Route/journey-based memory structure
• Clicking different pins opens the same story

---

Irrelevant or Inappropriate Content

The feed should contain one reportable post.

Used to demonstrate:

• User reporting
• Community-supported moderation
• Content quality control

Example:

Random Advertisement Post

---

Data Preparation Checklist

Before the demo, make sure that:

• Emir Kaya’s mobile account exists and is logged in.
• Mehmet Rıza Demir’s web account exists and is logged in.
• Can Arslan’s mobile account exists and is logged in.
• The story “Fatih Sokaklarında Çocukluk” exists in the system.
• The reportable story “Random Advertisement Post” exists in the feed.
• The audio recording feature works or a prepared recording is available.
• Automatic transcription output can be displayed.
• At least one image is ready for Mehmet Rıza’s route story.
• The map supports adding multiple pins to one story.
• The story created on web becomes visible on mobile.
• The final route story can be opened from each route pin.