Metadata (Coursera, Fall 2013) - Revision history

Wtrettien: /* Unit 4: Alphabet Soup */

2014-02-16T15:43:16Z

Unit 4: Alphabet Soup

← Older revision		Revision as of 15:43, 16 February 2014
Line 260:		Line 260:

	provenance: record describing entities and processes involved in producing and delivering that resource		provenance: record describing entities and processes involved in producing and delivering that resource

			OPM: Open Provenance Model

			METS: Metadata Encoding and Transmission Standard; metadata about metadata

			crosswalks: translate between metadata schemas

	== Unit 5: Metadata for the Web ==		== Unit 5: Metadata for the Web ==

Wtrettien: /* Unit 3: How to Build a Metadata Schema */

2014-02-16T15:39:05Z

Unit 3: How to Build a Metadata Schema

← Older revision		Revision as of 15:39, 16 February 2014
Line 236:		Line 236:

	XML --> RDF --> DTDs & Namespaces --> Metadata schemes		XML --> RDF --> DTDs & Namespaces --> Metadata schemes

			== Unit 4: Alphabet Soup ==

			descriptive metadata

			structural & administrative metadata

			crosswalks

			descriptive example:

			Categories for Description of Works of Art (CDWA)

			EXIF

			administrative metadata:

			PREMIS; core set of elements for the preservation of digital objects

			preservation metadata is "the information a repository uses to support the digital preservation process"; requires viability, renderability, understandability, authenticity, identity

			PREMIS doesn't describe intellectual entities, but objects that instantiate them

			provenance: record describing entities and processes involved in producing and delivering that resource

			== Unit 5: Metadata for the Web ==

Wtrettien: /* Unit 3: How to Build a Metadata Schema */

2014-01-19T02:05:35Z

Unit 3: How to Build a Metadata Schema

← Older revision		Revision as of 02:05, 19 January 2014
Line 234:		Line 234:

	HTML is for human consumption; goal of semantic web is enable automated algorithms to sort material		HTML is for human consumption; goal of semantic web is enable automated algorithms to sort material

			XML --> RDF --> DTDs & Namespaces --> Metadata schemes

Wtrettien: /* Unit 2: Dublin Core */

2014-01-19T02:02:33Z

Unit 2: Dublin Core

← Older revision		Revision as of 02:02, 19 January 2014
Line 164:		Line 164:
	* level 4: shared formal vocabularies and constraints in records		* level 4: shared formal vocabularies and constraints in records
	* each level leans more heavily on RDF -- more readable by machines, less readable by humans		* each level leans more heavily on RDF -- more readable by machines, less readable by humans

			== Unit 3: How to Build a Metadata Schema ==

			eXtensible Markup Language

			Document Type Definition (DTD)

			Resource Description Framework (RDF)

			HTML in XML --> XHTML

			HTML is metadata, in that it describes the formatting of the page

			XML provides information about the structure of the document -- gives metadata about the content

			XML, like DC, made up of elements and values

			elements can have child elements -- data structure is a tree

			elements can have attributes -- so that child elements become attributes of parent

			e.g.: <ingredient><fooditem="milk"></fooditem></ingredient> vs. <ingredient fooditem="milk"></ingredient>

			in HTML, all elements and attributes are predefined; in XML, you can create any elements or attributes you want

			thus, must create a DTD to declare elements and attributes

			<?xml version="1.0" encoding="UTF-8"?>

			possible to put DTD in XML file itself, however usually you'll be using a schema that already exists, so you point elsewhere to its DTD

			child elements declared at top usually, parent at bottom

			<!ELEMENT recipe (child elements, child elements,)>

			? = 0 or 1
			* = 0+
			+ = 1+

			#PCDATA -- parsed character data; any block of text can be used

			HTML5 does not have a DTD

			entity declaration ex. -- <!ENTITY % fontstyle
			"TT \| I \| B \| BIG \| SMALL">

			attribut list -- <!ATTLIST

			CDATA -- character data

			RDF -- Resource Description Framework; data model for describing resources

			resource: anything with an address on a network

			descriptive metadata is made up of statements describing the object or resource

			triple: subject (value) - predicate - object (resource); e.g. leonardo da vinci - creator - Mona Lisa painting

			can create complex networks of triples

			RDF file:
			declare xml; declare rdf and two namespaces; describe object

			RDFS: RDF syntax

			DC doesn't care what your container element is

			prefix:element; e.g. "dc:subject"

			HTML is for human consumption; goal of semantic web is enable automated algorithms to sort material

Wtrettien: /* Unit 2: Dublin Core */

2014-01-18T21:36:04Z

Unit 2: Dublin Core

← Older revision		Revision as of 21:36, 18 January 2014
Line 157:		Line 157:

	Namespace -- conceptual space in which a set of identifiers are defined		Namespace -- conceptual space in which a set of identifiers are defined

			four levels of interoperability
			* level 1: use shared term definitions
			* level 2: use shared vocabularies based on formal semantics -- implicit or explicit use of RDF
			* level 3: use shared formal vocbularies in exchangeable records
			* level 4: shared formal vocabularies and constraints in records
			* each level leans more heavily on RDF -- more readable by machines, less readable by humans

Wtrettien: /* Unit 1: Organizing Information */

2014-01-18T21:30:39Z

Unit 1: Organizing Information

← Older revision		Revision as of 21:30, 18 January 2014
Line 97:		Line 97:

	Gregory Bateson, information is "a difference that makes a difference"		Gregory Bateson, information is "a difference that makes a difference"

			== Unit 2: Dublin Core ==

	Dublin Core; named after Dublin, OH, where OCLC is; first developed in 1995; developed to be simple and have a low cost of adoption		Dublin Core; named after Dublin, OH, where OCLC is; first developed in 1995; developed to be simple and have a low cost of adoption

Wtrettien: /* Unit 1: Organizing Information */

2014-01-18T21:29:58Z

Unit 1: Organizing Information

← Older revision		Revision as of 21:29, 18 January 2014
Line 97:		Line 97:

	Gregory Bateson, information is "a difference that makes a difference"		Gregory Bateson, information is "a difference that makes a difference"

			Dublin Core; named after Dublin, OH, where OCLC is; first developed in 1995; developed to be simple and have a low cost of adoption

			goals: simple, shared semantics, extensible, international

			characteristics of a DC record: all elements are option; all elements are repeatable; elements may be displayed in any order

			15 elements of DC:
			* contributor
			* coverage
			* creator
			* date
			* description
			* format
			* identifier
			* language
			* publisher
			* relation
			* rights
			* source
			* subject
			* title
			* type

			elements: category of statement (like 'creator'); also "field"

			value: data provided in the statement (like 'William Shakespeare')

			record: set of element-value pairs

			metadata scheme: controls the kinds of statements you can make; it is a "formally efined set of metadata elements. The meaning (semantics) of the elements are pre-defined, constraining the kinds of statements that can be made about a resource."

			principles of DC:
			* "dumb-down principle": if an element is not relevant, don't use it
			* "one-to-one": one record per object

			HTML "meta" tag: name = element, content = value

			"DC.element", i.e. "DC.creator" -- standard method of representing DC metadata in meta tag in HTML

			qualified DC -- modifying; through element refinement (adding "created" to date -- dc.date.created) or encoding schemes (add "scheme" to meta tag; i.e. name="dc.subject scheme="MESH" content="Posterior Eye Segment")

			DCMI communities: working on extending DC for their schemas

			terms -- expand on the basic 15 core elements

			DCMI Abstract Model
			* independent of any particular encoding syntax
			* shows all the things needed to be included in any metadata scheme
			* i.e. written to be generic model, but is model upon which DC is built
			* resource model
			** diamond arrows, "has a," regular triangle arrow, "is a," line arrow, "described using"
			** property-value pair has both property (element) and value, which can be literal and/or non-literal
			* element-value or property-value pairs make up a statement
			* how resources are described; description is encoded in a vocabulary; how terms in a vocabulary are encoded
			* models are way of determining basic ontological categories that can be used for ny metadata schemes

			Namespace -- conceptual space in which a set of identifiers are defined

Wtrettien: /* Unit 1 */

2014-01-16T03:02:46Z

Unit 1

@@ Line 5: / Line 5: @@
 https://class.coursera.org/metadata-001
-== Unit 1 ==
+== Unit 1: Organizing Information ==
 metadata -- "data about data"; description
 world divided into natural and artificial objects; physical and digital

Wtrettien: Created page with 'Metadata Coursera Taught by Jeffery Pomerantz https://class.coursera.org/metadata-001 == Unit 1 == metadata -- "data about data"; description world divided into natural and a…'

2014-01-14T14:09:18Z

Created page with 'Metadata Coursera Taught by Jeffery Pomerantz https://class.coursera.org/metadata-001 == Unit 1 == metadata -- "data about data"; description world divided into natural and a…'

New page

Metadata
Coursera
Taught by Jeffery Pomerantz

https://class.coursera.org/metadata-001

== Unit 1 ==

metadata -- "data about data"; description

world divided into natural and artificial objects; physical and digital