Transcript CONTENTdm - University of Iowa

Pre-Conference Workshop:
The Care and Feeding
Fifth Annual
Post-ALA
MidwestAnnual
Users
JulyGroup
11, 2008
of
Compound Objects
April 7, 2010
Geri Ingram
OCLC Digital Collection Services
Manager, User Services
Welcome CONTENTdm users
To get the most out of this session
Either you have:
• Experience building CONTENTdm collections
OR
• Attended recent CONTENTdm Training
Agenda
8: 30 – 9:00
Context-setting
9:00 – 9:30
Data file organization, logic, and naming
9:30-9:45
Break
9:45- 11:45
Exercises
11:45 – Noon
QA
Context-setting
Real world application—it’s all about the
users and what collections you have
• What are the materials you have?
• How do your users want to access them digitally?
• You must understand how the tools work with YOUR data
• Which tools are appropriate for your materials?
• What do different wizards expect by way of file naming and
organization?
What are your users looking for?
Yearbooks, newspapers…
Photograph collections…
Historical postcards…
Archival papers…
How are they looking for these materials?
Browsing
Searching--across collections, subgroups?
• Known item searching, and/or
• Total recall by topic, name, etc.
Do you have text-rich materials?
• If so your users hope for full-text search-ability across the
repository.
Formats: Born-digital
Papers, videos, audio files
In CONTENTdm, these are natively simple items, not
compound objects, e.g.:
.pdf
.mp3
.avi
Formats: Digitized (reformatted)
If still to be digitized
• You have control over the project specification
• File name and organization
• Metadata automatically and manually created
If already digitized
• You choose among the tools for the one that best fits your
data organization
CONTENTdm Compound Objects
CONTENTdm defined classes —when 2 or more simple items
are bound together by logic (and XML):
• Documents—”flat”—a series of related items
• We will load multiple letters, two ways
• Postcards—exactly two digital files; two-sided items
• Monographs—”hierarchical”—items related in a hierarchy
• We will load a single book (a section of a book with chapters)
two ways
• Six-sided views—exactly six digital files (known as “picture
cube”)
First things First-Collection Configuration choices
• If your materials have searchable text, you will
need
One empty, searchable field configured as “Full
text search” data type to hold text
• If users expect to see “top” level records only in
the search result set: set CISOSUPPRESS parameter
to suppress display of components of compound
objects in search results.
What PDF conversion does and does NOT do.
It DOES allow very large pdf files to be indexed, searched and
retrieved quickly—EACH page can have 128,000 characters.
It DOES allow end users to search for text across huge volumes of
materials without having to re-execute the search inside each
document using the Adobe Reader “binoculars” search.
It DOES allow the end-user to choose from ‘compound-object’
viewer three more views, including subset and complete Adobe
Reader view.
It does NOT allow you to “nest” compound objects. I.e., you can
assemble multiple PDFs as a compound object, but you cannot
then take advantage of the page-level indexing, display etc.,
within each “page” of the compound object.
9:00 File organization and naming
Preparing to use the Project Client wizards
• File organization for adding materials commonly assembled as
compound objects, e.g.,
• Yearbooks, Papers, Postcards, Books
• Adding single and multiple compound objects
• Add compound objects:
• Having components in organized file folders only, or also
• Having text files that describe the objects and the items
File and folder facts: regardless of wizard to
be used in Add compound object function,
SCANS are held together in one folder
• For all compound object classes
• Document, Monograph, Postcard, Six-sided view
• For each compound object
• All digital files must reside in one directory/folder
• This is true whether you are adding multiple compound
objects or a single compound object.
Example: a single Document
using Add compound object
Directory Structure wizard
Object List wizard
Example: a single Monograph
Using Compound Object wizard
Where structured by
folder organization
Where structured by a tabdelimited text file
ALSO—When you add multiple compound objects
using tab-d files:
Their nature and placement changes
Got page-level metadata?
Got only object-level metadata?
Each object needs its own.
All objects share one.
Compound objects using tab-d files, depending upon
the Object class:
The structure of the .txt file changes
Monograph: two new
Document: all “columns”
“columns” define structure
are field attributes
Questions & Answers
Getting help with compound objects
• User Support Center
• Tutorials to study
• Installing, activating the OCR extension
• Help files related to text works
• Write [email protected]
Questions?
Geri Ingram
[email protected]