Asset Management System for CoolStateLA Thesis Presentation Winter 2008 Farrukh Shakil CS Dept., CalStateLA Advisor: Dr. Russ Abbott

Outline Introduction  Digital Repositories  Digital Asset Management Fedora Repository  Object Oriented Model  Webservices  Mulgara Database  Content Model Architecture of the System Content Models  Gallery Content Model  STORI Content Model  News Feed Content Model Demo Gallery CModel Future Work Conclusion References

Introduction Digital Repository is simply a digital library in which collections are stored in digital formats and accessible over the network. Digital Asset Management consists of tasks and decision surrounding ingesting, annotating, cataloging, storage and retrieval of digital assets.

Fedora Repository Stands for Flexible Extensible Digital Object Repository Architecture. Contents are stored in form of digital objects or models.

Object Oriented Model Properties Fields/ Attributes Methods Java ObjectFedora Object

Object-Object Relationships Fedora Object1 Fedora Object 2

Webservice Interfaces API-Access API-Management Resource Index Search(Mulgara)‏ Basic OAI

Mulgara Database For Object -Object Relationship subject-predicate-object ITQL  select $s $p $o from  where $s $p $o and $p  and $o

AMS's Architecture

Content Model The rules for the configuration of elements or digital contents allowable in instances of an element type. Classification of the contents How our intellectual work may be expressed, so that we could communicate our intellectual works effectively to others. A PPT is hardly any different from a Video Game without the proper software to run them.

Fedora CModel Content classification to facilitate discovery. Validation usually at ingest or modification. Template when content is created

CoolState's Content Models Elements  Fedora Elements Data Object CModel Object BDef Object BMech Object  CoolState's Elements Collection Object Item Object

Image Gallery Content Model

STORI Content Model

News Feed Content Model

Demo Gallery Content Model

Future Work Enhance the Functionality of the Controller Interface AMS to other Components Improve the existing Content Models Implement STORI and Feed Content Models Add Video/Audio Collection Content Model

Conclusion The presented Asset Management System provides a complete Asset Management Solution to this project. The Asset Management System built as a part of this project can be used as a baseline. The proposed content model not only captures most of the content and meta-data related requirements but also suggests a mechanism for delivering those contents.

References “Content model”, Glossary of terms,User Manual: For epcEdit Release “What is Mulgara?”,Mulgara FAQ., “The Fedora Content Model Architecture”,Fedora System Documentation RL 3.0., commons.org/documentation/3.0b1/userdocs/index.html