fedora rathachai chawuthai [email protected] information management csim / ait repository...

FEDORA

Rathachai [email protected]

Information ManagementCSIM / AIT

RepositoryIssued document 1.0

2

Agenda

• Overview• Data Model• Services• Architecture• Fedora in use• Challenges

3

Overview

4

• Flexible Extensible Digital Object

Repository Architecture

• A system that serve digital content repository for a wide variety of users– E.g. institutional repository, digital archive, content

management system, scholarly publishing enterprises, and digital library.

• Sponsor by Fedora Common– A non-profit organization providing free product

What is Fedora

fedora-commons.org, wikipedia.org

5

• Fedora has a core component that response to enable durable storage and access to the digital content

• Fedora is able to be either a stand-alone server or a component of other system

• To complete repository solution, 3rd parties are needed to enhance features– E.g. authoring, search engine, workflow management,

security component

Capability

fedora-commons.org

6

• Fedora’s Digital Object Model– The model can apply to many domains and digital object types.

• Distributed Repositories– It can integrated access to digital resource from other repositories.– It provides interface accessed by multiple repositories.

• Preservation & Archiving– Represent preservation object by XML format– Offer content versioning– Can define object to object relationships– Log event history for every change of the object

• Web Service– Provide SOAP and REST access

• Easy to integrate with other applications and systems– It is able to function as a generic repository that other applications or systems

can apply it

Design advantages

fedora-commons.org

7

• Store all types of content and its metadata• Digital content of any type can be managed and maintained• Metadata about content in any format can be managed and maintained• Scale to millions of objects• Access data via Web APIs (REST/SOAP)• Provide RDF search (SPARQL)• Rebuilder Utility (for disaster recovery and data migration)• The entire repository can be rebuilt from the digital object and content files.• Content Model Architecture (define "types" of objects by their content)• Many storage options (database and file systems)• JMS messaging (your apps can "listen" to repository events)• Web-based Administrator GUI (low-level object editing)• OAI-PMH Provider Service• GSearch (fulltext) Search Service• Multiple, customer driven front-ends.

Features

fedora-commons.org

8

• Fedora– A flexible system that is based on fundamental of SOA. It is capable to

preserve and access any types of digital contents. However, it does not provide rich user interface.

• DSpace– A complex system that complete all function of repository focusing on

user experience mainly. However, it is not a flexible system.

• EPrints– A system that is primarily used for scientific publication (digital object

are not modified very often). Commonly, it provides features as a document management system.

Compare with others

wikipedia.org

Archival Repository Systems

9

• User Interface– Provide complete user interfaces supporting all types of end-users

• System Security– Provide authentication and authorization in order to access information and functions

• RDF searchable– Provide service for semantic search in form of RDF language

• Customizable metadata formats– Allow users to work with many types of metadata format

• Flexibility of the system– Has flexibility of architecture that allow to build many alternative behaviors

• SOA principle– Provide accessibilities of services following principles of Service Oriented Architecture

• Process based approach– Support document management process

• Support Preservation Strategies– Support preservation activities of digital information based on OAIS reference model

Compare with others

Criteria

10

User InterfaceSystem SecurityRDF searchable

Customizable metadata formatsFlexibility of the system

SOA principleProcess based approach

Support Preservation Strategies

Compare with others

Fedo

ra

DSp

ace

EPrin

ts

D E

FFF

D

D

F

F

F

D

D

Michal,2010

E

E

Result

F D

E

E

F E

11

Data Model

12

<foxml:digitalObject PID="demo:999" xmlns:foxml="info:fedora/fedora-system:def/foxml#">

<foxml:objectProperties> ... </foxml:objectProperties>

<foxml:datastream ID="DC" STATE="A" CONTROL_GROUP="X" VERSIONABLE="true"> ... </foxml:datastream>

<foxml:datastream ID="RELS-EXT" CONTROL_GROUP="X"> ... </foxml:datastream>

<foxml:datastream CONTROL_GROUP="E" ID="IMAGE" STATE="A" VERSIONABLE="true"> ... </foxml:datastream>

<foxml:disseminator ID="DISS1" BDEF_CONTRACT_PID="demo:8" STATE="A" VERSIONABLE="true">

... </foxml:disseminator>

</foxml:digitalObject>

FOXML

Fedora Object XMLFOXML is a metadata that is stored in an object as a content.FOXML is required by Fedora Repository

13

• Digital Object Identifier: A unique, persistent identifier for the digital object.

• System Properties: A set of system-defined descriptive properties that is necessary to manage and track the object in the repository. – Object Properties describe the object’s type, its state, the content model to which it

subscribes, the created and last modified dates of the object, and its label.

• Datastream(s): The element in a Fedora digital object that represents a content item.

Object Data Model

fedora-commons.org

14

System Properties

<foxml:objectProperties> <foxml:property NAME="http://www.w3.org/1999/02/22-rdf-syntax-ns#type" VALUE="FedoraObject"/> <foxml:property NAME="info:fedora/fedora-system:def/model#state" VALUE="A"/> <foxml:property NAME="info:fedora/fedora-system:def/model#label" VALUE="FOXML Reference Example"/> <foxml:property NAME="info:fedora/fedora-system:def/model#contentModel" VALUE="TEST_IMAGE"/> <foxml:property NAME="info:fedora/fedora-system:def/model#createdDate" VALUE="2004-12-10T00:21:58.000Z"/> <foxml:property NAME="info:fedora/fedora-system:def/view#lastModifiedDate" VALUE="2005-01-20T22:46:07.506Z"/> <foxml:extproperty NAME="http://www.openarchives.org/OAI/1.1/oai-identifier.xsd" VALUE="oai:cornell.edu:demo:999"/>

</foxml:objectProperties>

• The content of System Properties is generated by system

For example

15

• A datastream is the element of Fedora object• A Fedora object can have one/more Datastreams– (It can treat as bitstream)

• Fedora model supports versioning of Datastreams– Every change of datastreams has running version

Datastreams

fedora-commons.org

16

• Datastreams can be:– Digital resource that is needed to preserve– Metadata of the digital resource

E.g. DublinCore (DC), METS, PREMIS, …. , and etc

• More …– DC is a default Datastream of Fedora system– AUDIT is to record change of digital object.

• AUDIT content is controlled by system (no human editable)

– RELS-EXT is to provide relationship between digital objects

Datastreams

fedora-commons.org

17

• Easy perspective– Fedora repository as a warehouse– Fedora digital object as a cabinet– Datastreams as a drawer

Datastreams

Fedora repository

Fedora Object

Datastream

18

Digital Object Identifier

Keep Persistent ID of an object called PID

Datastream

ID:38493

PID

19

Object Property

A set of system-defined descriptive properties that is necessary to manage and track the object in the repository. It is controlled by system

Datastream

Prop

PID

<foxml:objectProperties> <foxml:property NAME=“…#state" VALUE="Active"/> <foxml:property NAME=“…#label" VALUE="Example 1"/> <foxml:property NAME=“…#ownerId" VALUE=“st111227"/></foxml:objectProperties>

Example

20

DatastreamDlubinCore (DC)A reserved datastream.(Key object metadata)

DC contents is basically generate to fedora objects. However, administrator is able to add it by insert DC information in the stream

Datastream

DC

PID

Prop

<dc:title

>

<dc:author>

<oai_dc:dc xmlns:oai_dc="...." xmlns:dc="...." xmlns:xsi="...." xsi:schemaLocation="...."> <dc:title>Example 1</dc:title> <dc:identifier>demo:555</dc:identifier></oai_dc:dc>

Example

21

DatastreamAUDITA reserved datastream.(Key object metadata)

To record a change of digital object.The record is controlled by system

Datastream

AUDIT

PID

Prop

audit:recordAudit:process

DC

<audit:auditTrail xmlns:audit="info:fedora/fedora-system:def/audit#"> <audit:record ID="AUDREC1"> <audit:process type="Fedora API-M"/> <audit:action>addDatastream</audit:action> <audit:componentID>HTML</audit:componentID> <audit:responsibility>fedoraAdmin</audit:responsibility> <audit:date>2011-07-07T16:47:12.679Z</audit:date> <audit:justification></audit:justification> </audit:record></audit:auditTrail>

Example

22

DatastreamRelationship-External

RELS-EXTA reserved datastream.(Key object metadata)

To defined relationship with other digital objects in RDF syntax

Datastream

RELS-EXT

PID

Prop

DC

<foxml:datastream ID="RELS-EXT" STATE="A" CONTROL_GROUP="X" VERSIONABLE="false"> <foxml:datastreamVersion ID="RELS-EXT1.0" LABEL="RDF Statements about this object" CREATED="2008-07-02T05:09:44.406Z"

MIMETYPE="application/rdf+xml" > <foxml:xmlContent>

<rdf:RDF xmlns:fedora-model="info:fedora/fedora-system:def/model#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="info:fedora/fedora-system:ServiceDeployment"> <fedora-model:hasModel rdf:resource="info:Model"></fedora-model:hasModel> </rdf:Description> </rdf:RDF> </foxml:xmlContent> </foxml:datastreamVersion></foxml:datastream>

Example AUDIT

23

DatastreamContent … e.g. IMG

User can add content that need to preserve. In this case, user need to preserve image file, so he can upload image file to system and name the datastream himself (e.g. IMG).

Datastream

IMG

PID

Prop

DC

AUDIT

RELS-EXT

24

DatastreamContent e.g. Metadata “PREMIS”

It can use datastream to keep external metadata schema e.g. PREMIS. User has to define a PREMIS content and add it as the datastream, then name the datastream e.g. “PREMIS”

Datastream

PID

Prop

DC

ExampleAUDIT

RELS-EXT

PREMIS

IMG

pms:objectpms:eventpms:agentpms:rights

25

User can change datastream directly in the digital object. After changing, The system run a new version of the content.Thus, user is able to access the previous version of content.

Versioning

PID

Prop

PREMIS

AUDIT

RELS-EXT

DC

IMG

<dc:title

>

<dc:author>

<dc:subject>

DC

<dc:title><dc:author>

<dc:title><dc:author>

<dc:subject>

V. 1V. 2

26

• Datastream Identifier: an identifier for the Datastream that is unique within the digital object (but not necessarily globally unique)

• State: the Datastream state of Active, Inactive, or Deleted• Created Date: the date/time that the Datastream was created

(assigned by the repository service)• Modified Date: the date/time that the Datastream was modified

(assigned by the repository service)• Versionable: an indicator (true/false) as to whether the repository

service should version the Datastream. By default the repository versions all Datastreams.

• Label: a descriptive label for the Datastream• MIME Type: the MIME type of the Datastream (required)

Datastream’s Properties

fedora-commons.org

27

• Format Identifier: an optional format identifier for the Datastream. Examples of emerging schemes are PRONOM and the Global Digital Format Registry (GDRF).

• Alternate Identifiers: one or more alternate identifiers for the Datastream. Such identifiers could be local identifiers or global identifiers such as Handles or DOI.

• Checksum: an integrity stamp for the Datastream which can be calculate using one of many standard algorithms (MD5, SHA-1, etc.)

• Bytestream Content: the "stuff" of the Datastream is about (such as a document, digital image, video, metadata record)


fedora-commons.org

28

• Control Group: pertaining the the bytestream content, a new Datastream can be defined as one of four types, or control groups, as follows:– Internal XML Metadata – To store XML content– Managed Content – To store content that need to preserve; such

as, image file, video, pdf, and etc that upload to the system.– Redirect Referenced Content - To store URL of digital object from

external repository– External Referenced Content – Same purpose as Redirect, but

when user access the content, user will see url of content in the same domain name of the repository


fedora-commons.org

29

Example


List of datastreams

Fedora object information

Be able to add a new datastream

Can export

Display digital object information

30

Example


In case of XML, user can input XML content

here.

XML

Datastream group XML.It might be ontology, RDF, metadata, and etc.

31

Example


URL of image in repository

M

Set MIME Type

Datastream group Managed Content, a content that user need to preserve

32

Example


Reference URL

E

Set MIME Type

Reference digital object from external source.The digital content will not be stored in the repository itself.

URL to access

33

Example


View XML Object

View digital object in XML format

34

Example


Can export

• FOXML 1.1 (the most current FOXML format)• FOXML 1.0 (the FOXML format used with pre-3.0 Fedora repositories)• METS 1.1 (the most current Fedora extension of METS)• METS 1.0 (the METS format used with pre-3.0 Fedora repositories)• ATOM (the Fedora extension of Atom)• ATOM ZIP (an ATOM based format which packages all datastreams along with the object XML in a ZIP file)

Export digital object to another format

35

<?xml version="1.0" encoding="UTF-8"?><foxml:digitalObject VERSION="1.1" PID="changeme:2"xmlns:foxml="info:fedora/fedora-system:def/foxml#"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="info:fedora/fedora-system:def/foxml# http://www.fedora.info/definitions/1/0/foxml1-1.xsd"> <foxml:objectProperties> <foxml:property NAME="info:fedora/fedora-system:def/model#state" VALUE="Active"/> <foxml:property NAME="info:fedora/fedora-system:def/model#label" VALUE=" Photo Jpg"/> <foxml:property NAME="info:fedora/fedora-system:def/model#ownerId" VALUE="Rathachai"/> <foxml:property NAME="info:fedora/fedora-system:def/model#createdDate" VALUE="2011-07-06T15:13:41.243Z"/> <foxml:property NAME="info:fedora/fedora-system:def/view#lastModifiedDate" VALUE="2011-07-12T20:10:58.659Z"/> </foxml:objectProperties> <foxml:datastream ID="AUDIT" STATE="A" CONTROL_GROUP="X" VERSIONABLE="false"> <foxml:datastreamVersion ID="AUDIT.0" LABEL="Audit Trail for this object" CREATED="2011-07-06T15:13:41.243Z" MIMETYPE="text/xml" FORMAT_URI="info:fedora/fedora-system:format/xml.fedora.audit"> <foxml:xmlContent> <audit:auditTrail xmlns:audit="info:fedora/fedora-system:def/audit#"> <audit:record ID="AUDREC1"> <audit:process type="Fedora API-M"/> <audit:action>modifyObject</audit:action> <audit:componentID></audit:componentID> <audit:responsibility>fedoraAdmin</audit:responsibility> <audit:date>2011-07-06T15:15:22.428Z</audit:date> <audit:justification></audit:justification> </audit:record> <audit:record ID="AUDREC2"> <audit:process type="Fedora API-M"/> <audit:action>modifyObject</audit:action> <audit:componentID></audit:componentID> <audit:responsibility>fedoraAdmin</audit:responsibility> <audit:date>2011-07-06T15:16:37.065Z</audit:date> <audit:justification></audit:justification> </audit:record> </audit:auditTrail> </foxml:xmlContent> </foxml:datastreamVersion> </foxml:datastream> <foxml:datastream ID="DC" STATE="A" CONTROL_GROUP="X" VERSIONABLE="true"> <foxml:datastreamVersion ID="DC1.0" LABEL="Dublin Core Record for this object" CREATED="2011-07-06T15:13:41.243Z" MIMETYPE="text/xml" FORMAT_URI="http://www.openarchives.org/OAI/2.0/oai_dc/" SIZE="339"> <foxml:xmlContent> <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd"> <dc:identifier>changeme:2</dc:identifier> </oai_dc:dc> </foxml:xmlContent> </foxml:datastreamVersion> </foxml:datastream> <foxml:datastream ID="MEDRES_IMG" STATE="A" CONTROL_GROUP="M" VERSIONABLE="true"> <foxml:datastreamVersion ID="MEDRES_IMG.0" LABEL="Rathachai image" CREATED="2011-07-06T15:23:39.962Z" MIMETYPE="text/jpeg" SIZE="4575"> <foxml:contentLocation TYPE="INTERNAL_ID" REF="changeme:2+MEDRES_IMG+MEDRES_IMG.0"/> </foxml:datastreamVersion> <foxml:datastreamVersion ID="MEDRES_IMG.1" LABEL="Rathachai image" CREATED="2011-07-06T15:28:01.456Z" MIMETYPE="text/jpeg" SIZE="37443"> <foxml:contentLocation TYPE="INTERNAL_ID" REF="changeme:2+MEDRES_IMG+MEDRES_IMG.1"/> </foxml:datastreamVersion> <foxml:datastreamVersion ID="MEDRES_IMG.2" LABEL="Rathachai image" CREATED="2011-07-06T15:29:40.024Z" MIMETYPE="text/jpeg" SIZE="54448"> <foxml:contentLocation TYPE="INTERNAL_ID" REF="changeme:2+MEDRES_IMG+MEDRES_IMG.2"/> </foxml:datastreamVersion> </foxml:datastream></foxml:digitalObject>

Example exported XML

Information of object identifier

PID…

36



System Properties of digital object

generated from system

…

37



Datastream “AUDIT”

An audit record

Date

Audit ID

Action

…

38



Datastream “DC” DC content

…

39



Datastream of preservation

content

Name + Version number

Managed Content(to store in repository)

Version Record

URL to resource file

…

40

• To record relationship of a Fedora digital object can be related to other Fedora objects.

• Relationship types:– isPartOf, hasPart– isMemberOf, hasMember

• Relationship ontology– http://www.fedora.info/definitions/1/0/fedora-rel

sext-ontology.rdfs

Relationship

fedora-commons.org

http://www.fedora.info/definitions/1/0/fedora-relsext-ontology.rdfs

http://www.fedora.info/definitions/1/0/fedora-relsext-ontology.rdfs

41

Relationship

Example

fedora-commons.org

42

• Benefit of relationship– Support OAI harvesting and user search/browse– Be able to define bibliographic relationship

among objects– Define semantic relationship among resources– Link resources together based on contextual

information

Relationship

fedora-commons.org

43

Pattern

Relationship

<subjectFedoraObject> <relationshipProperty> <targetFedoraObject>

<Chapter1.pdf> <isPartOf> <TheBook>

Example

fedora-commons.org

44

Between object and object use datastream RELS-EXT

Relationship

<isMemberCollectionOf>< > < >

45

Relationship

Between datastreams inside the same Fedora digital objectuse datastream RELS-INT

< >

< >

<isThumbnailOf>

46

Services

47

• Open Source - The Fedora repository system is open source software.• Flexible Digital Object Model - The Fedora digital object model provides the

flexibility to create kinds of objects including documents, images, electronic books, multi-media learning objects, datasets, metadata, and etc.

• Content Versioning - Any modifications made to a Datastream through the Fedora management interface (API-M) will automatically result in the creation of a new version of that Datastream or Disseminator

• XML Ingest and Export - Digital objects can be submitted to a Fedora repository as XML-encoded files : FOXML

• XML Storage - By default, Fedora digital objects are stored in a Fedora repository as XML-encoded files

• Object-to-Object Relationships - Fedora provides the ability to assert object-to-object relationships.

• Access Control and Authentication - Includes a simple form of access control to provide access restrictions based on IP address/range.

Major Features

fedora-commons.org

48

• Simple Search - Fedora automatically creates simple indexes of the repository. Search engine also use information from DC and relationship.

• RDF-based Resource Index - Includes more information about objects plus object-to-object relationships

• OAI Metadata Harvesting Provider - The OAI Protocol for Metadata Harvesting is a standard for sharing metadata across repositories

• Migration Utility - A new migration utility is provided to perform mass export and mass ingest of objects

• Batch Utility - Fedora Administrator client that enables the mass creation and modification of Fedora digital objects

• Reporting Utility - A reporting utility is provided providing different management views of the contents of the Fedora repository

Major Features

web services from wiki.duraspace.org

49

Web Service Interfaces

Internet

50

• Management API (API-M) – SOAP-enabled web service defines an administration interface managing repository. There are necessary functions for administrator to create and maintain digital objects and their components.

• Access API (API-A) – SOAP-enabled web service defines an interface for accessing digital objects stored in the repository.

• Resource Index Search API –RDF based index search provides searching of the new Resource Index to each digital objects following: – object properties– object-to-object relationships– metadata about datastreams and disseminations– default Dublin Core record


API


51

• Access-Lite API (API-A-Lite) –REST-based web service that can be invoked access function to digital object.

• Management-Lite API (API-M-Lite) – Future REST-based web service that response for management functions

• Search API (part of API-A-Lite) – REST-based web service that include search operations.


API-LITE a light-weight version of the Fedora Access Service


52

• Datastream Management– addDatastream– compareDatastreamChecksum– getDatastream– getDatastreamHistory– getDatastreams– modifyDatastreamByReference– modifyDatastreamByValue– setDatastreamState– setDatastreamVersionable– purgeDatastream

Management API (API-M)

• Relationship Management– addRelationship– getRelationships– purgeRelationship

• Object Management– modifyObject– purgeObject– export– getNextPID– getObjectXML– ingest– validate


53

• Repository Access– describeRepository– Object Access– findObjects– resumeFindObjects– getObjectHistory– getObjectProfile– Datastream Access– getDatastreamDissemination– listDatastreams– Dissemination Access– getDissemination– listMethods

Access API (API-A)


54

Example API

To get history of the specific object


55

• Semantically search provided by web service.• Allow to query by SPARQL• Response by RDF support formats

such as, N-Triples, RDF/XML, Turtle, and etc.• For example

Resource Index Search API

select $object $modified from <#ri>where $object <fedora:hasModel> <info:ServiceDefinition> and

$object <fedora:lastModifiedDate> $modified

info:fedora/demo:1,2009-02-16T19:39:28.859Zinfo:fedora/demo:12,2009-02-16T19:39:17.843Zinfo:fedora/demo:19,2009-02-16T19:39:20.375Zinfo:fedora/demo:22,2009-02-16T19:39:20.671Z


56

Architecture

57

Framework and Services

fedora-commons.org

58

• Repository Service: the core service that enables functions manipulating digital objects; such as, creation, management, storage, access, and reuse.

• OAI Provider Service: a service that harvests metadata from other repositories and provide metadata to them.

• Directory Ingest Service: a service that uses to ingest a digital object and store it.

• Search Service: a service for search that can be enhanced by adding other search engines.


fedora-commons.org

59

• Object Reuse and Exchange (ORE) Access Point: provide cross repositories service.

• Workflow and Orchestration: (Future plan)• Preservation Integrity Service: (Future plan)• Preservation Monitoring and Alerting Service:

(Future plan)


fedora-commons.org

60

Core Repository Service

fedora-commons.org

61

• The service framework applies concept of OAIS• It provided interfaces to access the core repository services via

web services– API-M (Management)– API-A (Access)– Basic Search– RDF Search

• Fedora Repository server is running on Tomcat• Store data in database

– Object (XML) and byte streams to collect preservation data and metadata

– SQL registry + metadata – RDF-Based index

Core Repository Service

fedora-commons.org

62

Fedora in useA case study of islandora

63

islandora

• Institution– University of Prince Edward Island's Robertson Library

• Description– Islandora is an open source project underway at the Robertson Library at the University of

Prince Edward Island. Islandora combines the Drupal and Fedora software applications to create a robust digital asset management system that can be used for any requirement where collaboration and digital data stewardship, for the short and long term, are critical.

• Tools– Fedora Repository + GSearch, Drupal, and Solr

• Link– http://islandora.ca

Overview

example from fedora-commons.org

http://islandora.ca/



64

islandora

• Provide administration panel– View, ingest, and purge any digital objects– Help user to understand the relationship between digital objects

• Provide lightning-fast search of the Fedora database– Including full-text search– Integrate with Solr to be better performance of searching

• Support many formats of metadata – Allow user to define metadata model for each digital object category

• Support many types of digital object– Support collection of both bond-digital and digitized materials

Features

islandora from wiki.duraspace.org

65

islandora

System Architecture

FedoraCore Service

Database SOLR

GSearchGeneric Search

Drupal Servlet Filter

Web Server

Database Server Search ServerService Provider

Database

Database ServerWeb Server

Service Consumer

Drupal islandora module

66

islandora

islandora.ca

67

islandora

• Drupal Servlet Filter– The Drupal Servlet Filter allows the Fedora Repository to use Drupal’s database for authentication,

including integration with Drupal user roles.• The islandora Module

– The Islandora module is a Drupal module written to allow the Drupal content management system to act as a front end to a Fedora Digital Repository. The module enables viewing and management of Fedora objects. This includes insert, update, and delete datastream, and also browse and search.

• Enabling Indexing/Searching with SOLR– Islandora utilizes the Solr open-source search platform to enable flexible and configurable indexing

and searching. Solr uses the Lucene Java search library at its core for full-text indexing and search and offers hit highlighting, faceted search, dynamic clustering, database integration, and rich document (e.g., Word, PDF) handling as additional features.

• GSearch– The Fedora Generic Search Service, or GSearch, is a search service installed with Fedora that allows

for automatic updating of the Lucene/Solr index. GSearch relies on JMS to receive messages that are sent when Fedora objects are ingested, modified or purged. This keeps the Lucene index in sync with the Fedora repository.

islandora from wiki.duraspace.org

Components

68

islandora - demo - browse - collection

A collection of digital object that collects

many PDF documents.

69

islandora - demo - object relationship

Hierarchy of collection(From administration page)

70

islandora - demo - object relationship

The collections are represent in fedora object hierarchy

islandora:demos

islandora:pdf_collection islandora:demo_image_collection

isMemberOfCollection

islandora:collectionCModel

hasModelhasModel

hasModel

islandora:top

hasModel

hasModel

demo:DualResImageCollection

71

islandora - demo - collection / digital object

A digital object in a collection.

(Display after select a collection)

72

islandora - demo – object relationship

The collections are represent in fedora object hierarchy

islandora:demos

islandora:pdf_collection islandora:demo_image_collection

isMemberOfCollection isMemberOfCollection

islandora:6 islandora:1


islandora:collectionCModel

hasModel

hasModel

hasModel

hasModel

islandora:top

demo:DualResImageCollection

73

islandora - demo - collection / digital object / view

Go inside digital object to get standard

MetaData

74


1)

2) To get stream

75


Be able to retrieve datastream of the

digital object

76

islandora - demo – object relationship

islandora:book_collection


Example structure from digitalized object such as Book that each page is scanned by TIFF format

islandora:demos

islandora:topisMemberOfCollection


islandora:book1 islandora:book2

islandora:book1-page1 islandora:book1-page2

isPartOfisPartOf

77

islandora - demo - collection / digital object / add

It allows user to add digital object under selected collection

e.g. islandora:pdf_collectionStep: 1) click on “Add”

2) Select a content model of digital object.

The choice leads to difference ingestion UI

3) Click “Next”

78


Put metadata information in

application form

79


Scroll down and click “Ingest” to

finish ingest process

80

islandora - demo – Fedora object

All information (including datastream) of the created

digital resource has already ingested to Fedora repository

Fedora admin

81

islandora - demo - admin / collection

User can browse to page that allow user to manage collection and model byMenu : Administer > Content Management > Islandora Content Modeler

82

islandora - demo - admin / collection

Collections of digital object that are displayed in the first page of

digital repository page

Can add more collection from

button +

83

islandora - demo - admin / model

All content models that are templates of digital objects

Create more

Input form to create Content Model

84

islandora - demo - admin / model

Detail of a selected content model

85

islandora - demo - admin / model / form

Input form elements that are customizable to display

on ingestion form

A new input element is able to create from the panel

after click + to add element

86

islandora - demo - search

User can search and get the search result of digital object

87


After view a digital object. User can click a metadata's’

value to search from that valuee.g. dc.subject:History-Conoe Cove (PEI)

88


After that user gets related digital object that relevance to dc.subject:History anddc.subject:Conoe Cove (PEI)

89

islandora - demo

More information about installation and user manual guide are available

at https://wiki.duraspace.org/display/ISLANDORA/Islandora+Guide

https://wiki.duraspace.org/display/ISLANDORA/Islandora+Guide

https://wiki.duraspace.org/display/ISLANDORA/Islandora+Guide

90

Challenges

91

• DSpace– Founded in MIT– An open source software that

provides functions for manage digital resources, and generally support instructional repository.

– It supports many kind of digital formats and controls process to manage digital resource.

– A DSpace data model supports preservation

– It also supports OAI-PMH protocol.

Fedora with DSpace

dspace.org

92

Fedora with DSpace

Fedora-DSpace integrationFlexible

architectureRDF based semantic

search

SOA

Customizable metadata format

Flexible information model

Disaster recovery

Preservation activities

Data migration

Versioning

Many storage options (database or file system)

Web-based application

Documentation process control

Authentication & authorization

Localization

Browse and search UI

Configurable UI

Preservation process management

Administration UI

93

• May, 2009, Fedora Commons and Dspace Foundation merge organization to synergize strategies and missions.

• It becomes “DuraSpace” – a non-profit organization provide leadership and innovation in open source of preservation and dissemination of digital library and institutional repository resources.

Fedora with DSpace

duraspace.org

DURASPACE

94

Fedora with DSpace

• Running DSpace on Fedora– Current status : In progress

duraspace.org

Objective

95

• DURASPACE, a Fedora-DSpace integration, becomes a complete archival repository solution. Users still experiences with the system from rich features that enhance from strong points of DSpace. Furthermore, advantageous back-end features of Fedora are improved in order to serve enhanced DSpace functions.

• Therefore, DURASPACE is capable to provide: – Rich experiences to user; such as,

• rich administration functions, • rich search functions supporting semantic search

– Excellence back-end system that • is based on flexible service architecture • fully supports preservation activities • support versioning of digital object and datastream• has flexible information model appending semantic technology to support relationship

between digital object

• To ensure longevity and re-use of digital content

Fedora with DSpace

Benefits

96

• Identify high impact scholarly applications to integrate with other repositories• Demonstrate DSpace running on top of Fedora• Define common information model

– Map the information model of DSpace to Fedora – Define a common information model for intuitional repository purpose

• Define common standard protocol for repositories• Define scenario for integration open repositories• Develop shared services/modules to enable exchange of information among

repositories• Define common storage API• Integrate semantic technology• Share user interface approaches by Manakin (enhanced DSpace XMLUI) and

build lightweight applications on top of repositories• Move toward common architecture based on well-defined design pattern

architecture

Fedora with DSpace

Possible ideas

duraspace.org

97

DuraCloud

DURACLOUD from duraspace.org

98

• A hosted service and opend technology developed by DuraSpace under concept “Store and Do More”.

• DuraCloud will let libraries and institutes manage own repositories without building own technical infrastructure. It offers storage across commercial and non-commercial provider.

• Progress : Pilot phase• Benefits

– “Digital contents are stored in the cloud”– “Backing up, preserving, and updating content yourself can be an uphill battle”– “Maintaining several copies in different locations is a lot safer”– “Let you add image viewing and media streaming services to your site without messing with new

servers or software”

DuraCloud

DURACLOUD from duraspace.org

99

• PREMIS– PREservation Metadata:

Implementation Strategies– Focus on developing metadata for use in digital

preservation– Sponsored by Library of Congress (LOC)– Objectives

• To store technical information that supports making decision and action in order to do preservation

• To document actions taken, such as migration.• To record the effects of preservation strategies• To ensure authenticity of digital resources over the long-term• To note information about collection management and rights management

Fedora with PREMIS

PREMIS from LOC.gov

100

• Store PREMIS in Fedora Digital Object

Fedora with PREMIS

PREMIS

PREMIS

PREMIS

PREMIS

fedora-commons.org

101

Challenge!

Fedora with PREMIS

?What does input form should look like?

102

Fedora with PREMIS

Could it be?

PREMIS

Object

objectIdentifier *

objectIdentifierType *

objectIdentifierValue *

Environment

storage

relationship

103

Fedora with PREMIS

Could it be?

PREMIS

Object

objectIdentifier *



Environment

ISBN

storage

relationship

104

Fedora with PREMIS

Could it be?

PREMIS

Object

objectIdentifier *



Environment

ISBN

storage

relationship

105

Fedora with PREMIS

Could it be?

PREMIS

Object

objectIdentifier *



Environment

ISBN

storage

relationship

106

Fedora with PREMIS

Could it be?

PREMIS

Object

objectIdentifier *



Environment

ISBN

softwareswName *swVersion

Environment

swType *hwInformation

software

107

Fedora with PREMIS

Could it be?

PREMIS

Object

objectIdentifier *



Environment

ISBN

softwareswName *swVersionswType *hwInformation i

Environment

software

108

Fedora with PREMIS

Could it be?

PREMIS

Object

objectIdentifier *



Environment

ISBN

softwareswName *swVersionswType *hwInformation ibm

Environment

software dc:ibmdp:ibmdp:ibmserverfoaf:ibm

109

Fedora with PREMIS

Could it be?

PREMIS

Object

objectIdentifier *



Environment

ISBN

softwareswName *swVersionswType *hwInformation ibm

Environment

software dc:ibmdp:ibmdp:ibmserverfoaf:ibm

110

Fedora with PREMIS

Could it be?

PREMIS

Object

objectIdentifier *



Environment

ISBN

softwareswName *swVersionswType *hwInformation dp:ibmserver

Environment

software

111

Fedora with PREMIS

Could it be?

PREMIS

Object

objectIdentifier *



Environment

dp:ibmserver

softwareswName *swVersionswType *hwInformation

IBM ServerhwInformation

ISBN

software

112

?

References

• http://www.wikipedia.org• http://www.wseas.us/e-library/conferences/2010/Faro/DNCOCO/DNCOCO-16.pdf

Comparison of digital libraries systemsMICHAL KÖKÖRČENÝ, AGÁTA BODNÁROVÁ University of Hradec Králové, Faculty of Informatics and Management

• http://fedora-commons.org/download/2.0/userdocs/server/features/features.html• http://www.fedora-commons.org/fcrepo/about/examples/escienceeresearch• https://wiki.duraspace.org/display/FCR30/Web+Service+Interfaces• http://www.dspace.org/• http://www.duraspace.org/• https://wiki.duraspace.org/display/DSPACE/DSpace+Fedora+jointprojects• https://wiki.duraspace.org/display/DURACLOUD/DuraCloud• http://www.loc.gov/standards/premis/• https://

wiki.duraspace.org/display/ISLANDORA/Islandora%3bjsessionid=B7E3C28760E87B295138FBE3E1F00280• http://islandora.ca/• https://wiki.duraspace.org/display/ISLANDORA/Islandora• http://islandora.ca/sites/islandora.ca/files/pdf/islandora_2010_ORposter_web_0_0.pdf• http://islandora.ca/sites/islandora.ca/files/Islandora_PASIG_09_Deep_Divesanfran.pdf

113

http://www.wseas.us/e-library/conferences/2010/Faro/DNCOCO/DNCOCO-16.pdf




http://fedora-commons.org/download/2.0/userdocs/server/features/features.html

http://fedora-commons.org/download/2.0/userdocs/server/features/features.html

http://www.fedora-commons.org/fcrepo/about/examples/escienceeresearch

https://wiki.duraspace.org/display/FCR30/Web+Service+Interfaces

http://www.dspace.org/

http://www.duraspace.org/

http://www.duraspace.org/

https://wiki.duraspace.org/display/DSPACE/DSpace+Fedora+jointprojects

https://wiki.duraspace.org/display/DSPACE/DSpace+Fedora+jointprojects

https://wiki.duraspace.org/display/DURACLOUD/DuraCloud

https://wiki.duraspace.org/display/DURACLOUD/DuraCloud

http://www.loc.gov/standards/premis/

https://wiki.duraspace.org/display/ISLANDORA/Islandora;jsessionid=B7E3C28760E87B295138FBE3E1F00280




https://wiki.duraspace.org/display/ISLANDORA/Islandora

https://wiki.duraspace.org/display/ISLANDORA/Islandora

http://islandora.ca/sites/islandora.ca/files/pdf/islandora_2010_ORposter_web_0_0.pdf

http://islandora.ca/sites/islandora.ca/files/pdf/islandora_2010_ORposter_web_0_0.pdf

http://islandora.ca/sites/islandora.ca/files/Islandora_PASIG_09_Deep_Divesanfran.pdf

fedora rathachai chawuthai [email protected] information management csim / ait repository...

Documents

digital content repository

digital object types

types of content

digital library

digital resource

digital contentfedora

types of digital contents

content management system