Fedora App Slide 2009 Hastac

934 views
872 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
934
On SlideShare
0
From Embeds
0
Number of Embeds
101
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Fedora App Slide 2009 Hastac

  1. 1. SEASR:
@
Work
–
Fedora
Components
 Interac.ve
Web

 Applica.on
 Web
Service

  2. 2. SEASR:
@
Work
–
Fedora
Components
 •  Quick
Introduc.on
of
Fedora
 –  Repository
Server
for
digital
content
and
metadata
 –  Digital
Objects
 –  Services
and
Interfaces
Provided
 –  Applica.on
Programmers
Interface
 •  SEASR
Fedora
Components

 •  Move
Content
from
Zotero
to
Fedora
using
SEASR
 web
service
end‐point
running
as
a
data
flow.
 •  Search
and
Browse
Fedora
Repository
using
a
 SEASR
web
based
applica.on
interface
running
as
 a
data‐flow

  3. 3. SEASR:
@
Work
–
Fedora
Components
 •  About
FedoraCommons
:

 •  Fedora
Commons
is
a
non‐profit
organiza.on
 providing
sustainable
technologies
to
create,
manage,
 publish,
share
and
preserve
digital
content
as
a
basis
 for
intellectual,
organiza.onal,
scien.fic
and
cultural
 heritage
by
bringing
two
communi.es
together.
 •  Communi.es
of
prac.ce
that
include
scholars,
ar.sts,
 educators,
Web
innovators,
publishers,
scien.sts,
 librarians,
archivists,
publishers,
records
managers,
 museum
curators
or
anyone
who
presents,
accesses,
 or
preserves
digital
content.
 •  SoRware
developers
who
work
on
the
cuSng
edge
of
 open
source
Web
and
enterprise
content
technologies
 to
ensure
that
collabora.vely
created
knowledge
is
 available
now
and
in
the
future.
 •  Fedora
Commons
is
the
home
of
the
unique
Fedora
 open
source
soRware,
a
robust
integrated
repository‐ centered
plaUorm
that
enables
the
storage,
access
and
 management
of
virtually
any
kind
of
digital
content.
 •  Reference;

hWp://www.fedora‐commons.org/about

  4. 4. SEASR:
@
Work
–
Fedora
Components
 •  Fedora’s
Digital
Object
Model:
 Digital
Object
Iden.fier
 Abstrac5on:

 Persistent
ID
(PID)
 –  The
object
model
is
the
same
whether
the
object
 is
data,
behavior
defini.ons,
or
behavior
 Descrip.ve:
key
metadata
and
 mechanism.
It
also
does
not
maWer
what
kind
of
 rela.onships
to
other
objects
 data
the
digital
objects
is
represen.ng—text,
 images,maps,
audio,
video,
geospa.al
data
are
all
 the
same
to
Fedora.
 FOXML
Metadata
 Flexibility:

 –  Object
Proper.es
 Implementers
of
Fedora
can
design
their
content
 models
to
best
represent
their
data
and
the
 Rela.onship
Metadata
 presenta.on
requirements
of
their
specific
use
 case.
 Item
Perspec.ve:
sets
of
content
or
 Generic:

 –  Metadata
and
content
are
.ghtly
linked
within
the
 metadata
items
 digital
object.
 Aggrega5on:

 –  Datastream
(item)
 Fedora
objects
can
refer
to
data
that
is
stored
 locally
or
that
is
stored
on
any
web
accessible
 Datastream
(item)
 server.
 Datastream
(item)
 Extensibility:

 –  Fedora’s
behavior
interfaces
are
extensible
 because
services
are
directly
associated
with
data
 Service
Perspec.ve:
methods
for
 within
a
Fedora
object.
As
the
services
change,
the
 objects
change
along
with
them.
 dissemina.ng
“views”
of
content
 Default
Disseminator
 Custom
Disseminator
 Reference:

(pages
6,7,
&
9)
 Custom
Disseminator
 hWp://www.fedora‐commons.org/documenta.on/2.2.3/userdocs/tutorials/tutorial1.pdf

  5. 5. SEASR:
@
Work
–
Fedora
Components
 Fedora’s
Preserva5on
&
Archive:
 •  This
diagram
shows
in
very
general
terms
the
structure
of
the
 XML:

 en.re
repository.
Users
interact
with
the
content
of
the
 –  Fedora
objects’
XML
and
the
schema
upon
which
 repository
by
means
of
client
applica.ons,
web
browsers,
 they
are
based
are
preserved
at
ingest,
during
 batch
programs,
or
server
applica.ons.
These
applica.ons
 storage,
and
at
export
 access
the
repository’s
data
by
means
of
the
four
APIs
by
which
 
Content
Versioning:

 –  Fedora
is
exposed:
management,
access,
search,
which
are
 Fedora
repositories
offer
implementers
the
op.on
of
 versioning
data
objects.
When
a
data
object
is
 exposed
via
HTTP
or
SOAP,
and
the
OAI
provider
API,
which
is
 versioned,
the
object’s
audit
trail
is
updated
to
 exposed
via
HTTP.
 reflect
the
changes
made
to
the
object,
when
the
 change
was
made
and
by
whom
and
a
new
version
 of
the
modified
data
is
added
to
the
object’s
XML.
 This
new
datastream
cascades
from
the
original
and
 is
numbered
to
show
the
rela.onship
between
 original
and
version.
This
allows
users
to
retrieve
 older
versions
of
a
data
object
by
performing
a
date/ .me
search
and
retrieval,
or
the
most
current
 version
if
the
date/.me
criteria
are
not
included
in
 the
search.
 Object
to
Object
Rela5onships:

 –  Rela.onships
between
objects
can
be
stored
via
the
 metadata
included
in
the
objects.
This
allows
 implementers
to
link
together
related
objects
into
 parent/child
rela.onships.
 Event
History:

 –  Every
object
in
a
Fedora
repository
contains
an
audit
 trail,
which
preserves
a
record
of
every
change
made
 to
the
object.
 Distributed
Repositories
 •  Dynamic
Data
Transforma5on
 •  Web
Services
(HTTP/SOAP)
 •  Reference:

(pages
7,8
&
14)
 hWp://www.fedora‐commons.org/documenta.on/2.2.3/userdocs/tutorials/tutorial1.pdf

  6. 6. SEASR:
@
Work
–
Fedora
Components
 Fedora’s
“Bigger
Picture”
 Where
could
SEASR
fit
into
the
bigger
picture?
 Reference:

(page
15)
 hWp://www.fedora‐commons.org/documenta.on/2.2.3/userdocs/tutorials/tutorial1.pdf

  7. 7. SEASR:
@
Work
–
Fedora
Components
 Fedora’s
Applica5on
Programmers
Interface
 • Approximately
40
logic
en55es
divided
into
two
dis5nct
sets.
 • 
APIA
–
Access

 • 
APIM‐
Management

 Connec.on
 Connec.on
 Connec.on
 Get
Content
 Connec.on
 Search
 SEASR
Components

 Each
significant
logical
en5ty
defined
by
Fedora
API*
was
represented
as
a
component.
 • 
Allows
for
broadest
possible
range
of
poten5al
uses
and
flexibility
 Reference:


  8. 8. SEASR:
@
Work
–
Fedora
Components
 •  Two
Examples
uses:
 –  Upload
web
service
end‐point
for
Fedora
from
 Zotero
running
as
persistent
data
flows.
 –  Search
&
Browse
simple
example
that
provides
 web
pages
that
act
as
a
user‐interface
for
 exploring
a
Fedora
repository.

  9. 9. SEASR:
@
Work
–
Fedora
Components
 Building
a
Web
Service
End‐Point:
 Listens
for
Input
from
a
Client
normally
in
the
form
of
a
HTTP
 Request
that
acted
upon
to
deliver
to
provide
a
HTTP
Response

 Request
 Response
 Processing
 Steps
 Response
Object

  10. 10. SEASR:
@
Work
–
Fedora
Components
 Web
Service
Scenario

  11. 11. SEASR:
@
Work
–
Fedora
Components
 Web
Service

 Request
Processor

  12. 12. SEASR:
@
Work
–
Fedora
Components
 Web
Service

 Func.onal
Work
 And
Building
Response

  13. 13. SEASR:
@
Work
–
Fedora
Components
 Web
Service

 Send
Response

 to
Client

  14. 14. SEASR:
@
Work
–
Fedora
Components
 Web
Service

 Output
Could
Allow

 Addi.onal
Ac.ons
 
in
The
Response

  15. 15. SEASR:
@
Work
–
Fedora
Components
 •  Two
Examples
uses:
 –  Upload
web
service
end‐point
for
Fedora
from
 Zotero
running
as
persistent
data
flows.
 –  Search
&
Browse
simple
example
that
provides
 web
pages
that
act
as
a
user‐interface
for
 exploring
a
Fedora
repository.

  16. 16. SEASR:
@
Work
–
Fedora
Components
 Building
a
Web
–based
Applica5on
:
 Capture
Input
from
a
Client
Request
that
are
evaluated
and
 cause
a
Response
to
be
computed,
generated,
&
delivered
back
 to
the
client
 Response
Object
 Request
 Response
 Processing
 Cycle
 Processing
 Cycle
 Processing
 Cycle

  17. 17. SEASR:
@
Work
–
WebService


  18. 18. SEASR:
@
Work
–
WebSession


  19. 19. SEASR:
@
Work
–
WebResponder


  20. 20. SEASR:
@
Work
–
Condi.onal
Gate

  21. 21. SEASR:
@
Work
–
Fedora
Components
 Search
Query
 And
 Results

  22. 22. SEASR:
@
Work
–
Fedora
Components
 Fedora
XML
 Object

  23. 23. SEASR:
@
Work
–
Fedora
Components
 Detail
Datastreams
&
 Methods

  24. 24. SEASR:
@
Work
–
Fedora
Components
 View
Datastream
 Dublin
Core

  25. 25. SEASR:
@
Work
–
Fedora
Components
 Complicated
Overview
of
 Func.onal
View
of
Applica.on
 Applica.on
Orchestra.on
 Orchestra.on

  26. 26. SEASR:
@
Work
–
Fedora
Search


  27. 27. SEASR:
@
Work
–
Fedora
Components
 Interac.ve
Web

 Applica.on
 Web
Service


×