3.20.08 in-class

metadata-interoperability-crosswalks

http://www.niso.org/framework/Framework2.pdf

NISO’s Understanding Metadata: A really good resource

http://www.niso.org/standards/resources/UnderstandingMetadata.pdf

CROSSWALK:

“A crosswalk allows metadata
created by one community to be
used by another group that employs
a different metadata standard.”

Not everyone is following standards. Information is structured to meet specific users, so metadata schemes reflect those differences.

Many people agree on the standards of dublin core.

What is my point and how will I fulfill my mandate in this metadata chaos?

Follow a standards (MARC) and fund a system, a technology that will store it and provide an interface for users.

OPAC: online public access catalogs: + – $500,000 to purchase, $50,000/yr to maintain.

Eastman House uses TMS system.

INTEROPERABILITY = Different systems can communicate and share information. They do this by utilizing crosswalks. Crosswalks are multi-lingual.

Metadata can either be encoded within the object itself or outside it like in a MARC record.

Union catalogs, union databases= info that works together because the common information like a title has been identified in each metadata scheme. So a crosswalk unifies TITLE in MARC, Dublin Core etc., and links it.

CROSSWALK con’t.: Map a proprietary archive to Dublin Core. Map title, date, dimensions etc. = migrating data to a new platforms and develop an interface so that people can use it.

Data Conversion= big issue for most disciplines today.

LOC MARC mappings/ crosswalks:

http://www.loc.gov/marc/marcdocz.html

MARC=$aAuthors, American$y20th century$xPortraits.

DUBLIN CORE=Authors, American — 20th century — Portraits

Library of Congress cataloging tools and NISO

Cataloging Tools Produced by the Prints and Photographs Division of the Library of Congress

http://www.loc.gov/rr/print/cataloging.html

A Framework of Guidance for Building Good Digital Collections

Common Elements for Description & Cataloging

http://www.niso.org/framework/framework2.html

-Creator and Context

-Identity

-Content and Structure

-Access and Use

-Acquisition and Appraisal

-Related Materials

-General Notes

-Control of Desctription

Useful Description of Pictorial Materials

• Use a word that describes a broad type of material, such as ‘pictures’
• State the physical media/format and quantity
• Express the subject and specific work type, media or genre
• Favor names of creators
• Undertake rights statements
• Link to digital reproductions

NISO: National Information Standards Organization

http://www.niso.org/framework/framework2.html

A Framework of Guidance for Building Good Digital Collections

The Framework is organized around indicators of goodness for four core entities:
• Collections (organized groups of objects)

• Objects (digital materials)

• Metadata (information related to objects)

• Projects (initiatives to create or manage collections)

Collections principle 1: A good digital collection is created according to an explicit collection development policy that has been agreed upon and documented before digitization begins.

Collections principle 2: Collections should be described so that a user can discover characteristics of the collection, including scope, format, restrictions on access, ownership, and any information significant for determining the collection’s authenticity, integrity, and interpretation.

Collections principle 3: A collection should be sustainable over time.

Collections principle 4: A good collection is broadly available and avoids unnecessary impediments to use.

Collections principle 5: A good collection respects intellectual property rights.

Some tools supporting interoperability include:
• Dublin Core Metadata Initiative. In addition to the element set, DCMI is developing registries for metadata interoperability.

Digital Objects
Objects principle 1: A good digital object will be produced in a way that ensures it supports collection priorities, while maintaining qualities contributing to interoperability and reusability.

Objects principle 2: A good object is persistent. That is, it will be the intention of some known individual or institution that the good object will remain accessible over time despite changing technologies.

Objects principle 3: A good object is digitized in a format that supports intended current and likely future use or that supports the derivation of access copies that support those uses.

Objects principle 4: A good object will be named with a persistent, unique identifier that conforms to a well-documented scheme.

Objects principle 5: A good object can be authenticated in at least three senses. First, a user should be able to determine the object’s origins, structure, and developmental history (version, etc.). Second, a user should be able to determine that the object is what it purports to be. Third, a user should be able to determine that the object has not been corrupted or changed in an unauthorized way.

Objects principle 6: A good object will have associated metadata.

METADATA

Metadata Principle 1: Good metadata should be appropriate to the materials in the collection, users of the collection, and intended, current, and likely future use of the digital object.

Metadata principle 2: Good metadata supports interoperability.

Metadata principle 3. Good metadata uses authority control and content standards such as controlled vocabularies that are in line with user expectations to describe the content of objects and collocate related objects.

Metadata principle 4. Good metadata includes a clear statement on the conditions and terms of use for the digital object.

Metadata principle 5: Good metadata supports the long-term management of objects in collections.

Metadata principle 6: Good metadata records are objects themselves and therefore should have the qualities of good objects, including authority, authenticity, archivability, persistence, and unique identification.

3/13: create a database

dreamweaver siteinClass2yes server – php sqlfiles where: data (d drive)new folder : give a name inClass2

and open it ( select)

edit locally

ftp

ftp.imagearts.ryerson.ca

ppcm/username/inClass2

username

password

http://www.imagearts.ryerson.ca/ahackman/inClass2/

go to the beginning: write the same thing

and say no to the last one., click done

right click to site-inclass2

new folder

inclass 2 – drop down list

manage sites

edit – advanced

select images click done

take images from inclass2 (weston) to data d …

you should have them in your dreamweaver .. 3 photos

we are going to make 2 pages.

insert data into our database

(small application)

other page : use the images on database

right clik – new file .php

insert.php

change the title – untitled document

its easily overlooked

web http.

php

rdms my sql

they talk to each other- they are all connected

web server only speaks HTML

php server only speaks php

rdms server only speaks sql

.php – dont even try to read it as html

send it to php

create a database connection

myConnection

localhost

serdem

password (7 digits)

click ok, and click your username

write insert new images

twice enter

format heading 3

forms – click the first square

text field – second one to the square

filename

Enter Filename:

enter category

enter caption

captio : delete the label

go to textarea , write caption

2 more buttons

to submit button

to reset button

button (up)

write submit

write reset ( go to reset form)

down – form#form1 – select the form ( selects altogether)

application – server behaviours

plus signt _ drop sign -

insert record

click my connection

after inserting go to : insert.php

http://www.imagearts.ryerson.ca/ahackman/inClass2/insert.php

put all the folder names – click submit

http://www.imagearts.ryerson.ca/ahackman/phpmyadmin/

ahackman – inclass2 – browse

new file – viewall.php

table

4 coloumns 1

bindings

recordset

drag filename, category, caption and id

upload the viewall – say yes

erase recordset

tree sign – pope001

data sources

url : images/

click on table

go to server behaviour

repeat regions , all regions

Database Building

Database Structures

R.D.M.S. = Relational Database Management Systems

(can access relational info from various tables)

D.B.2 = Big, expensive
ORACLE = Big, expensive
SQllite = free
mySQL = free = what we’re using

SQL = Structrured Query Language

SQL = Language used to ask questions

ORACLE/mySQL etc. translates info slightly different.

SQL Command to create database is

Create Database (andrea_database )

Column = Field
Row = Record

Field names cannot have spaces.

Every Record in a Db has to be completely unique.

Must have a mechanism to make sure Db records are unique.
(accession number)

Most common DATA TYPES:

PRIMARY KEY: generates unique # for records.

End of primary key # should always be ID therefore you always know what the primary key # is.

Primary Key type is almost always INT (integer/whole number).

VARCHAR = Variable Character Length = allows you to keep the size of memory set aside to a minimum.
ex. VARCHAR 30 (store characters up to the # 30) Maximum VARCHAR for mySQL is 255.
If you need more characters than 255, use TEXT or BLOB. BLOB is for more text/info.

Salary = FLOAT = Floating point #; #’s with a decimal.

DATE =

NAMING CONVENTIONS:
Name of Database/ Field/ Table

Rule #1: Make the name as descriptive as possible: explicitly state what they contain.

Rule #2: For 2 word field: lowerCase firstWord, upperCase secondWord   firstNameHere

Head First SQL: Chapter 1-4 & 7

A database is a container that holds tables and other SQl structures related to those tables.

The information inside the database in organized into tables.

Tables are organized as columns and rows.
Column = Value (Last name)
Row = Information (Hackman)

This is all about setting up queries and making info searchable.

CREATE TABLE in all caps table_name lowercase.

(
last_name VARCHAR (variable character) (up to 30 characters long).
email VARCHAR (50),
birthday DATE,
profession VARCHAR (50),
);

The Select statement: how to narrow down your query.Type in where command:WHERE first_name = ‘Anne’;

* commant tells RDBMS to give back values from all the columns in the table.

VARCHAR, CHAR, BLOB, DATE and TIME data types need single quotes. The numerical types, DEC and INT don’t.

makes sense, will make more sense once we start creating tables.

Operators to use :  = <> <  > <=  >=

IS NULL: Use this to create a condition to test for NULL value.

AND and OR: With AND and OR, you can combine you condistional statements in your WHERE clauses for more precision.

NOT: NOT lets you negate your results and get the opposite values.

DELETE: This is the tool fo deleting rows of data from the table. Use it with a WHERE clause to precisely pinpoint the rows you want to remove.

UPDATE: Updates an existing column or columns with a new value. It also uses a WHERE clause.

SET: This keyword belongs in an UPDATE statement and is used to change the value of an existing column.

ATOMIC DATA: Data in your columns is atomic if  it’s been broken down into the smallest pieces that you need.

Atomic Data Rule 1: It can’t have the same data in the same column.

Atomic Data Rule 2: can’t have multiple columns with the same type of data.

SHOW CREATE TABLE: command to see the correct syntax for creating an existing table.

FIRST NORMAL FORM (1NF): Each row of data must contain atomic values, and each row of data must have a unique identifier.

PRIMARY KEY: A column or set of columns that uniquely identifies a row of data in a table.

AUTO_INCREMENT: When used in your column declaration, that column will automatically be given a unique interger value each time an INSERT is performed.

Transitive functional dependency: This means any non-key column is related to any of the other non-key columns.

Schema: A description of the data in your database.

One-to-one relationship: Exactly one row of a parent table is related to one row of a child table.

One-to-many relationship:  Two tables are connected by a junction table, allowing many rows in the first to match many rows in the second, and vice versa.

Second Normal Form (2NF): Your table must be in INF and contain no partial functional dependencies to be in 2NF.

Third Normal Form (3NF): Your table must be in 2NF and have no transitive dependencies.

Foreign Key: Your table must be in 2NF and have no transitive dependencies.

Composite Key: This is a primary key made up of multiple columns, which create a unique key value.

Valentines Day in-class notes

leaves= one side

pages= two sides

Subject Headings: authorities.loc.gov : maximum of 6, really 3-4: Be specific, full with records.

Subdivisions:
1. Topical go in subfield X
2. Geographic go in subfield Z: Maximum of 2, and for U.S. and Canada use state then city, every other country is country then city.
3. Chronological go in subfield Y
4. Form go in subfield V: What it IS (statistics, index bibliography)

LoC Classification

http://www.loc.gov/catdir/cpso/lcco/

Photography is TR: this goes in 050 subfield a. The call# matches the first subject heading.

050 $aTR147$b.H33 2008

$aTR147$b.G76 2008

In class: MARC Fields con’t.

260: publication, distribution

example:

260 ## $a New York :
$b Chelsea House,
$c 1986.

If you don’t know the date, guess. [1980?] information that is added or guessed, not from chief source, is in BRACKETS [ ]. You don’t have to guess subfields a or b, just c.

300: Physical description

300 $avi, 200 p. (this means that there are 6 roman numeral pages in front and 200 #’d pages )
300$a150 p.
300 $a200, [5] p.

leaves are single sided pages, plates are tipped-in images (unnumbered leaves within an item)

$c length of spine, rounded to nearest centimeter.

440 Series

$a–Title
$v–Volume #

500 General Notes

504 Bibliographies, Index

505 & 520 (always have)

600 Subjects (what is this work about) examples: Established forms of personal names (if person is the subject)

650 use authority file to establish subject
BT–Broad Term
NT–Narrower Term
UF–Used For
USE–Use (use this form instead of what you were using…)

Readings: Chapters 1-3 of Introduction to Vocabularies and handouts from SCM: Subject Headings

I. Chapters 1-3 of Introduction to Vocabularies

1. What is Art and Material Culture Information, and Why is it Important?
This chapter emphasises how text, research and documentation enhances the value (educational and financial) of art.

2. Documentation: Analyzing and Recording Information
There are 4 major approaches to documentation of art and material culture.
1. THE ARCHIVAL APPROACH
            Involves the arrangement and description of records, personal papers, and manuscripts.
        2. THE LIBRARY APPROACH
Involves the cataloging and classification of books and other published textual materials.
3. THE MUSEUM APPROACH
            Involves the documentation of museum objects (e.g., works of art, artifacts, and specimens).
4. THE VISUAL RESOURCES APPROACH
Involves the cataloging, classification, and indexing of images.
3. Standards: What Role Do They Play?
STANDARDS are mutually agreed upon statements that help to control an action or product. They represent professional consensus on best practice. These standards will be useful once I actually need them in the workplace. Right now they are just lists.  The benefits of standards are that they improve the quality and consistency of information, improve compatibility of information structures, protect the long-term value of data and facilitate information retrieval.

II. Handouts from SCM: Subject Headings 

In lieu of Taking notes on constructing subject headings, I will try to create a MARC record of one of my assigned books.

LC Control No.: 98075091
035 __ |9 (DLC) 98075091
010 __ |a 98075091
020 __ |a 0914630210 (pbk.)
040 __ |a DLC |c DLC

245 00 |a Six exposures: : |b essays in celebration of the opening of the Harrison D. Horblit collection of early photography.
260 __ |a Cambridge : |b The Houghton Library, Harvard University, |c 1999.

week 4 Lecture: Cataloging with AACR2R and MARC21

Making MARC Records

Copy cataloging: finding a record previously made and using its codes. Go through record field by field and make sure records are right/current. ie: http://catalog.loc.gov

Anglo-American-Cataloging-Rules AACR2 over /antiquated is now RDA (Resource Description and Access)

RDA=The new content standard: a standardized way of cataloging content. RDA creates the same MARC records but presents it differently.

Access points= subject index (author, title, subject) (Title page contains cataloging info.)

• How do you form access points?
  

• How should info be indexed/what form of subject heading should you use?

AACR2
In cataloging there are 8 main areas of description. They are based on:

International
Standard
Book
Description

1. Consider publication: is it a Monograph? Series?
2. Title Page is the usual Chief Source of Information (spine, cover could suffice).
3. If no title/chief source, put the title I choose in square brackets
ie: [Rock Climbing for Dummies] (title is field 245 in MARC records)

4. Punctuation in AACR2 is case sensitive

… = “I left some stuff out here” / = precedes statement of responsibility (author) [ ] = record maker made it up.

MARC is how AACR2 information is electronically recorded

1. Title statement in MARC #245

• (statement of responsibility is a transcription of authors name from title page and is always used in MARC title statement with a / )
• Indicator 1= 1=Main entry is the author name, 0=Title is the main entry, no author given ie: no 100 MARC field entry.
• Indicator 2= NONFILING CHARACTERS ie: THE in title, don’t want to use THE in title catalog. 0-9 nonfiling character #’s: THE has four (three letters plus the space) A is represented by the number 2
• … in title replaced with -
• Transcribe title wording, order, spelling but not necessarily punctuation
• Subfield A (in MARC)= $aThe photographic history (do not capitalize all words, even if on title page; First letter and proper names get capitalized)
• Subfield C = $cLarry J. Whatever

2. Practice

• 245 00 $aSix exposures
  $bessays in celebration of the opening of the Harrison D. Horblit collection of early photography.

3. Always have a 520 (summary or abstract with useful key words) or 505 (table of contents) entry. Do only one of these options, unless they have totally diff information

4. MARC biblographic page gives a list of all the MARC fields:
020= LOC ISBN entry field

5. 100 is established form of person’s name; Main Entry. Editors do NOT go in 100; title is therefore main entry; editors go in 700.

6. 250 Edition Statement
Editions are always abbreviated ie: $a6th ed.

http://www.loc.gov/marc/bibliographic/ecbdnumb.html#mrcb010

homework reading:

http://www.loc.gov/marc/umb/

Readings: Understanding MARC Bibliographic and AACR2 chapters

I. Understanding MARC Bibliographic

What is a MARC record?

• A MARC record is a MA chine-Readable Cataloging record.
  • “Machine-readable” means that one particular type of machine, a computer, can read and interpret the data in the cataloging record.
  • Librarians follow the rules in Anglo-American Cataloguing Rules, 2nd ed.,(AACR2) 2002 revision to compose the bibliographic description of a library item.
    • This “description” is shown in the paragraph sections of a card. It includes the title, statement of responsibility, edition, material specific details, publication information, physical description, series, notes, and standard numbers.
    • POINTS OF ACCESS: Rules in AACR2 are used to answer questions such as: For this book, should there be entries in the catalog for more than one author or more than one title? Should the title of the series be noted? How should the author’s name be written? Is this a “title main entry” item (no author)?
    • Subject headings: Library of Congress Subject Headings (LCSH), or another standard subject headings list to select the subjects under which the item will be listed. Use of an approved list is important for consistency.

• MARC Code The MARC 21 format uses “260″ “$a” “$b” and “$c” to mark the field that holds imprint data instead of storing the words “publication area,” “place of publication,” “name of publisher,” and “date of publication” in each record. This convention makes more efficient use of computer storage space.

FIELDS are marked by TAGS.

Field: Each bibliographic record is divided logically into fields. There is a field for the author, etc.
Tag: Each field is associated with a 3-digit number called a “tag.” A tag identifies the field — the kind of data — that follows.

1. EXAMPLE: The tags used most frequently are:
   10 tag marks the Library of Congress Control Number (LCCN)
   020 tag marks the International Standard Book Number (ISBN)
   100 tag marks a personal name main entry (author)
   245 tag marks the title information (which includes the title, other title information, and the statement of responsibility)
   250 tag marks the edition
   260 tag marks the publication information
   300 tag marks the physical description (often referred to as the “collation” when describing books)
   440 tag marks the series statement/added entry
   520 tag marks the annotation or summary note
   650 tag marks a topical subject heading
   700 tag marks a personal name added entry (joint author, editor, or illustrator)

EXAMPLE ENTRY: 100 1# $a Pirsig, Robert M.

Some fields are further defined by INDICATORS

• Indicators: Two character positions follow each tag (with the exception of Fields 001 through 009)
• It is the convention to represent a blank, or undefined, indicator position by the character “#”.
  • EXAMPLE: 245 14 $a The emperor’s new clothes / $c adapted from Hans Christian Andersen and illustrated by Janet Stevens.

Some fields are further defined by SUBFIELDS

• Subfield: Most fields contain several related pieces of data. Each type of data within the field is called a subfield, and each subfield is preceded by a subfield code. Fields 001 through 009 have no subfields.
• Subfield codes are one lowercase letter (occasionally a number) preceded by a delimiter. A delimiter is a character used to separate subfields. ($)
  • EXAMPLE: 300 ## $a 675 p. : $b ill. ; $c 24 cm.

Most of the access points are in:
1XX fields (main entries)
4XX fields (series statements)
6XX fields (subject headings)
7XX fields (added entries other than subject or series)
8XX fields (series added entries)

II. AACR2 chapters

It is hard to comment on the AACR2 (Anglo-American-Cataloging-Rules) chapters since this is a guide / tool that is used while creating MARC records. It seems to be very useful and thorough, and I’m sure will be helpful once I actually create these records. It’s good to note that AACR2 is very specific when concerning punctuation and wording, as this helps streamline metadata records across institutions.