What are Multimedia Database Characteristics ?

Multimedia Database Characteristics 

A  multimedia database contains various data types such as text,  images,  graphic objects (including pictures,  drawings, and illustrations),  animation sequences,  video, and audio.  Additionally, Kalipsiz  summarized some characteristics of multimedia data below:

  • Lack of structure:  Multimedia data often are not quite structured;  therefore,  standard indexing and/or content-based search and retrieval may not be available.  

• Temporality: Different multimedia data types have different requirements. For example, some multimedia data types such as video, audio, and animation sequences have temporal requirements that have implications on their storage, manipulation, and presentation, but images, video, and graphics data have spatial constraints in terms of their content. 

 • Massive Volume:  Usually,  the data size of multimedia is large such as video; therefore, multimedia data often require a large storage device.

  • Logistics:  Non-standard media can complicate processing.  For example,  a  multimedia database application requires using compression algorithms.  



Comments

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

Suppose that a data warehouse consists of the three dimensions time, doctor, and patient, and the two measures count and charge, where a charge is the fee that a doctor charges a patient for a visit. a) Draw a schema diagram for the above data warehouse using one of the schemas. [star, snowflake, fact constellation] b) Starting with the base cuboid [day, doctor, patient], what specific OLAP operations should be performed in order to list the total fee collected by each doctor in 2004? c) To obtain the same list, write an SQL query assuming the data are stored in a relational database with the schema fee (day, month, year, doctor, hospital, patient, count, charge)

Discuss classification or taxonomy of virtualization at different levels.