1. Merging Traffic Accessing Archival Collections and Museum Artifacts Through a Common Interface Brian Wilson Digital Access & Preservation
Mid-Michigan Digital Practitioners Group Meeting
October 14, 2016
Michigan State University Library
East Lansing, Michigan

2. bit.ly/2dAMzr9 #midmichdp
#midmichdp

3. Museum
Archive
Library

4. Archival Collection Related Collection Description Related Object
Group of Items
Item

5. Rome visit, June 2008 - 57 Ed Yourdon
Image: “Depressão Na Pista” by William Droops.

15. Connections Related Collection Collection Description Items in Item

16. Requirements Givens Implications Federated search
Convey LAM connections
Open archival collection record from an item record
Open all available items from a single item
Collection record must display when no digitized assets exist
Archival standards must be followed when possible
Givens
Common Museum and Archives CMS
Limited project budget and timeframe
Limited resources and technical abilities
Implications
DACS Single-level minimum records
Use PDF finding aids and link where available
Must differentiate between artifact and collection records
Library assets not included

17. Key Vendors and Technology
Axiell – EMu, Collection Management System
MS Windows file system
Perficient Digital – Project Management and Design
Sitefinity – Web CMS
Elasticsearch
Hostway Services – Cloud-based server and data hosting

18. High-Level Asset Flow
Image: Perficient Digital, The Henry Ford Solutions Document, May 2016, Page 8

19. Web System Architecture
Image: Perficient Digital,
The Henry Ford Solutions Document,
May 2016, Page 7

20. Data Flow – Simplified(?)
Web
EMu
xml
Online
Platform
Kiosk
Network
Storage
APIs
Video
Service MM
Storage

21. Data Harvest
Image: Perficient Digital, The Henry Ford Solutions Document, May 2016, Page 9

26. Events / News
Footer

27. Collection title
Link to
PDF finding aid
Abstract
Related objects
Bio/Hist
and Scope
Access terms
Related content
(when available)
Admin info
Digitized
content

28. Collection Title

29. Finding Aid

30. BioHist and Scope

31. Related Objects

32. Digital Asset Linking

33. Not a Perfect System Collection level, not container level
Can’t point to box or folder aggregations
Can’t relate collection to collection
Site demands graphic image for each collection
No links outside THF domain. Yet.
Image conversion can be very time consuming
But…..“Fitness for Use”

34. Foundational Work Create and publish more CMS records
Normalize existing CMS records
Establish cataloging rules
Commonize collection title format
Create ID numbers for assembled collections
Form titles for assembled collections
Create finding aids for assembled collections
Form rules for Related Objects and Content

35. Positives Archival description part of digitization workflow
Description can be part of reporting metrics
Standardization between records and among catalogers
Increases importance of CMS record
Reduces number of data silos
Exposes archival collections to new audiences
Internal and External

36. Better Connections Related Collection Collection Description Items in

37. Image: “501st 15” by Joe Philipson. https://www. flickr

38. Thank you! Brian Wilson Digital Access & Preservation Archivist
The Henry Ford
Dearborn, Michigan
@brilwil