Luna Insight and Rutgers Art History Collections

1
Luna Insight and Rutgers Art History Collections

• Art History is comprised of three collections
• Department Collection 53,584 images
• Teaching Collection 12,178 images
• Public Collection 3,110 images
• Total 68,872 images

The Art History Collections images are added in
periodic batches of approximately 4000-6000
images. For these batches the Art History
department delivers source images, TIFFs, and
there latest Access database for the
collections. The batch loading method we use in
Luna requires us to export the metadata from
Access into a Oracle database of a similar
design. After loading the data Lunas built in
indexer adds the new records to the
collections. Finally the source images are
processed creating usable derivatives and they
are associated with there corresponding metadata
record.
2

• DB Structure prior to Upgrade
• 19 tables
• depth 3

3

• DB Structure after the Upgrade
• 39 tables
• depth 6

4

• Overlay of old and new DB structures
• No change (yellow)
• Supports existing (orange)
• New (white)

5
Configuring Luna Insight to index source tables
Establish the database structure you wish to
index, create table configuration in Insight
Administrator.
6
Establish the database relationships using Edit
Joins in Insight Administrator.
7
Establish fields that will be displayed, keyword
searchable and or data field searchable using
Insight Administrator.
Fields 81 - Display 65 Keyword Search 39 Data
Field 26
8
With the fields created we group appropriate
fields together using Insight Administrator.
9
Now we need to create a field standard for the
new schema using Insight Administrator. We call
the field standard Rutgers Art History but it
is equitable to our VRA Core 4 model.
Every field we defined is mimicked here, along
with its configuration setting (Display, Keyword
Search, data field etc.)
10
To provide better cross collection searching we
map our new Rutgers Art History standard to
Insights base standard, CDWA.
11
We also map DublinCore to Insights base standard,
CDWA.
12
Finally we map our base standard, RUcore, to
Insights base standard, CDWA.
13
Mapping all standards against CDWA you can then
use CDWA as a crosswalk for displaying fields in
different standards.
We used a spreadsheet to collaborate on how the
mappings should be configured in Luna.
14
Chad Mills cmmills_at_rci.rutgers.edu http//lunaproj
ect.rutgers.edu/