User:SN/Documentation Failure: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<div style='width:900px;'> | |||
On the first thematic project, we were speculating on documentation practices and methods, especially on documentation of the digital objects. As the exercise, we were asked to create a document, that concatenates previous records of graduation projects. The epub output format was our single constraint. Reflecting on what we were discussed about documentation processes, we concluded that “Distortion [ is an ] inevitable consequence of Documentation”. We were looking at the process as our subject, which seeps into our method as well as design. Documentation of documentation of document creates distortion and buries original object under the layers of documentation specificities and its media attributes. Being focused on the process of documentation, we decided to pick scanning as a method and general strategy to work with content. Scanning as a process is very fragmented yet systematic with the aim of creating an entity. When you are scanning the scanner has no idea of the whole, the image is that of the fragmented images. Scanning as a concept could be implemented different ways on different types of documentation objects. To underline disruption while documenting, while we are scanning something, there exists the framework - even it is successful or unsuccessful - just doing it once. | On the first thematic project, we were speculating on documentation practices and methods, especially on documentation of the digital objects. As the exercise, we were asked to create a document, that concatenates previous records of graduation projects. The epub output format was our single constraint. Reflecting on what we were discussed about documentation processes, we concluded that “Distortion [ is an ] inevitable consequence of Documentation”. We were looking at the process as our subject, which seeps into our method as well as design. Documentation of documentation of document creates distortion and buries original object under the layers of documentation specificities and its media attributes. Being focused on the process of documentation, we decided to pick scanning as a method and general strategy to work with content. Scanning as a process is very fragmented yet systematic with the aim of creating an entity. When you are scanning the scanner has no idea of the whole, the image is that of the fragmented images. Scanning as a concept could be implemented different ways on different types of documentation objects. To underline disruption while documenting, while we are scanning something, there exists the framework - even it is successful or unsuccessful - just doing it once. | ||
| Line 33: | Line 35: | ||
[[File:2015_Anne_Lamb_documented_Elleke_Hageman.png|1000px]] | [[File:2015_Anne_Lamb_documented_Elleke_Hageman.png|1000px]] | ||
</div> | |||
Revision as of 14:06, 5 December 2016
On the first thematic project, we were speculating on documentation practices and methods, especially on documentation of the digital objects. As the exercise, we were asked to create a document, that concatenates previous records of graduation projects. The epub output format was our single constraint. Reflecting on what we were discussed about documentation processes, we concluded that “Distortion [ is an ] inevitable consequence of Documentation”. We were looking at the process as our subject, which seeps into our method as well as design. Documentation of documentation of document creates distortion and buries original object under the layers of documentation specificities and its media attributes. Being focused on the process of documentation, we decided to pick scanning as a method and general strategy to work with content. Scanning as a process is very fragmented yet systematic with the aim of creating an entity. When you are scanning the scanner has no idea of the whole, the image is that of the fragmented images. Scanning as a concept could be implemented different ways on different types of documentation objects. To underline disruption while documenting, while we are scanning something, there exists the framework - even it is successful or unsuccessful - just doing it once.
