Anithamudaliar (talk | contribs) ←Replaced content with '{{Infobox catalog |DDC = 306 |LCC = |UDC = 008 }} {{Sister project links}} {{Portal|Culture}} {{Cat main|Culture}} Category:Main topic classifications ...' |
Anithamudaliar (talk | contribs) No edit summary |
||
Line 12: | Line 12: | ||
[[Category:Sociology]] |
[[Category:Sociology]] |
||
[[Category:Categories requiring diffusion]] |
[[Category:Categories requiring diffusion]] |
||
http://www.hl7.org/implement/standards/fhir/v0.01/fhir-book.htm |
|||
Metadata as “information about the content that provides structure, |
|||
context, and meaning.” |
|||
Metadata is structured info that describes, explains, lcoates or |
|||
otherwise makes it easier to retrieve, use or manage info resource |
|||
Metadata represents a documented and orderderd summary of info that |
|||
describes something, in this case, spatial data. It provides the what, |
|||
where, when and why for spatial data |
|||
includes ownership and contact details and access and use conditions |
|||
DOeX provides precise specificaiton to enforce and ensure consistency |
|||
and interoperability. |
|||
define and describe metadata entities and elements and classify and |
|||
group relevant metadata elements with entities |
|||
assing structure and condition |
|||
Dublic core has 15 elements |
|||
9 mandatory |
|||
red - mandatory, green is optional |
|||
Metadata enables consistency, context, interoperability by facilitating |
|||
structured information exchanges. |
|||
Metadata is info about info objects, the content, the containers of info |
|||
objects. |
|||
Document |
|||
3 types of Metadata |
|||
Descriptive - enables context, defines content |
|||
adm - manage and enable consistency |
|||
date, category, make, origin |
|||
status, expiry date, content owner, access rights, |
|||
Structural - composition of compound objects |
|||
it enables interoperability |
|||
Name, first, last |
|||
Architecture |
|||
Presentation, storage, exchange |
|||
each side has a unique structure |
|||
Metadata Standards |
|||
X refers to it, y refers to it |
|||
XML standards enable exchanges; exchanges enable data linking, |
|||
What is defined by metadata standard |
|||
semantics means "bench" |
|||
Syntax is expression |
|||
If a capsium is a info object, a user is too |
|||
1. Make metadata a priority |
|||
link metadata to ROI, reduce inefficiences |
|||
create loyalty |
|||
2. Define your data, info objects, content assets, users, relationships, |
|||
1:1, 1:many, many:many |
|||
contextual inquires |
|||
discover what needs to be defined |
|||
Specify semantics, syntax, lexical rules |
|||
start with a controlled vocabulary |
|||
3. identify exchanges |
|||
internal and external |
|||
journey map |
|||
4. build the infrastructure |
|||
start small, build on what exists |
|||
borrow and reuse |
|||
Example - Bool |
|||
title, author, year, subject, no of pages |
|||
MDT types |
|||
structural - describes relationship within a info objec t |
|||
perservation - |
|||
What is an Element |
|||
Each info is describes using specific data items, these are called |
|||
elements |
|||
Metadata schema |
|||
set of MDT elements designed for a specific purpose such as describing |
|||
particular type of info |
|||
imposing restrictions and modifying vocabularies, we increase |
|||
interoperability with base standard |
|||
Element set |
|||
15 elements |
|||
All elements are optional and repeatable |
|||
elements can be refined using qualifiers |
|||
any syntax may be used to refine metadata |
|||
text based info objects |
|||
Core element set |
|||
title, type, format, identifier, owner, relation, date, description, |
|||
creator, contributor, rights |
|||
Element set |
|||
9 categories of elements are defined in Dublin |
|||
- elements may be repeated individually or as a group |
|||
- valus and data type are defined for each element |
|||
- they can be profiled to meet context specific needs |
|||
Values and DAta types |
|||
Value - restrictions on elements |
|||
Eg: controlled vocabulary |
|||
Data types |
|||
date and time |
|||
length |
|||
DOeX categories (taxonomy) |
|||
Document types |
|||
structure |
|||
Definition of DO, examples, quality, reusable DO |
|||
DO |
|||
with appropariate MDT descriptions, they can be modular units that can |
|||
be assembled together to allow exchange |
|||
Text is used to be talking about DOs |
|||
OAI-ORE standard for exchange of aggregations |
|||
Type 1 - internal entity (content repository), Type 2 - only links to |
|||
DOs (linking or MDT repos), Type 3 - links to DO and internal entities |
|||
(hybrids) |
|||
Usages - Functions |
|||
maintain - version control |
|||
retrieve - receive an object that has been requested |
|||
submit - provide an object to repository for storage |
|||
publish - provide metadata to other repositories |
|||
store - place a DO into the store with unique id that allow it to be |
|||
lcoated |
|||
gahter, - push/pull: obtain metadata about objects in other repositories |
|||
for wider searches and information via a clearing house function |
|||
three main types of metadata: |
|||
Structural: Defines the metadata elements that need to be collected; |
|||
labels like title, author, date created, subject, purpose, etc. Defining |
|||
these structural elements is typically based on a mix of organizational |
|||
and system needs, along with standard schemas |
|||
http://blog.braintraffic.com/2012/03/an-intro-to-metadata-and- |
|||
taxonomies/ |
|||
Administrative metadata includes things like date created or author. |
|||
They can sometimes include sub-elements about rights-management or |
|||
preservation. |
|||
Descriptive: These values describe aspects specific to each content |
|||
component, like title, subject, audience, and/or purpose. |
|||
The structural metadata gets identified as part of your system |
|||
requirements. Administrative and descriptive metadata are identified |
|||
during the creation or curation of specific content. I |
|||
If you think of it like a form, the structural metadata supports which |
|||
information needs to be collected (fields on the page), and the |
|||
descriptive and administrative metadata provide the values for those |
|||
form fields. |
|||
http://blog.braintraffic.com/2012/03/an-intro-to-metadata-and- |
|||
taxonomies/ |
|||
“controlled vocabularies” are nothing but taxonomies. Regardless of the |
|||
term, the underlying goals are to create some level of consistency and |
|||
control over the information used to describe a content component, and |
|||
clarify relationships between them. |
|||
Common types include: |
|||
Term list: A standardized list of terms created to insure consistent |
|||
tagging and indexing. Think of it as a list of “preferred language.” |
|||
Term lists typically provide a series of metadata values to pick from |
|||
for elements like format or content type. |
|||
Hierarchies: Often called a “taxonomy,” a hierarchy defines the |
|||
structural framework used to classify terms into parent/child or broad- |
|||
to-narrow relationships. Hierarchies are specifically used to support |
|||
layered groups of information and not simply for the convenience of |
|||
creating groupings—although each level of a hierarchy is commonly |
|||
referred to as a “category.” |
|||
Thesauri: A thesaurus translates conceptual relationships between the |
|||
content, often made naturally by humans, into something a computer can |
|||
understand. Thesauri typically address three types of relationships: |
|||
equivalent (synonyms), hierarchical (broad-to-narrow terms), and/or |
|||
associative (related terms). |
|||
At its simplest, a taxonomy organizes information, and metadata |
|||
describes it. For the taxonomy to be able to organize the information, |
|||
terms need to be stored as metadata. It all works together to make the |
|||
content findable, recognizable, and useful. |
Revision as of 16:49, 10 May 2013
Library cataloging and classification | |
---|---|
main topic | culture |
Dewey Decimal | 306 |
Universal Decimal | 008 |
http://www.hl7.org/implement/standards/fhir/v0.01/fhir-book.htm
Metadata as “information about the content that provides structure,
context, and meaning.”
Metadata is structured info that describes, explains, lcoates or
otherwise makes it easier to retrieve, use or manage info resource
Metadata represents a documented and orderderd summary of info that
describes something, in this case, spatial data. It provides the what,
where, when and why for spatial data
includes ownership and contact details and access and use conditions
DOeX provides precise specificaiton to enforce and ensure consistency
and interoperability. define and describe metadata entities and elements and classify and
group relevant metadata elements with entities assing structure and condition
Dublic core has 15 elements
9 mandatory
red - mandatory, green is optional
Metadata enables consistency, context, interoperability by facilitating
structured information exchanges.
Metadata is info about info objects, the content, the containers of info
objects.
Document
3 types of Metadata
Descriptive - enables context, defines content
adm - manage and enable consistency
date, category, make, origin
status, expiry date, content owner, access rights, Structural - composition of compound objects it enables interoperability
Name, first, last
Architecture
Presentation, storage, exchange
each side has a unique structure
Metadata Standards
X refers to it, y refers to it
XML standards enable exchanges; exchanges enable data linking,
What is defined by metadata standard
semantics means "bench"
Syntax is expression
If a capsium is a info object, a user is too
1. Make metadata a priority link metadata to ROI, reduce inefficiences create loyalty
2. Define your data, info objects, content assets, users, relationships,
1:1, 1:many, many:many
contextual inquires
discover what needs to be defined
Specify semantics, syntax, lexical rules
start with a controlled vocabulary
3. identify exchanges
internal and external
journey map
4. build the infrastructure start small, build on what exists
borrow and reuse
Example - Bool
title, author, year, subject, no of pages
MDT types
structural - describes relationship within a info objec t perservation -
What is an Element
Each info is describes using specific data items, these are called
elements
Metadata schema
set of MDT elements designed for a specific purpose such as describing
particular type of info
imposing restrictions and modifying vocabularies, we increase
interoperability with base standard
Element set
15 elements
All elements are optional and repeatable
elements can be refined using qualifiers any syntax may be used to refine metadata text based info objects
Core element set
title, type, format, identifier, owner, relation, date, description,
creator, contributor, rights
Element set
9 categories of elements are defined in Dublin
- elements may be repeated individually or as a group - valus and data type are defined for each element - they can be profiled to meet context specific needs
Values and DAta types
Value - restrictions on elements Eg: controlled vocabulary
Data types date and time length
DOeX categories (taxonomy)
Document types
structure
Definition of DO, examples, quality, reusable DO
DO
with appropariate MDT descriptions, they can be modular units that can
be assembled together to allow exchange
Text is used to be talking about DOs
OAI-ORE standard for exchange of aggregations
Type 1 - internal entity (content repository), Type 2 - only links to
DOs (linking or MDT repos), Type 3 - links to DO and internal entities
(hybrids)
Usages - Functions
maintain - version control
retrieve - receive an object that has been requested
submit - provide an object to repository for storage
publish - provide metadata to other repositories
store - place a DO into the store with unique id that allow it to be
lcoated gahter, - push/pull: obtain metadata about objects in other repositories
for wider searches and information via a clearing house function
three main types of metadata:
Structural: Defines the metadata elements that need to be collected;
labels like title, author, date created, subject, purpose, etc. Defining
these structural elements is typically based on a mix of organizational
and system needs, along with standard schemas
http://blog.braintraffic.com/2012/03/an-intro-to-metadata-and-
taxonomies/
Administrative metadata includes things like date created or author.
They can sometimes include sub-elements about rights-management or
preservation.
Descriptive: These values describe aspects specific to each content
component, like title, subject, audience, and/or purpose.
The structural metadata gets identified as part of your system
requirements. Administrative and descriptive metadata are identified
during the creation or curation of specific content. I
If you think of it like a form, the structural metadata supports which
information needs to be collected (fields on the page), and the
descriptive and administrative metadata provide the values for those
form fields.
http://blog.braintraffic.com/2012/03/an-intro-to-metadata-and-
taxonomies/
“controlled vocabularies” are nothing but taxonomies. Regardless of the
term, the underlying goals are to create some level of consistency and
control over the information used to describe a content component, and
clarify relationships between them.
Common types include:
Term list: A standardized list of terms created to insure consistent
tagging and indexing. Think of it as a list of “preferred language.”
Term lists typically provide a series of metadata values to pick from
for elements like format or content type.
Hierarchies: Often called a “taxonomy,” a hierarchy defines the
structural framework used to classify terms into parent/child or broad-
to-narrow relationships. Hierarchies are specifically used to support
layered groups of information and not simply for the convenience of
creating groupings—although each level of a hierarchy is commonly
referred to as a “category.”
Thesauri: A thesaurus translates conceptual relationships between the
content, often made naturally by humans, into something a computer can
understand. Thesauri typically address three types of relationships:
equivalent (synonyms), hierarchical (broad-to-narrow terms), and/or
associative (related terms).
At its simplest, a taxonomy organizes information, and metadata
describes it. For the taxonomy to be able to organize the information,
terms need to be stored as metadata. It all works together to make the
content findable, recognizable, and useful.
Subcategories
This category has the following 49 subcategories, out of 49 total.
+
A
C
E
F
G
H
I
L
M
O
P
S
V
Σ
Pages in category "Culture"
The following 50 pages are in this category, out of 50 total. This list may not reflect recent changes.
C
- Classic
- Coloured hat
- Criminal tradition
- Critical consumerism
- Cultural deprivation
- Cultural emphasis
- Cultural framework
- Cultural issues
- Cultural lag
- Cultural manager
- Cultural movement
- Cultural narcissism
- Cultural nationalism
- Cultural retention
- Cultural universal
- Culture and social cognition
- Culture hero
- Culture of life