Two-Way Integration between Adlib and DAMS Our Setup CMS Adlib - - PowerPoint PPT Presentation
Two-Way Integration between Adlib and DAMS Our Setup CMS Adlib - - PowerPoint PPT Presentation
Two-Way Integration between Adlib and DAMS Our Setup CMS Adlib XPlus DAMS Extensis Portfolio Either no object details, or different details to Full Object Details Adlib Low Res Images High res images with
SLIDE 1
SLIDE 2
Our Setup
CMS – Adlib XPlus DAMS – Extensis Portfolio
- Full Object Details
- Low Res Images
- Used by Collections Management staff
- Either no object details, or different details to
Adlib
- High res images with capability to convert
- Used by the Photo Librarian and Content team
SLIDE 3
- We needed 3 versions of every image – high res, low res and
Adlib resolution.
- We had to manually rename each image to make sure the
name was unique.
- Then we had to manually attach images, one object record at
a time.
- Most of our properties are country houses full of cutlery,
crockery and furniture sets that all need individual records!
Struggling to COPE (Create Once Publish Everywhere)
SLIDE 4
The context – a full inventory project for all our collections
- 100,000 items
- 47 properties
- 24 months
- 6 regionally-based project teams
Online engagement potential:
- Marketing
- Creative digital content
- Virtual tours etc.
- Social media
- Easier to share with others – research
and exhibitions
- Will allow us to publish our collections
- nline for the first time
Project Reveal
SLIDE 5
In an ideal world we would have…
- Just one version of every photo.
- One place to upload images (Portfolio)
- One place to enter object information (Adlib)
- A preview of the high quality image in Adlib…
- …and you’d see information about the object pictured in
Portfolio.
- This would all happen automatically with no double-entering
- f data , to make the most of the inventory teams’ time.
But has anybody ever done that before? Actually, yes! Adlib and Portfolio both have APIs to enable other applications to use the data. So what we needed was a piece of software to read from each API and write to the other.
Reveal Inventory Team South West
SLIDE 6
- Pronounced “sim”
- Stands for Collections Information Integration Middleware
- Developed and installed by Knowledge Integration
The Solution - CIIM
SLIDE 7
Adlib data in DAMS The
- utcome
- We already have 132,000 images
synchronized from our DAMS to Adlib this way
- Our DAMS web front-end is available to
all staff, who now see Adlib collections data with every digital asset
SLIDE 8
DAMS Images in Adlib The
- utcome
- Images are automatically generated in
preview resolution and served to our Adlib Internet Server, which we have now been able to make available to all
- f our staff and volunteers
- The next step is to fully publish our
collections online for all
SLIDE 9