Transcript PowerPoint-esitys

The Finnish National Gallery
Database implementation
Juha Inkari
Aimari Oy
[email protected]
The Finnish National Gallery
Database implementation
 Old/current relational database
 New relational database designed for CRM
compatibility in mind
 Conversion application to copy database
contents from the old database to the new
database
 Task specific user-interface (10 modules)
Starting point
 ”Flat” schema
 Missing data or data in wrong place
 First correct and cleanup data in the
current/old database
– average 1 error correcting update per row
New database
 SqlServer 2000 RDMS
– can be managed
 Use CRM as a guideline
 Compatibility
– in the future possible to export database in a
CRM compatible XML Document
Support for CRM
 Mapping from current data structures and
data to relevant CRM structures was done
 Based on needed CRM structures a
relational database schema was designed
”Flat” schema
 Source database
E23/E73 Information Carrier & Object
P46 is composed of / forms part of
P62 depicts
P129 is about
E34 Inscription
E3 Condition State
P46 forms part of Collection
P45 consists of
E35 Title
P2 has type
P3 has note
P70 is documented in
E54 Dimension
E42 Object Identifier
E78 Collection
E57 Material
Translation
E55 Type
Note
E31 Document
Step 1 : Add Events
E12 Production Event
E8 Acquisition Event
P14 carried out by
P32 used general technique
P3 Production has note
P3 acquisition has note
P70 acquisition is documented in
E9 Move
E31 Document
P25 moved by
P108 was produced by
E23/E73 Information Carrier & Object
P24 changed ownership by
Step 2 : Add Actor
E39 Actor
E12 Production Event
E8 Acquisition Event
P14 carried out by
P32 used general technique
P3 Production has note
P3 acquisition has note
E9 Move
P70 acquisition is documented in
P25 moved by
P108 was produced by
E23/E73 Information Carrier & Object
P24 changed ownership by
E31 Document
Step 3 : Add Place
E53 Place
E39 Actor
E12 Production Event
P14 carried out by
P32 used general technique
P3 Production has note
E9 Move
P25 moved by
P108 was produced by
E23/E73 Information Carrier & Object
Step 4 : Add Time-Span
E52 Time-Span
E53 Place
E39 Actor
E12 Production Event
P14 carried out by
P32 used general technique
P3 Production has note
E9 Move
P25 moved by
P108 was produced by
E23/E73 Information Carrier & Object
Add Activity and properties to
support documentation needs
E52 Time-Span
E53 Place
E39 Actor
P14 performed
E7 Activity
P16 was used for
P19 was made for
E23/E73 Information Carrier & Object
Normalised database
The normalised database has tables for
objects
actors
events
places
time-spans
Yet there has not been a need to denormalise
for performance
Order or precedence
 Catalogers want to keep the order of precedence
 classifications
– work of art is classified to be as more of a type
”drawing” than of a type ”painting”
 materials and techniques
– broader term like ”metal” before specialized term like
”bronze”. Also main materials are listed before
supplemental and not so important materials.
Production carried out by
extensions
 Order of precedence to keep list of artists in
the precise order requested by the artists
themselves
 Note used to document unknown artists
School of work
 Belief/certainty field
– Belief/certainty classification
– Mutually exclusive cases
Original and reproduction
Photo is about
"Artist at the
Exhibition
openings at ..."
Image File depicts Photograph
Photographing
of the original
photographed by Hasse L. Blad 1997
Scanned
Image File
Scanning
scanned by Photo Shop 2001
Missing original
Original
photograph
missing
Photo is
about
"Artist in
Paris..."
o
ot
ph
n
n.
io al
ct igin atio
u
od or r m
pr the nfo
e
ti
er o
th on t ven
m ti
E
fro llec tion
k
in co c
" l ur rodu
t
o
u
rtc s in hs P
o
i p
h
"S ich gra
h
w oto
ph
Reproduction
Photographing
photographing
of the original
Photographed by N. N. 1888
 Shortcut to enable joining subject and time of
production for example
Making CRM ”user friendly”
 Users do have some kind of mental model
about the system
– our userbase refers to object records as ”cards”
 Focus attention to the work problems like
classification
 Users could apply their CRM knowledge (if
there would be any) to work problems
Goals
 Revise the cataloging rules from 1998
– the new cataloging rules should somehow refer
to CRM
 In the future with successfull training
curators developing cataloging rules could
also map those documentation needs to
CRM
Thats all folks
