asset management system for coolstatela thesis presentation winter 2008

Asset Management Systemfor CoolStateLA

Thesis Presentation Winter 2008

Farrukh ShakilCS Dept., CalStateLAAdvisor: 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 Object Fedora Object

Object-Object Relationships

Fedora Object1

FedoraObject 2

<isMemberOf>

<Contains>

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 <#ri> where $s $p $o and $p <mulgara:is>

<info:fedora/fedora-system:def/relations-external#isMemberOf>

and $o <mulgara:is> <info:fedora/cPID>

AMS's ArchitectureFedora Repository/Server

Fedora Client

CoolS tate's Client for Fedora/ Controller

Integration Interface

APIA-Lite CallsXML/DS

SOAP Calls

FOXML ByteStreams, Simple Method Calls

Data/Meta Data

Use r In te rfa ce / O th e r Co m p o n e n ts

M ulgara Resource Index

ITQL

Object Relationships

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 ModelGallery(Collect ion)

No of Im ages(CM D)Creat ion Date(CM D)Event(DC--> Subject)Creator(DC--> Owner)Source(DC)Tit le Im ages(M DS-IM AG E)

getThum bnails()s lideShow()getM D()

Im age(Item )

Label (DC--> Tit le)Date Taken(CM D)Photographer(DC--> Cont ributor). ..Form at(DC)Content (RDS--> M DS-IM AGE)Im age(M DS-IM AGE)

rel:isMemberOf

bDef

brightness()grayscale()wm Text ()zoom Am t()convertTo()newW idth()

Im age CM odel

DS-COM POSITE-M O DEL(IDS-XM L). ..

hasContentModel(conforms ...

hasBDef

bM ech

brightness()grayscale()wm Text ()zoom Am t()convertTo()newW idth()

isContractor(deploys Service f...

hasBDef(deploysService)

STORI Content Model

Text

Author--> DC-CreatorCreat ion Date--> CM DTit le--> DCForm at--> DCDesc/Abst ract--> DCCONTENT--> RDS-TEXTTEXT--> M DS

showAbstract ()

Im age

Photographer--> DC-CreatorDate Taken--> CM DForm at--> DCTit le--> DCDim ensions--> CM DDescription--> DCCONTENT--> RDS-IM AG EIM AGE--> M DS

resize()

V ideo

Runtim e--> CM DForm at--> DCV ideographer--> DC-CreatorCreat ion Date--> CM DTit le--> DCDescription--> DCCONTENT--> RDS-V IDEOVIDEO--> M DS

setResolut ion()

Audio

Runtim eForm at--> DCCreat ion Date--> CM DAudiographer--> DC-CreatorTit le--> DCDescription--> DCCONTENT--> RDS-AUDIOAUDIO--> M DS

setB itrate()

Collection of STORIs

Tit leNo Of STORIsSr. Editor

STORI

Editor--> DC-CreatorReporters list --> DC-Cont ributor. ..M edia--> DC-Form atS tatus--> DC-S tateValidit y Date--> CM D

applyS tyleSheet ()validateM odel()

rel:isMemberOfrel:isMemberOfrel:isMemberOf

rel:isMemberOf

rel:isMemberOf

News Feed Content Model

Feed Collect ion

Tit le--> DCDate of F ilter--> CM DUser--> DC-CreatorF ilter Term --> DC-Description

Feed

Tit le--> DCDesc--> DCSum m ery--> DC-SubjectDate--> DCSource--> DC

isMemberOf

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 1.2.1 <http://www.epcedit.com/UserManual/g4701.html>

“What is Mulgara?”,Mulgara FAQ .,2006 <http://docs.mulgara.org/overview/faq.html#o1068>

“The Fedora Content Model Architecture”,Fedora System Documentation RL 3.0., <http://www.fedora-commons.org/documentation/3.0b1/userdocs/index.html>