bas van velzen (university of amsterdam), documentation or reporting?
TRANSCRIPT
structure or jumble?
ordocumenting reporting
inle
idin
gin
trodu
ctio
nthe documentation burden•obligation set by our organisations•responsibility of the conservator towards
the object
inle
idin
gin
trodu
ctio
nspecialisation diversity•specialisations differ in object
complexity•specialisations differ in time spent per
object•specialisations differ in documentation
culture
inle
idin
gin
trodu
ctio
ncomplexity
inle
idin
gin
trodu
ctio
ntime spent on object
20
150
minutes
hours
inle
idin
gin
trodu
ctio
nculture•education- formal training- on the job training
•tradesmanism vs academia•institutional vs self employed
inle
idin
gel
emen
tsyou are also documented•S = subjective: anamnesis, problem
based•O = objective: result of examination•E = evaluation: diagnose•P = plan: treatment
inle
idin
gel
emen
tsthe object being documented•S = treatment necessity- exhibition, damage, maintenance, bad repair
•O = condition report- expertise conservator, examination/research
•E = treatment proposal•P = treatment (to be documented)
inle
idin
gel
emen
tswhat to document•who•what•where•when•how
•why ???
inle
idin
gel
emen
tselements of documentation•metadata > supplied by client/museum- object description, number etc.
•object description- size, technique, material, etc.- condition/damage > treatment proposal
•treatment- operations: what, how, where, with what (tools)- materials used: what, composition, origin- illustrations, before, during, after
inle
idin
gpr
oble
ms
prob
lem
s pr
oble
ms
what is not part of documentation•(art)historical essays•implicit pseudo documentation- not “B72” but:
ethyl-methacrylate copolymer: Paraloid B72- “surface cleaned” without method, means, location
•unreadable illustrations- “look how many clamps I have”- position/orientation of object different in every picture
•report
inle
idin
gso
lutio
n?documentation vs report•documentation is for you/colleague•documentation should go with object
lingua franca - jargon of the conservator
•report is a narrative•report explains the why•report is for client/non-colleague
the “non” jargon speaker
inle
idin
gso
lutio
n?documentation vs report•report can be constructed from the
information in the documentation
•documentation derives the why from protocol/shopbook, work journal
•only treatment variations have to be documented: written down
inle
idin
gpr
oble
ms
prob
lem
s pr
oble
ms
time spent on object
20 150 1 : 7,5
20150
minutes
hours 7,5 : 1
inle
idin
gw
hat t
o lo
ok fo
r?current practice•analog: physical- forms, reports- illustrations
•digital: virtual- text document (.doc)- spreadsheet (.xls)- database (.dbs .fm)
inle
idin
gw
hat t
o lo
ok fo
r?analog•is infrastructure still in place?- accessability to documentation/reports- suspension files etc.- bulky, single location
•documentation material decays- quality of paper and ink- photos, negatives
•transition to digital- large files- mostly not machine readable (OCR)
inle
idin
gw
hat t
o lo
ok fo
r?
•compatibility- platform (PC, UNIX, MAC)
•quality IT-structure: back-up!- by conservator- by institution
•accesibility is not an issue- access can be regulated
•obsolescense- backward compatible- hardware not available/breaks down- software does not run on modern machines
digital in general
inle
idin
gw
hat t
o lo
ok fo
r?digital traps•text documents (.doc)- only non discriminative search possible (flat)- invites narrative instead of documentation- easy link illustration-text- infinite freedom- relation to other file needs extra keywords- other program needed to establish links
inle
idin
gw
hat t
o lo
ok fo
r?digital traps•spreadsheet (.xls)- in office-suite: “no need” to purchase database- hybrid use: actual function is for complex calculations- has to be designed and built- only flat searches possible (one level)- relations between data cumbersome- integrating information in database systems can be
tricky
inle
idin
gw
hat t
o lo
ok fo
r?digital traps•database (.dbs .fm)- to be purchased separately- learning curve- has to be designed and built
inle
idin
gw
hat t
o lo
ok fo
r?digital solution•database (.dbs .fm)- to be purchased seperately- learning curve- has to be designed and built
- multiple, discriminative search possible- easily made relations between records and data- easily publishable on the web- excellent integration in existing systems
inle
idin
gw
hat t
o lo
ok fo
r?status quo•no standard- what to document- how to make photos/illustrations
•no common thesaurus- names of techniques- names of deterioration/damage patterns- names of materials
•no repository- who can access data?- who pays?
