Decisions to make

Game or selfportrait
Game with a vision of a selfportrait
Selfportrait with game elements

Shop or mechanics
The shop is the main experience
The mechanics (network) the main experience

Important to note is even if the experience of the network is the heart beat of the project I still feel that the shop is an important part. That means I have to create more a relationship between the two.

The common thread
Should there be a common thread that connects to the shop?
Should be this be somthing like secret fragements that people will come across when browsing through the network?
Or
Should the the secret of the shop be in pieces? These pieces are then rewards a player gets from the puzzles he/she solves.

Network framework
Prezi style
Wiki style
Different HTML pages


To make a few examples to try out I need a small part of the network.




Next is to sort the fragments

Objects	Locked	Fragments
Fox Tail	Lost Tail	Fox
Raven Skull	Stealing Feathers	Raven
Locket	Time Capsule	Shiny Collection
-	-	Feather Collection

Objects get a profile page with a secret which can be in any form (video, picture, text)

Locked means that the player needs to do something (puzzle solving and such). So far I have 3 different kind of locked fragments. I already sort the locked fragments to the different puzzle solving. This way I have for each an example.

Puzzles	Request	Search
Time Capsule	Stealing Feathers	Lost Tail
Color code text	Communicate to fictional character	Photgraph with something missing (go to the location)
Text is about time travel, future?	See the stealing on security cam	A manual how to get a fox tail
Online, time short	email/chat, real letter, 3 days	as long as it takes to get to location, picture print/download

The rest of the fragments can be anything I whish. Blogs, small flash games, pictures, videos, text, anything really.

Update

Mapping Process
It has been a while since I looked at the mapping of the project process. So I had made a few sketches on paper how the map has evolved.
Image jet to be made

On the weekly meetings with my colleagues an interesting point came up. The map is the detail source of the process. Next to the map there is a document about the overview and general terms of the process. I have not thought about the timeline. So the suggestion came make a colour code for the map to be able to see the timeline. An important point to remember.


Presentation
For the presentation on 16 march we have to show what we have, want and why. It is also a good thing to show what is going to be made in the end. In my case it is going to be a “proof of concept”.

In preparation of the upcoming presentation I am going to make sketches of the scenario how I think the “player” will experience my project. With each image I will try to write down the rules at that point and why.

I think that are 3 parts a small explanation what the project is (self-portrait), the scenario and what exactly I am going to make at the end of the project.


Project
I am the stage to make some kind of prototype of the interactive network. Here kame up to use Wikispaces. I make my own wiki after all. If this is the way to go for the real product is yet to be seen.

Even though the project is called the Curiosity shop I always thought that this would not be the actual title of the shop or experience. Yesterday I had a thought that might be interesting. I really liked the title “The Keeper of Secrets” . In different old mythologies it is also connected to the Raven. The Raven was feared but it also was a sign of looking into your inner darkness revealing the fears and light the dark. Who knows, it was just a thought.

Network = Database

A great website showing interactive database, visualised.
Data visualization


Places to visite:

Fizz


We Feel Fine



I would think this is the technology to use for my database/network
Processing js