User:Jules/digitalarchitecturearchives: Difference between revisions
(Created page with "<b>Digital architecture archives (Henk Vanstappen and Wim Lowet)</b> The memory of the architect. Creation and preservation of born digital architectural archives CVAs : cen...") |
No edit summary |
||
Line 1: | Line 1: | ||
<b>Digital architecture archives (Henk Vanstappen and Wim Lowet)</b> | <b>Digital architecture archives (Henk Vanstappen and Wim Lowet)</b><br> | ||
<i>The memory of the architect. Creation and preservation of born digital architectural archives</i><br><br> | |||
CVAs : center of expertise coordinating the archiving of private documents for the architectural heritage in Flanders.<br> | |||
DATABLE : consultancy in sustainable digital collection management.<br><br> | |||
Completed research steps :<br> | |||
- survey : how are digital architectural archival records created and managed<br> | |||
- case study : what steps are necessary at ingest and preservation<br><br> | |||
<b>1. Born-digital architectural archives</b><br> | |||
1. Born-digital architectural archives | |||
Softwares being used ... | Softwares being used ... | ||
drawing and design (sketchup and autocad mainly) + presentation and visualisation (Adobe mainly) | drawing and design (sketchup and autocad mainly) + presentation and visualisation (Adobe mainly) | ||
Line 17: | Line 15: | ||
- Intelligence (layers, text, look and feel, behaviour, complexity grow in each version) | - Intelligence (layers, text, look and feel, behaviour, complexity grow in each version) | ||
2. preservation issues | <b>2. preservation issues</b><br> | ||
i. seldom open technologies | <i>i. seldom open technologies</i><br> | ||
problems with automatic file format identification and validation | problems with automatic file format identification and validation<br> | ||
few alternatives = greater risk for obsolescence (mac vs windows for proprietary software, some aren't cross platforms) | few alternatives = greater risk for obsolescence (mac vs windows for proprietary software, some aren't cross platforms)<br><br> | ||
<i>ii.often problems with backward compatibility</i><br> | |||
some files versions are too old to be opened by recent versions of the softwares<br><br> | |||
<i>iii.technology is complex</i><br> | |||
each program has its own underlying method to define geometrical forms<br><br> | |||
<b>3. policies for preservation</b><br> | |||
- migration vs emulation<br> | |||
- importance of knowledge about the collection<br> | |||
- importance of central storage<br> | |||
- importance of making choices<br><br> | |||
threats <br> | |||
→ OS migration <br> | |||
→ employees leave firm (expertise)<br> | |||
→ failure in software company<br> | |||
→ raise in license costs<br><br> | |||
stakeholders | stakeholders<br> | ||
→ colleagues | → colleagues<br> | ||
→ legal department | → legal department<br> | ||
→ PR-department | → PR-department<br> | ||
→ clients | → clients<br> | ||
→ fanbase | → fanbase<br> | ||
→ future generations | → future generations<br><br> | ||
Use cases can be varied( post construction management, website publishing, book publishing, exhibitions...) | Use cases can be varied( post construction management, website publishing, book publishing, exhibitions...)<br><br> | ||
Is editing necessary? Is look and feel important? Does text need to remain in the same font? How about layers? | Is editing necessary? Is look and feel important? Does text need to remain in the same font? How about layers?<br><br> | ||
2 major options | 2 major options<br> | ||
→ migration | → migration<br> | ||
→ emulation/software preservation | → emulation/software preservation<br><br> | ||
Migration to open format | <b>1. Migration to open format</b><br> | ||
→ file format specs published | → file format specs published<br> | ||
→ no licensing issues | → no licensing issues<br> | ||
→ software tools available | → software tools available<br> | ||
→ no significant information lost | → no significant information lost<br> | ||
→ reversible to original | → reversible to original<br><br> | ||
Some tests have been done to STEP | Some tests have been done to STEP<br> | ||
lots of layers vanished | lots of layers vanished<br> | ||
same with VMRL | same with VMRL<br> | ||
Emulation | <b>2. Emulation </b><br> | ||
what do you want to emulate? | what do you want to emulate?<br> | ||
→ document original software versions | → document original software versions<br> | ||
→ archive original software | → archive original software<br> | ||
→ complex technology | → complex technology<br> | ||
→ licensing issues | → licensing issues<br><br> | ||
knowledge about the collection | Important things to have in mind:<br> | ||
Documentation of the working process. | knowledge about the collection<br> | ||
Understanding about design process is a prerequisite to make decisions about the preservation actions. | Documentation of the working process.<br> | ||
Understanding about design process is a prerequisite to make decisions about the preservation actions.<br><br> | |||
MDMA project | <b>Case : MDMA project </b><br> | ||
clear naming convention and folder organisation | clear naming convention and folder organisation<br> | ||
http://www.projecttracks.be/en/projects/detail/digital-file-management-at-mdma | http://www.projecttracks.be/en/projects/detail/digital-file-management-at-mdma <br><br> | ||
knowledge of collection (arrangement, design process) | Steps undertaken:<br> | ||
central storage | knowledge of collection (arrangement, design process)<br> | ||
knowledge of stakeholders, use cases, threats, options, costs and gains | central storage<br> | ||
knowledge of stakeholders, use cases, threats, options, costs and gains<br><br> | |||
3D doesn't just apply to architecture | Also : 3D doesn't just apply to architecture | ||
Film preservation, sculpture etc... | Film preservation, sculpture etc... |
Latest revision as of 18:44, 30 October 2015
Digital architecture archives (Henk Vanstappen and Wim Lowet)
The memory of the architect. Creation and preservation of born digital architectural archives
CVAs : center of expertise coordinating the archiving of private documents for the architectural heritage in Flanders.
DATABLE : consultancy in sustainable digital collection management.
Completed research steps :
- survey : how are digital architectural archival records created and managed
- case study : what steps are necessary at ingest and preservation
1. Born-digital architectural archives
Softwares being used ...
drawing and design (sketchup and autocad mainly) + presentation and visualisation (Adobe mainly)
- 2D + 3D geometry (vector based)
- Intelligence (layers, text, look and feel, behaviour, complexity grow in each version)
2. preservation issues
i. seldom open technologies
problems with automatic file format identification and validation
few alternatives = greater risk for obsolescence (mac vs windows for proprietary software, some aren't cross platforms)
ii.often problems with backward compatibility
some files versions are too old to be opened by recent versions of the softwares
iii.technology is complex
each program has its own underlying method to define geometrical forms
3. policies for preservation
- migration vs emulation
- importance of knowledge about the collection
- importance of central storage
- importance of making choices
threats
→ OS migration
→ employees leave firm (expertise)
→ failure in software company
→ raise in license costs
stakeholders
→ colleagues
→ legal department
→ PR-department
→ clients
→ fanbase
→ future generations
Use cases can be varied( post construction management, website publishing, book publishing, exhibitions...)
Is editing necessary? Is look and feel important? Does text need to remain in the same font? How about layers?
2 major options
→ migration
→ emulation/software preservation
1. Migration to open format
→ file format specs published
→ no licensing issues
→ software tools available
→ no significant information lost
→ reversible to original
Some tests have been done to STEP
lots of layers vanished
same with VMRL
2. Emulation
what do you want to emulate?
→ document original software versions
→ archive original software
→ complex technology
→ licensing issues
Important things to have in mind:
knowledge about the collection
Documentation of the working process.
Understanding about design process is a prerequisite to make decisions about the preservation actions.
Case : MDMA project
clear naming convention and folder organisation
http://www.projecttracks.be/en/projects/detail/digital-file-management-at-mdma
Steps undertaken:
knowledge of collection (arrangement, design process)
central storage
knowledge of stakeholders, use cases, threats, options, costs and gains
Also : 3D doesn't just apply to architecture Film preservation, sculpture etc...