Projects

All projects residing in the project folder have to be valid Portfolio Project Format to work with the presentation applications. This format is really just a set of file naming conventions and a special text file, project.yaml, containing YAML-formatted project metadata.

The folder structure is inspired by the application running the intermedia lab website, Staceyapp 3.0. This makes it possible to share a common file structure among website and AtriumDisplay and other apps that might want to display the portfolio.

Also the website can publish the project portfolio as json/atom/rss feeds with web friendly image sizes, downscaled server side from the original project assets. Read more in the website documentation on the page Intermedia Lab Website.


Folder structure


AtriumDisplay Resouce Files.png

Each project has its own sub-folder containing project assets such as images, videos and pdfs alongside a project.yaml text file containing project metadata.

Please note that AtriumDisplay.app and the website will show all projects, whose folder name starts with a number and a dot. This follows the publication method of Staceyapp. The convention is to use a date and the project name in the format YYYYMMDD.Project-name as shown in the Resource Folder screenshot above.

Changes to the contents of the original folder are reflected on the website and the displays within 20 minutes via BitTorrent Sync.

Project Metadata


The project.yaml file in each project folder contains the metadata, that makes the image/video/pdf collection meaningful. The file must be properly formatted YAML to function. The file contains written information about the project, authorship, credits, tags, webiste, license etc.

project.yaml

title: Project Title # This is a comment
 
date: 2012-03-06  # Year-Month-Date, eg. january 3rd 2004 = 2004-01-03
 
homepage: http://CHANGEME.dk
 
participants: # a list of elements with each three attributes; [name:], [mail:] and [role:]
 -
   name: FirstName LastName
   mail: user@server.domain
   role: Role # eg. Master Student, Advisor, Assistant
 -
   name: FirstName LastName
   mail: user@server.domain
   role: Role # eg. Master Student, Advisor, Assistant
 
credits: # a list of [name:]s that should be credited [for:] something, just delete the tag and the list if not relevant. This could be sponsoring companies, partners or the photograper.
 -
   name: Someone
   for: Something
 
tags: # relevant keywords. We want to use ITU course codes eg. DCDP-2013E and terms like Master Thesis, and general concepts and themes like eg. Food or Governance
 - PhD Project
 - Research
 - Architecture
 - Software
 
materials: # just the stuff that went into making the project
 - arduino
 - wood
 - computer
 
summary: | # Max 50 words - is shown on website and screen presentations (eg. the Atrium Displays) All paragraphs start with two white-spaces.
  Practice-based research in architecture provisioned with software that has the capability to modify to change in the environment and incorporate new parameters from the environment. As new architectural design practices emerging from this development, what are the implications this has on the built environment and our spatial experiences?
 
abstract: | # Max 150 words - is shown on website
 
legal:
 - copyright: # the name of the formal copyright holder
 - cc-url: http://creativecommons.org/licenses/by/4.0/ # any valid url to a creative commons licence is encouraged, or you can paste in a raw text of an alternative licence below.
 - non-cc-license-text: | # put the full raw licence if not a creative commons below, e.g.:
    Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
    The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Parameter
Sub-parameter
Type
Default
Description
title:

String

The project title.
date:

YYYY-MM-DD
2013-01-01
The project date, usually the date of finalisation, first publication or hand-in.
homepage:

URL

Full url to project website. [optional]
participants:

Dictionary list

List of project participants, give at least one.

name:
String

Full name of a participant

mail:
String

Email address of a participant (not made available online)

role:
String

Role of participant, eg. Student, Advisor, Designer, Dancer etc.
credits:

Dictionary list

List of other people that should be credited for something within the project
[optional]

name:
String

Full name of person, company or institution

for:
String

What to credit for, eg. Photography, Styrofoam, Cake or Sponsoring
tags:

String List

Tags, both internal ITU stuff like eg. course acronym, research group name and more general concepts such as relevant key terms about theme and subject area. The special tag Featured will display the project prominently on the website and screens.
materials:

String List

A list of materials used, e.g.. styrofoam, whipped cream, arduino, tape. For gallery like textual presentation of artifacts.
summary:

Paragraphs

Max 50 words describing your project as briefly and understandably as possible. Mainly for screen presentation. Could be a catch-prase.
abstract:

Paragraphs

Max 150 words describing your project academically.
legal:

Dictionary

Here you claim your rights and decide how you want to share your project documentation and assets.

copyright:
String

Full name of the copyright claiming entity

cc-url:
URL

Full URL to a creative commons license, or nothing if you choose a non-cc license.

non-cc-license-text:
Paragraphs

Full license text of an alternative license, that is not available from the creative commons website. Not necessary when using Creative Commons