The semester has come to an end and the final project produced for this class is up and running… Well, it’s still a work in progress, but it’s on the way to being a fully functioning picture database.

www.imagearts.ryerson.ca/jsheptytskyzall/CathNewTimes/index.html

View in Firefox or Safari

The site is simple, and set up to offer a few basic details about the project.
The navigation structure is as follows:
Home – identifies the site’s purpose
Blog – link to this blog
Database (maybe a bit of a misnomer, as it was meant to contain the search function) – instead, the page contains the form used to input information into the database.
Collection – displays all the images in the database in sequential order. Previous/Next buttons are available on the bottom of each record.
Links- offers a few links to museums of interest. This section will be significantly expanded to include a long list of bookmarks which I’ve been compiling over the year.
Contact – a way to reach me
The last, blank square functions as a button from the home page only and links to a basic author query.

The database is designed specifically for the Catholic New Times images, but can likely be applied to any collection of a similar nature; containing a variety of subject matter but from a consistent production source, like press images.

The field definitions were taken from a number of sources, including the Getty, Library of Congress and Dublin Core.

The database fields are as follows:
Image Title
Creator/Author
Alternate Author Date – specified to be input in (mm-dd-yyyy) format
Medium – User can choose between: Photograph and other. This is in order to limit input of objects not specific to the collection. Everything which is not a photograph, such as a caption note or clipping would be classified in other and further reviewed for its inclusion in the database.
Process- The user can choose between RC and Fibre Gelatin Silver or Digital print. Again this is specific to the content of the collection as it would not contain other historical material. An Other field allows the cataloguer to input unidentified prints or reproductions. This field could be omitted entirely, however it may be of useful for identifying preservation concerns of certain materials.
Caption
Caption Verso
The user is prompted to use LC Authorities to identify subjects.
Subject – Person
Subject – Place
Subject – Topic
Inscription Recto
Inscription Verso
Both of these fields can be used to identify any important markings on the image.
Size The size properties are broken down to image size and paper size. This is important if an image is to be displayed or housed. The unit of measurement, mm is a choice specific to the medium. The Getty suggests choosing an appropriate unit and keeping it uniform, mm are often used for photographs.
Image Height (mm)
Image Width (mm)
Paper Height (mm)
Paper Width (mm)

There is one other field that should potentially be included, however we did not address it in class. The database does assign a unique ID number to each record, but it the collection being catalogued already has a numbering system in place, such as accession numbers, this would be included. Other fields may include the item location or notes, which would address this type of information.

NISO – National Informational Standards Organization

A Framework of Guidance for Buiilding Good Digital Collections
http://www.niso.org/framework/Framework2.pdf

NISO – Understanding Metadata
http://www.niso.org/standards/resources/UnderstandingMetadata.pdf

World Library Index – 18000 libraries
http://www.libdex.com/
 (opac – online public access catalogue) 

There is a large number of systems used by different institutions to compile data and make it accessible.
Interoperability – the ability of different database systems to communicate, by means of crosswalks. (like a translation)

Crosswalks – a means of transfering data from one system to another, like MARC to DublinCore.
http://www.ncecho.org/ncdc/template.html
In Class assignment – MARC to Dublin Core 

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 Principles
1. A good digital collection is created according to an explicit collection development policy that has been agreed upon and documented before digitization begins.
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.
3. A collection should be sustainable over time.
4. A good collection is broadly available and avoids unnecessary impediments to use.
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 Principles
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.
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.
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.
4. A good object will be named with a persistent, unique identifier that conforms to a well-documented scheme.
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.
6. A good object will have associated metadata.

Metadata Principles
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.
2. Good metadata supports interoperability.
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.
4. Good metadata includes a clear statement on the conditions and terms of use for the digital object.
5. Good metadata supports the long-term management of objects in collections.
6. Good metadata records are objects themselves and therefore should have the qualities of good objects, including authority, authenticity, archivability, persistence, and unique identification.

Creating a Database

1. www.imagearts.ryerson.ca/jsheptytskyzall/phpmyadmin/

2. Sign In

3. Select a database or Create a new one

4. Create a Table (bottom of the page) + number of fields (Dublin Core 15 + primary key) 

5. Assign Fields
   1. Primary Key - tablename_ID (INT) Extra (autoincrement) select first bullet button to assign primary key.
   2. Author – CHAR/Varchar (max 255 including spaces) Null (not null indicates that the field must have input. Null for author because there may not be one.)
   3. Title – TEXT
   4. Date - DATE (because date formats vary, VARCHAR (30) can be used to include such variations ei. c 1890, year only etc. DATE can perform calculation but has a set format)

A supplementary field can be added to include only year (intYear for example) INT, if calculations are nessesary. 

   5. Medium – VARCHAR (30) set length at the maximum of the longest option
   6. Content/Caption –  TEXT (no value)
   7. altAuthor – VARCHAR (100)
   8. subjectPerson – VARCHAR (100) null
   9. subjectTopic – VARCHAR (100) null
   10. subjectCorporation – VARCHAR (100) null
   11. Place/Location – TEXT Use authoritative name
   12. etc.

6. Save – check SQL query, red will signify problems.

Can Edit fields and Insert date directly in SQL

DREAMWEAVER

New Site
Yes. Server Technilogy – mySQL
Edit locally, then upload. Select/Create folder.
No check IN/OUT.

  create image folder
   go back to edit sites/ advanced/ local info/ set image folder/ done
   create new file/ insert.php

      create a form on the page – text entry fields, get from Applications/+ MySQL Connections/
      Connection Name: whatever
      My SQL Server : localhost (almost always)
      Username/Password
      Database – select (should be the one created in phpmyadmin)

Golden drum should appear

shared connections
tables (only this one is of relevance)
   + sitename
      + fields
views

On insert.php
   insert form
     - insert field
          Input Tag Accessebility Window
          ID – Field Name
          Label – User prompt
          insert all fields in table + add submit and reset buttons

Applications -Database – Insert Record

New File – view.php

Applications – Bindings + Recordset
         Connection – define
         Table – choose appropriate table
         Columns: All
         Filter: none
         Sort: Filename - Assending

Back to the file view.php
     Create a table – first row – add image
                              – select image source – data sources – select
    Image Tag Accessibility Attributes – Alt text (….) – Long description (none)

-remaining fields can be draged and dropped from Recordset
Check in browser

Back to the file
– select the table
Application – Server Behaviour + Repeat region
Repeat Region – Recordset
Show – alll records
(grey square will appear around the repeat region.
Save – Upload – Check in Browser
     

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

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

- Common and Useful Information Elements for Cataloging Pictorial Materials

For further reference see post for March 17th, 2008

A Framework of Guidance for Building Good Digital Collections

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

METADATA

 

Questions to consider include, but are not limited to: 

Purpose of the digital collection

- What are the goals and objectives for building this collection?

User needs & intended usage

Metadata standard selection & usage

- Does the collection or its items have metadata before the digital collection is built?

 

 How useful are existing metadata for collection control, management, and access?

What is the format of the original resources?>

How rich of a description is needed and does the metadata need to convey?

How will you distinguish between the source object and the digital surrogate available?

 

Dublin Core

http://dublincore.org/ 

For further reference see post for March 17th, 2008

RDMS – Relational Database Management System
ex.
SQLlite & MySQL – free open source
Structured Quarry Language – a language used to ask the database questions
ex.
Oracle/DB2 – propriatory, very expensive
All implement about 80% of sqlanguage in the same way, the remainder varies.

Database Management SystemsEach database contains tables.
The tables contain the data, so a table can be considered a separate database.
The tables are not neccessarily connected. Each table contains one kind of information.
In a relational database name, address, photo etc, would all be in separate tables.
A relational DMS can describe the relationships between the tables.
(Chapter 7 in MySQL)

A table contains rows and columns, where columns are fileds (describe content) and rows are records.
ex. Field – Last_Name: Record – Sheptytsky-Zall
Field Name can not contain spaces. The contents may or may not allow spaces depending on the filed type.
Every record in a database has to be unique (unlike a spreadsheet)
Nothing inherent about a database that can allow calculations, it can be set up within the database.

Primary Key
Auto Incrementing by the database – a unique number that the database uses to make sure that there are no duplicate records.
This number is not used by the user as much as it is by the system.
As a convention, the field containing a Primary Key should always end with ‘ID’, almost always type ‘INT’ for interger.

Data Types – most common
INT – whole number
TEXT – a character based format
BLOB – a binary format that can hold character or image (use more processing power)
VARCHAR – variable character length (length can be set to save memory but uses more processing power)
CHAR – reserve space for XX characters

Max for mySQL is 255 in char and varchar
FLOAT – floating point number, any number with a decimal point. Don’t use more less than 4 digits after the decimal.
DATE – able to calculate dates
Do not change the data types once data has been input unless you are giving more space for characters.

Naming Conventions – Database, Tables, Fields
Make it descriptive- explicitly state what they contain.
Make it readable
Camel Text – lowerCase, firstName – instead of a space capitalize every subsequent word
or first_name, lower_case

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.

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.

Dissertation Record

=LDR 01904cas 2200433 a 45×0
=008 080207s2007\\\\xx\a\\\\mb\\eng\d
=040 \\$aCaOTR$beng$cCAOTR
=050 4\$aJV6346$b. 2007
=100 1\$aRosic, Igor.
=245 10$aDual citizenship in the context of globalization, identity and belonging debate$cby Igor Rosic.
=260 \\$c2007.
=300 \\$av, 58 p.
=500 \\$aIncludes table of contents.
=502 \\$aThesis (M.A.) — Ryerson University, 2007.
=504 \\$aBibliography: p. 52-58.
=520 3\$aAt the beginning of the 21st century, there seems to be a global shift in paradigms of identity and belonging. For a long time, both of these entities have been deemed to be fixed and one-dimensional, tied to a specific nation, state and territory. But, under the influence of globalization, notions of identity and belonging are undergoing some fundamental changes. In the interconnected and migratory world we are living in, transnational communities possess and nurture identities of multiple belonging. These global interconnections create new challenges for previous notions of exclusive belonging to a single state-territory, and by extension, citizenship as the ultimate form of political belonging of this situation. In this paper, I discuss various issues connected to dual citizenship and argue for the need for recognition of full dual citizenship by every country in the world.
=610 20$aRyerson University$xDissertations.
=650 $aDual nationality.
=650 \\$aDual nationality European Union countries.
=650 \\$aDual nationality Mexico.
=650 \\$aCitizenship$zCanada.
=650 \\$aConflict of laws$xCitizenship.
=650 \\$aEthnicity.
=710 2\$aRyerson University.$bSchool of Graduate Studies.$bProgram
in Immigration and Settlement Studies.
=910 \\$djuli sheptytsky-zall


LDR 00000cam 2200000I 4500
=001 6006295
=008 740729s1947 nyua b 000 0 eng
=010 \\$a(DLC)47005398
=040 \\$aDLC$cPPi$dOCoLC$dCaOTR
=050 \\$aTR680$b.C38 1947
=100 2\$aCartier-Bresson, Henri,$d1908-2004.
=245 04$aThe photographs of Henri Cartier-Bresson/$ctexts by Lincoln Kirstein and Beaumont Newhall.
=260 0\$aNew York$bMuseum of Modern Art$c1947.
=300 \\$a56 p. :$bill. ;$c26 cm.
=504 \\$aBibliography: p. 56.
=590 \\$aFrom the collection of Michael Mitchell.$5CaOTR
=650 $aPhotography, Artistic.
=700 10$aKirstein, Lincoln,$d1907-1996.
=700 10$aNewhall, Beaumont,$d1908-1993.
=710 20$aMuseum of Modern Art (New York, N.Y.)
=910 \\$dJuli Sheptytsky-Zäll

LDR 00883cam 22002771 4500
=001 8938924
=008 730920s1966 txuac bc 000 0 eng
=010 \\$a66017556
=035 \\$a(OCoLC)692258
=040 \\$aDLC$cNhD$dOCoLC$dDLC$dCaOTR
=042 \\$apremarc
=050 \\$aTR140.W44$bA5 1966
=100 1\$aWeston, Brett
=110 2\$aAmon Carter Museum of Western Art.
=245 10$aBrett Weston Photographs:$bexhibition dates: 27 January-20 March 1966./$cIntrod. by Nancy Newhall.
=260 \\$aFort Worth$c[1966]
=300 \\$a40 p. :$bill., port. ;$c23 cm.
=504 \\$aBibliography: p. [37]
=590 \\$aFrom the collection of Michael Mitchell.$5CaOTR
=600 10$aWeston, Brett.
=650 $aPhotography, Artistic.
=650 $aPhotography$vExhibitions.
=700 10$aNewhall, Nancy,$d1908-1974.
=710 20$aAmon Carter Museum of Western Art
=910 \\$dJuli Sheptytsky-Zäll

LDR 00638cam 2200217Ia 4500
=001 1461947
=008 960822s1975 ne a 000 0 dut d
=020 \\$a9070115018
=035 \\$aocm35232486
=040 \\$aBRL$cBRL$dCaOTR
=041 1\$aeng
=050 \\$aTR140.R655$bR655 1975
=100 1\$aRona, Jutka.
=130 \\$aWolvenstraat 1974 tussen 12 en 2/between 12 and 2$lenglish and dutch.$f1975
=245 10$aWolvenstraat 1974:$btussen 12 en 2/between 12 and 2/$c Jutka Rona.
=260 \\$aAmsterdam :$bMart. Spruijt,$cc1975.
=300 \\$a52 p. :$bchiefly ill. ;$c25 cm.
=520 \\$aThis book is a photographic calendat
=590 \\$aFrom the collection of Michael Mitchell.$5CaOTR
=650 $aPhotography, Artistic.
=651 \\$aWolvenstraat (Amsterdam, Netherlands) $vPictorial works.
=910 \\$dJuli Sheptytsky-Zäll