Documentation

The following is the copy/pasted text that explains documentation guidelines from - http://imagearts.ryerson.ca/sdaniels/physcomp/documentation.html.
I am posting this as reminder to fellow classmates but to myself that these are the expectations we should set for ourselves with regards to our projects.
With finals sneaking up fast - I feel this is a heavy reminder for myself because once the rush sets in, minor details can be lost and the difference between an A or B with explaining a work.

__________________________________________________________________________

Documentation

A piece that is not documented DOES NOT exist.

Documentation is the primary link between your work and the rest of the world.  It is possible that more people will see your documentation than will ever see your work first hand.

Therefore, documentation that is done well, as apposed to poorly or not at all, will mean the difference between getting awards / scholarships / grants / shows / job interviews and being IGNORED.

Keep in mind that documentation is also a form of self-evaluation and reflection.


Good Documentation Practices:

Identify Audience:

- as with everything, know to whom you are directing this document: curators, other artists, the public, prospective employers
- what does the audience need to know
- to what extent do you want / need to show inner workings?
- do the images you shoot require text based support? or voice over?
Identify Stage:

Are you Producing Outreach Material? Or Production Documents? Or a Finished Project?
- large projects may require you to document prototypes to aid in gathering additional funds – these documents will be sent out with grant applications and occasionally to curators
- smaller projects may only require deliverables after completion
- ALL PROJECTS should be documented during production – you shoot keep records of ideas, sketches, drawings, virtual and physical models, interface tests – every step of the way.
Identify Media and forms of distribution:

- as you are all aware different media provide different opportunities for producing records.
- Decide if you will shoot stills and video (stills alone are OK for static works, but anything dynamic requires both)
- Web page requirements
- DVD, mail, carrier pigeon?

What to Include:

Summary:

- Project Name
- Project Synopsis
- Keywords
- Description of User Experience
- Artist Statement – this is not a description – it is a personal reflection
- references to related works (your own first, then others)

Technical Summary:

- explanation and overview – can include imagery – you may wish this to be separate, or included in the main document
- this is often useful when doing artist talks  — depending on audience
- list peripherals and special equipment required
- OS specs and hardware requirements
- Clear description of space requirements
- KEEP copies of your CODE – don’t need to distrubute this but ARCHIVE IT with everything else.
Contact Info:

- Bio (all producers)
- Contact person (identify one if a group)
- Contributers contact info – (for reference)
- Credits
Images

(Low (72 dpi) and High Resolution (300dpi)):
- 5 -10  images that illustrate overall piece, user experience, technical details
- on web sites, you may wish to identify media images – these must be 300DPI and should be your best shots – these will be included in press kits etc.
Video:

- keep this to 4-5min tops – most juries will look at your documents and all submissions for no more than 15min – a 20 min doc will be partially viewed or ignored
- WEB: compress and optimize for at least 2 connection speeds (dialup and high speed) – test them – on dial up.  File size for each minute should be about 2.5MB at 320x240 for high bandwidth, and around 100K at 160x120 for dial-up.
- DVD: Prep a high resolution copy for DVD.
- SOURCE: ARCHIVE YOUR SOURCE FOOTAGE and your EDL (edit descition list)
Video Documentation Should INCLUDE:

- explanation of project
- user experience
- project credits
- funder acknowledgement
Treat documentation as a video/film shoot.  Light properly, think about sound, use external mic’s, storyboard or write out an outline.

Get an establishing shot, then show experience then show details.  Show, don’t tell.  Use voice only when needed.  Text panels at the beginning of video may be better than voice – use your judgment.

If you go in thinking you will just wing it – you will end up with lousy docs.

1. mangalcun liked this
2. dwbl liked this
3. sambjbrown posted this