Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Content-Specific Goals

No description
by

Jennifer Stertzer

on 17 February 2017

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Content-Specific Goals

GWFPP: Building Content-Specific Taxonomies and System Specifications
The Question:
How Did We Approach This?
Dublin Core
Getty Research Institute
Conclusion
Goals and Specifications
George Washington Financial Papers Project website
Occupations/Titles
Resources
Getty Research Institute
The Art & Architecture Thesaurus
Colonial Williamsburg
Mount Vernon

Content-Specific Goals
Metadata
Transcription and data
Annotation,
taxonomies
, glossary
Internal Linking
Indexing

Platform-Specific Goals
Open-source
Flexible editorial / publishing tools
Ability to download data
Powerful
search
and
browse
functions
Object - document
sender / recipient / author
document type
manuscript type
source (and information about that source)
date
to an extent, some content

Content - elements within a document:
people
places
services
events
commodities
currencies
occupations
We started with the content and considered:
What information is in the ledgers?
How should that information be recorded?
How does the information relate to each other?
How do we structure and define the information?
How do these things relate to browsing and searching capabilities?

What information is in the ledgers?
names of people, places, ships, and organizations
occupational names and titles
services being performed and paid for
types of currency
commodities of various types
How should that information be recorded?
How does the information relate to each other?
How do we structure and define the information?
How do we use this to develop browsing and searching
Taxonomy
controlled vocabulary list
hierarchical
allows for the classification of content
using multiple taxonomies allows for content to be categorized in multiple ways
Content Types
template designed specifically for content (document type, person, place)
pre-defined collection of fields
can call on taxonomy list through fields which allows content to be grouped together
Places
Account Names/People
PGWDE Index
Object-based vs Content-based
Metadata & Classifications
By focusing on and using content to create taxonomy lists, we are able to expose users to the language used by GW throughout his documents.
However, we need to be able to create hierarchies using broad terms to group the specific content-based terms.
Our cumulative index provided a good starting point of how best to conceptualize what these lists might look like and relate to one another.
standardized data about digital objects
use case example: Omeka
Object and Limited Content:
people, place, organizations, etc.
Drupal provides two solutions for this - taxonomies and content types
Occupations/Titles
first pass
What can be defined with standardized metadata schemas and what requires content-driven, customized vocabularies?
second pass
Are there established controlled vocabularies to accurately capture and categorize content within very specific collections, such as GW financial papers?

Things to consider:
time period
geographical location
demographics
networks
etymology
Additionally, we also wanted to consider the user and how information would be discovered through browsing and searching.
What can be defined with standardized metadata schemas and what requires content-driven, customized vocabularies?
Top level descriptions:
occupation
services
place
person
commodities
other?
At what level does it make sense to use broad classifications?
There are several broadly conceived object-based options (title, creator, publisher, description, date, location, etc.).
Much less for content.
Building Occupation Taxonomies:
all terms can have equivalencies on export
Consider object and content and what information needs to be captured and defined in both.
Determine what can accurately be defined with standardized metadata schemas and what requires content-driven, customized vocabularies.
Legacy considerations?
Map relationships.
Evaluate options within chosen platform/tool.
Consider how these decisions will impact and shape browsing, searching, and layout.
Develop a plan for sharing vocabularies and/or mapping to other vocabularies and schemas.
Steps to Building Content-Specific Taxonomies and System Specifications
Full transcript