150 likes | 435 Views
MuDoc: Mu ltimedia /Mu sic Doc umentation. a dynamic digital multimedia archive for world music Michael Frishkopf, Department of Music, University of Alberta (with thanks to Mario Nascimento, Osmar Zaiane, Ken Sobool, David Descheneau, Akil Pessoa, and others for their input.) Aim
E N D
MuDoc: Multimedia/Music Documentation a dynamic digital multimedia archive for world music Michael Frishkopf, Department of Music, University of Alberta (with thanks to Mario Nascimento, Osmar Zaiane, Ken Sobool, David Descheneau, Akil Pessoa, and others for their input.) • Aim • Motivation • Desiderata • Functionality
Aim • Provide digital multimedia archive database for world music research, education, dissemination, and preservation, which is: • Widely (web) accessible • Permanent • Searchable • Extensible • High quality
Motivation • To preserve and present aesthetic value • To support cross-cultural understanding through the arts • To support diversity of music & music-makers • To enable research in humanities and social sciences • To enable research in computer science and signal processing
Desiderata • Capacious • Multimedia • Web accessible • Secure • Data permanent • Scaleable and extensible • High-quality • Searchable • Generate revenue stream • Subsume Smithsonian’s Global Sound
MuDoc functionality • System and environment • Portal • MuDoc objects • Locating information • Export (system to environment) • Import and submission (environment to system) • Annotation • Computation • Data permanence and security • Revenue streams and reporting
MuDoc system and environment • System boundary passes through clients • System • Federation of data servers (multisite distributed dbase) • “Inner” computer client • Environment • “Outer” computer client • Users
Portal • Secure workspace (directory structure, objects) • Bookmarks • Account management ($) • Tools: browse/search, import/export, submit, annotate, compute • Includes client-side application
MuDoc objects • Object types: • Primitive multimedia objects (AV, text, score…) • Compound objects: object clusters and hierarchies • Annotation objects (micro-pointing hypertext) • Functions (algorithms) • Keywords and keyword-acyclic-graphs (KAGs) • Each object assoc. with keywords and metadata • All objects can be (conditionally) imported, submitted, exported • Objects may be displayed using multiple “views”
Locating information • Keyword browse or search • Metadata search • Content search (including non-textual search) • Cross-reference browse (see-also) • Fuzzy search • Suggestions (a la Amazon)
Export & rights management • Export: transfer digital information outside system boundary • Export conditions: derive from object(s), user, IP address. • Time and frequency filtering conditions • Payment ($) condition • Other export conditions (e.g. windows of availability, stream-only) • Conditions realize legal and ethical imperatives • Caching within federation (redundancy) minimizes transmission costs
Import, submission, review • Import: move information inside system boundary (including workspace) • Submit: propose to move object from workspace to database • Submitter (provides object(s), keywords, export restrictions) • Editor (assigns referees using database and keywords) • Referees (review according to quality, legality, ethics, space limitations)
Annotation • Annotation: hypertext in micro-relation to set of database objects • User creates annotations in workspace • Annotations may be submitted for review • Recursion: annotations (as objects) can be annotated • Enables gradual accumulation of scholarly knowledge and insights
Computation • Lisp-like environment • Functions output object from args: (F a b c) • Arguments: objects, object sets, entire database • System vs. user-defined functions • Server vs. client-run functions • Output object stores its formulaic genesis as metadata • Function types: search – edit – filter • Results of computations can be submitted
Data permanence • Tape backup • Redundancy across the federation (Portions of federation connected by high-speed links: Netera, Ca*Net, Internet2…) • Regular transcoding
Revenue streams • Implementation of royalty laws • Implementation of object restrictions • E-commerce, accounting • IN: Subscription and pay-per-download models • OUT: To artistsTo MuDoc (help cover overhead costs)