Presentation on theme: "Content and Systems Week 3. Today’s goals Obtaining, describing, indexing content –XML –Metadata Preparing for the installation of Dspace –Computers available."— Presentation transcript:
Content and Systems Week 3
Today’s goals Obtaining, describing, indexing content –XML –Metadata Preparing for the installation of Dspace –Computers available –User names and passwords –Access
The Digital Library Content Essential elements for a digital library –Users –Content –Services
Content - requirements Store –Organize –Describe Find Deliver
Describing the content How to describe content –Metadata Machine readable description of anything What description –Machine readable requires standard descriptive elements Dublin Core (http://dublincore.org/)http://dublincore.org/ –International standard –“a standard for cross-domain information resource description.” –15 descriptive elements Other metadata schemes –IEEE-LOM
Metadata What does metadata look like? Metadata is data about data –Information about a resource, encoded in the resource or associated with the resource. The language of metadata: XML –eXtensible Markup Language
XML XML is a markup language XML describes features There is no standard XML Use XML to create a resource type Separately develop software to interact with the data described by the XML codes. Source: tutorial at w3school.com
XML rules Easy rules, but very strict First line is the version and character set used: – The rest is user defined tags Every tag has an opening and a closing
Element naming XML elements must follow these naming rules: –Names can contain letters, numbers, and other characters –Names must not start with a number or punctuation character –Names must not start with the letters xml (or XML or Xml..) –Names cannot contain spaces
Elements and attributes Use elements to describe data Use attributes to present information that is not part of the data –For example, the file type or some other information that would be useful in processing the data, but is not part of the data.
Repeating elements Naming an element means it appears exactly once. Name+ means it appears one or more times Name* means it appears 0 or more times. Name? Means it appears 0 or one time.
Using XML - an example Define the fields of a recipe collection: ISO 8859 is a character set. See
Processing the XML data How do we know what to do with the information in an XML file? –Document Type Definition (DTD) Put in the same file as the data -- immediate reference Put a reference to an external description Provides the definition of the legitimate content for each element
Document Type Definition Repeat 0 or more times
Meringue cookies 3 egg whites 1 cup sugar 1 teaspoon vanilla 2 cups mini chocolate chips Beat the egg whites until stiff. Stir in sugar, then vanilla. Gently fold in chocolate chips. Place in warm oven at 200 degrees for an hour. Alternatively, place in an oven at 350 degrees. Turn oven off and leave overnight. Not the way that I want to see a recipe in a magazine! What could we do with a large collection of such entries? How would we get the information entered into a collection? External reference to DTD
XML exercise Design an XML schema for an application of your choice. Keep it simple. Examples -- address book, TV program listing, DVD collection, …
Another example A paper with content encoded with XML: First few lines: Standards E-learning and their possible support for a rich pedagogic approach in a 'Integrated Learning' context Rodolophe Borer "ePBLpaper11.dtd” shown on next slide
Vocabulary Given the need for processing, do you want free text or restricted entries? Free text gives more flexibility for the person making the entry Controlled vocabulary helps with –Consistent processing –Comparison between entries Controlled vocabulary limits –Options for what is said
Vocabulary example Recipe example –What text should be controlled? –What should be free text? Ingredients –Ingredient-amount –Ingredient-name –Should we revise how we coded ingredient amount? Directions
Dublin Core Standard set of metadata fields for entries in digital libraries: –Title, creator, subject, description, publisher, contributor, date, type, format, identifier, source, language, relation, coverage, rights
Dublin Core elements see: Title Creator Subject - C Description Publisher Contributor Date Type - C Format - C Identifier Source Language Relation Coverage - C Rights Rights Management information Space, time, jurisdiction. C = controlled vocabulary recommended. Reference to related resource Standards RFC 3066, ISO639 Unambiguous ID Ex: collection, dataset, event, image YYYY-MM-DD, ex. Entity primarily responsible for making content of the resource Entity making the resource available Contributor to content of the resource What is needed to display or operate the resource.
A DSpace example CITIDEL:
IEEE - LOM Example of a specialized metadata scheme –Learning Object Metadata Specifically for collections of educational materials Includes all of Dublin Core See
Computing systems Linux machines Introduction to unix: Dspace: –Documentation, including installation - Najib Nadi, our system administrator, is setting up the machines. He will send a message to the class by the middle of the week with details of machine location and login. Remember - you have the option to use your own machine, but must meet the criteria described last week.
This session Talked about the way that content is described. Saw one way that content gets into a DL. Became familiar with the computing resources available for our use.