Proposal

Here is the link to the proposal:

Proposal

Thanks,

Nick

Votes for team leader

Just to make sure everyone is happy about who leads the team I suggest we have a vote! You can vote for yourself or someone else!

Please can everyone vote before 6pm tonight if possible.

Cheers Steve

For Steve/Pete

Heya, sorry for delay. Had a major busy day yesterday with work and the small matter of my sister hitting 22 yrs old

Below is my input for the proposal, any problems, let me know.

==========

My Role:

Mike will take on the task of visual design and presentation of the Curatos system. This means all assets, including even this proposal document, will go through Mike to be married in with the design of the system. This will create a strong aesthetic identity for the project and further help to build user familiarity and give us set and consistent ways to “sell” the system to its intended audience. Mike will also be trying to act as a hub for the team, by facilitating regular meetings when needed and driving the project on to the next stage(s) when the time arrives. Whilst this responsibility belongs to everyone within the team, it will benefit us to have someone appointed to help organise and push when under pressure.

Curatos Design Considerations:

When broken down, Curatos is essentially a content management system. Dressed up appropriately and with the right options, we want Curatos to become a highly usable and worthwhile tool for the organisation, dissemination and delivery of digital “media” to an audience, whether in a public gallery, or even student webspace. Included with this document are examples of how the Curatos feature set might be laid out. Whilst not final by any means, they do illustrate how this system can potentially operate, and the visual design of Curatos will be one that allows a user straight forward and easy access to all the features we include. Comparisons between other CMS must be made and further research done as to how products such as WordPress allow their users to navigate. Differences and similarities must also be drawn so as to better allow us as a team to carve out the exact reasoning as to why Curatos is not “just another CMS” and something new, fresh and never-before-seen.

The feature-set design, something for the whole team to consider, will effect the aesthetics of the system fundamentally and therefore must be considered first. Once done, then we will have a framework to lay a visual design on top of. At this proposal stage the team is currently thrashing out the finer details of what features we want to build and how they will be laid out in context with each other and as stated, imagery as been included to highlight current thinking (subject to change as always).

Specific design considerations for the time being are that of an identifiable typeface to use as the spearhead of the projects “branding”, and one that is accompanied by a simple, yet easily understandable ident or “logo”. These are currently works in progress and as such at this proposal stage are still in the early development stages.

==========

Ok thats it I think, if Ive missed anything out let me know.

Thanks

//Mike

Curatos User Flow Possibility

Hey again all. As a way to address the comments left on the previous post I have put together a basic flow diagram as to how I imagined a user might progress through the system from logging in to saving and previewing a collection. Hopefully this was let people see a bit more clearly how it might work. The previous post was more of a “site map” I suppose, so hopefully this helps. Let me know.

//Mike

Curatos Interface/Functionality Map (Basic)

Hey all

As requested a mapped out ideal scenario for Curatos. Please pick it to death so we can get it right.

Response to Steve and Mike, Started Flash movie

In response to Steve:

I forgot to mention in my post about the meeting on the 16/11/07 that there is still scope to create your own content.

For example, there will be boxes to search for images from Flickr, videos from YouTubes and a box to select Curatos content. However, I assume that searching by ‘tags’ won’t work for our own content since there won’t be enough of it so perhaps if someone wants to search our own content then a sub-menu will appear where they can browse through images, videos and sound.

Also, apart from searching for content, there will be an ‘upload’ facility so people can upload there own content. This way they are not constrained to either web content or our content. However, this may lead to problems if someone uploads something that is ‘not acceptable’. How will we prevent/monitor this? Perhaps if someone uploads own content, an email gets sent to an administrator for them to approve it before it appears.

If we don’t use Flickr and YouTube then the outcomes of the art works created will be restricted since there will not be a vast deposit of resources to draw on so we need to find a balance. How much content can you envisage making?

————–

In response to Mike:

From what I understand you were thinking the same as Chris. We will develop an API but if we just made the API available then like Pete said in the last meeting how may curators will have the technical ability to implement it?

The way I understand it now is that yes we will be doing two things, one, an available API for people with technical savvy but two, a web based CMS type system where people can enter tags, search Flickr, YouTube, our own content, select the pieces they like, type some blurb, click a button and then there art work is created.

Therefore, when we demonstrate our API in public places, we have some pieces WE created to show-off its capabilities but also a database of OTHER works to draw upon so at the click of a button we can demonstrate works that a community has created using Curatos.

————–

Flash Movie:

I have started the Flash movie and have a demonstration to show at the meeting tomorrow. The demo loads 5 images that at the moment I have pre-defined. These images have a random opacity and x and y coordinates (position on stage) and move every 5 seconds to another random location and there opacity changes again. If a person has the mouse cursor over an image then it becomes fully visible and does not move until the user takes there mouse away from it. Also, when the images move, they ease in too position so they accelerate fast and then slow to halt.

————–

Thanks,

Nick

Mike’s Proposal Thoughts

Hey all

Am sat down in a cafe with a good amount of time to give to the proposal. Before I launch in to it though I will tell you what I thought was the outcome of the previous meet where I was present.

Basically it was my understanding that we would be doing 2 things. The first being to develop an API that would be designed and targeted towards curators and artists so they they might be able to organise and manage a collection of work in an online space specifically with the focus being on the eventual display of the work for public consumption. Collections could also be enhanced and supplemented with data pulled from various other online sources as described by the use, or collections could be created only using data-mining techniques. Collections would be parsed for output using specially designed flash files

Secondly, we would use our own API to demonstrate how such a system could function in practice, either via using the video screens in the DC Shopping Center and/or in the Planetarium and/or via Xiao’s “Faces” videowall idea (which I am really starting to think could be super cool).

So in short thats what I thought was the plan of action.

I noticed below that there seemed to be some further confusion as to the outcome of the project in terms of what we would essentially be handing in at the end. I was basically under the impression we would be creating a piece of web-based software (the API) and using it. So creating a tool and demonstrating that tool as proof of concept. This gives us all the scope to work to our own strengths and also gives those more interested in “content” to get their hands dirty being creative. If successful would also be something that could gain quite a bit of recognition depending on how savvy we are with marketing it.

The Proposal

As stated below, Steve & Pete are going to be collecting together the separate parts of the proposal ready for hand-in (correct me if I am wrong) and it has been asked that I consider the branding and marketing elements of the project re: my background in Graphic Design. I will go over that shortly but to begin with I thought it might be helpful to lay down how I think the proposal should be setup. Essentially what we are doing here is writing a specific briefing for ourselves, something I am used to dealing with from my BA years ans also as a freelancer. This brief also should be clear, concise and be understandable to any random outsider (not just m-dat staff).

The way I would envisage it being structured is as follows:

1: The Pitch

Here we lay out the idea in clean and plain English, the concept we aim to realise with this Unit.

2: Why

So how does this idea conform to the requirements of the Unit itself? How is the idea relevent to the topic of Curation.

3: Roles

Who is doing what and why that person has been selected to perform that task. This will help us solidify a good understanding of our group dynamic so we can better understand where we are all coming from.

4: Final Comments, End-product, Summary

Anything that does not fit in 1-3, a declaration as to what we aim to hand in, separate from the initial pitch, and a summary of any key points.

Branding Curatos

With this type of project, visual design and functionality obviously go hand-in-hand so the Branding for the project should be mainly doing two things.

1: Providing a simple and intuitive user interface that accurately and easily lays out the tools we create for the user to be able to effortlessly enjoy the process of using the API.

2: Point 1 combined with a visual aesthetic that is simple, and also one that understands its audience. The audience in this case initally being the Curator or Artist(s) who will use the API. No assumptions will be made as to the level of computer literacy of the user so traditional web-based semantics will NOT be taken as a given, but rather everything will be carefully placed to make 100% sure even someone who has only just learned how to login to hotmail can feel secure about the buttons they press. In short, “Simplicity, Speed, Accessibility”.

Brand identity can be developed relatively easily (Think Facebook…very very very simple visual style) but must be consistent throughout all materials, hence the API, Community webpage, Video stings, flash files and all documentation must conform together under one umbrella brand. The easiest way to achieve this without needing 5 degrees and a $50000 budget (think Guardian newspaper, which is the most heavily designed piece of print around at the moment..designed by Pentagram in London) is to use a distinctive type face and a single defining colour (defining the colour of curation might be a little tough though ). Unique iconography or a non-type ident will also work well and I will bring some example ideas with me on Wednesday.

Beyond this the design will depend upon what we let the user do i.e. the functionality. So if we can decided upon this aspect THIS WEEK interms of data flow and organisation then I will have a frame to hang the brand on more comfortably.

Thats it for now..will add more later on.

Take it easy!

Mike T

Meeting 16/11/07

1. We seem to be envisaging different things as the end product

Chris - under the impression that we would effectively be supplying an API for them to integrate.

I (Nick) – thought we would be enabling them to select photos and videos from Flickr and YouTube respectively and then we pull these into a Flash movie.

Pete – said that if we just supplied them with an API then a lot of people himself included wouldn’t know what to do to make there piece.

So, we decided we would do both.

In terms of our Flash movie pulling in peoples content from the Web, the way us three above now envisage it is effectively a blank canvas and then the images and videos get dynamically loaded into the Flash movie and placed in random locations in the movie (almost like papers scattered on a desk so overlapping will occur). Then the user can (ideally using a Nintendo Wii controller) movie the images around, perhaps enlarge them etc.

2. The Proposal

There must be other questions that need to be answered. The ones we have so far are just the ones that Joasia said off the top of her head.

 3. Actions

All – Does any one know how to write this type of proposal? Can anyone think of any bits we need to put in it apart from Joasia’s questions? Does anyone know of any sound libraries that we can enabl access to?

Chris – Write a couple of paragraphs on technical side of the project. Then send to Nick.

Nick - Amend what Chris has sent me if necessary, add my parts to it and then pass on to Steve and Pete. I’m going to start the Flash movie as well.

Mike - Write about the branding/marketing side of the project and then pass on to Steve and Pete.

Steve & Pete - Will compile the proposal.

4. Notes

We discussed the idea of alternating the meetings for this module so one week it is Wednesday and the next it is Friday. Is this a problem for anybody?

The next meeting is Wednesday at 10:00.

———

Thanks,

Nick

Initial answers for proposal (Nick)

Hi All,

Below are some initial answers that I have come up with to the questions that Joasia proposed to us:

——————

What makes it specific for curating?

Curatos is specific for curating as the Curatos software is a content specialist that enables the production and distribution of art works and has the ultimate responsibility for the artworks that are created using it. Also, Curatos will share the artworks created with it to the public in a number of scenarios like through an interactive installation (e.g. in the Planetarium Dome, Drake Circus Shopping Centre) and the World Wide Web.

The Curatos system enables possibilities that don’t exist with the usual institution model of curating (e.g. museum). It creates dynamic possibilities using the World Wide Web to bring curators together from around the world. The end result is a diverse curatorial process that features a community with a collection of art works and an online space to display them.

How is it different from MySpace/Flickr etc?

Curatos differs from ‘Web 2.0’ websites in that sites like MySpace and Flickr for example were not setup for curating. Instead, they provide opportunities for community engagement since MySpace is a social networking website and Flickr is a photo sharing website. Curatos will have a community of users but the art works they produce will be sourced from a number of areas like Flickr for photos and YouTube for videos.

People will look at Curator projects to see artwork rather than in the case of MySpace check on what a friend is doing or in the case of Flickr check the latest photos that a friend has uploaded to their allocated web space.

Is it a content management system, if it is how does it differ from others?

NEED TO LOOK AT FURTHER. AT THE MOMENT, YES IT IS!

Why would people want to use Curatos?

People would want to use Curatos perhaps if they do not have the know-how or the time to integrate Web 2.0 API’s (Application Programming Interfaces) like Flickr and YouTube themselves. The functionality to query and receive content from these types of sites will be coded by us and made available via a plug-in type method. Also, people who are interested in curating and technologies that could lead to a shift in the methods of curation will be curious about it.

How will we reveal Curatos to the public/audience?

We plan to exhibit it in unique spaces like the Planetarium Dome and the Drake Circus Shopping Centre. Also, we will investigate the possibility of exhibiting it in museums, a more traditional space for curation. We will also make it available on the World Wide Web so it is available to a wider audience. In summary, Curatos is not limited to a particular space.

——————

Thanks,

Nick

Neg Practice A Proposal

Hi everyone!

 Chris and I had a meeting on Wednesday to quickly go over a few points. I have added them to the proposal questions etc here.

Outline of project

 Might be a good idea to briefly go over intial ideas and how, as a team, we moulded them into one, to allow participation from everyone, and to make best use of our skills. Say why we are doing it and who are intended users and audience might be.  Maybe state where we intend to show/demonstrate the piece and how we want to make it accessible to as many people as posible not just the gallery afficinados /elite. How we intend to go about the task and the reasons why we chose to do it that way. Explain simply how it would work and why it would be of benifit to artists etc. 

The team needs to go into great detail about how Curatos will actually work. Explain each part of the process from typing in search options, to projection on screens, planetarium etc.

Important to say how an end user would be able to use it, will they need knowledge of Flash etc, or will there be some sort of explanation on the site of how best to make use of the xml feeds, and how to impliment them in Flash etc.

Will a complete multimedia novice be able to use it? Need to make it easy to use for artists/public not just techies?

End user decides what to do with it. Make it idiot proof.

  

What makes it specific for curating?

 Explain how Curatos allows for curating to take place.  Demonstrate how it will do this. Give example of how it may be used? 

How is it different from MySpace/Flickr etc?

 Demonstrate the uniqueness of the project and how users will have more control over how their work is viewed by others.Pull other peoples work in more like a social operating system. 

Is it a content management system, if it is how does it differ from others?

 Yes, pulls in info from other places 

Why would people want to use Curatos?

 Allows for artists/users to exhibit their work in more unique manner. Whether online/virtual or in real space.  

How will we reveal Curatos to the public/audience?

 Via the web, Planetarium, Museums, Eden, Shopping centres (Drakes circus) etc Roles of the team 

Emphasize the collabrative process in coming up with the ideas, presentations etc. How we will delegate the work to take advantage of the skill base and to allow for effiecncy in completing tasks to deadlines

 Nick, Chris- coding (xml feed)

Mike- the look (marketing, look and feel)

Pete/stephen-web interface, content (playable on Mikes screen?)

Xaio-content   

Deadlines Proposal November 30th

 Outcomes 

Many curation pieces don’t seem to work, if we can make a simple working  “prototype” that does actually what we say it will do, then this will be a major success I feel.   

Future uses Allow artists to show their work in a unique way 

Marketability 

As a group can we market the idea? 

Also, Pete and I were talking about the techies maybe producing a template, could be a Flash movie that makes use of the xml feeds or links. We could then maybe jazz this up or experiment with it to find other uses. It would also help bridge the gap between the techies and creatives, thus allowing us to have more involvement with the actual aim of the brief.

We need to ensure that ALL team members have roles as this is a team assignment!