Upload
eposthumus
View
1.974
Download
0
Embed Size (px)
DESCRIPTION
Citation preview
Challenge the future
DelftUniversity ofTechnology
1Overview of Fedora-Commons Repository
Fedora-Commons Repository•A brief overview
Etienne Posthumus, DPO, TU Delft Library
10-04-23
Challenge the future
DelftUniversity ofTechnology
2Overview of Fedora-Commons Repository
What is it?
Fedora is a general-purpose, open-source digital object repository system.
Challenge the future
DelftUniversity ofTechnology
3Overview of Fedora-Commons Repository
What is it?
Fedora is a general-purpose, open-source digital object repository system.
"Flexible Extensible Digital Object Repository Architecture"
NOT the Linux distribution
Challenge the future
DelftUniversity ofTechnology
4Overview of Fedora-Commons Repository
What is it?
Fedora is a general-purpose, open-source digital object repository system.
…a persistence and service delivery platform
Challenge the future
DelftUniversity ofTechnology
5Overview of Fedora-Commons Repository
What is it?
Fedora is a general-purpose, open-source digital object repository system.
…a persistence and service delivery platform
…implemented as a set of Java services (Tomcat)
Challenge the future
DelftUniversity ofTechnology
6Overview of Fedora-Commons Repository
What is it?
Fedora is a general-purpose, open-source digital object repository system.
A well-funded active community with a long history.
7Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Conforms to the OAIS reference model
Open Archival Information System - an ISO model defined by Consultative Committee for Space Data Systems widely adopted in Archives community
Built on sub-systems
Open Source, Open Standards
8Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Persistent digital archive ‘files on disk’ bootstrappeable in the face of disaster XML containers asset management
Built on sub-systems
Open Source, Open Standards
9Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Persistent digital archive ‘files on disk’ bootstrappeable in the face of disaster XML containers asset managementScaleable triple-store Mulgara
Built on sub-systems
Open Source, Open Standards
10Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Persistent digital archive ‘files on disk’ bootstrappeable in the face of disaster XML containers asset managementScaleable triple-store Mulgara Service delivery XSLT via Saxon built-in others pluggable
Built on sub-systems
Open Source, Open Standards
11Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Advantages?
• Scaling• Integrated Asset management• Extensive Versioning• Audit trails• Large(ish) community, esp. mindshare• General ‘fit and polish’
Goal is support for > 10 million objects
12Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Downsides?
• It’s a toolbox not a complete solution (front-end support)• Java code base (for some this is an advantage ;-)• Moving target in terms of innovation (also debatable)• Complexity of some concepts, steep learning curve
A lot of DIY is needed
13Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Digital Object Model
• Compound objects, aggregate items per object
14Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Digital Object Model
• Compound objects, aggregate items per object• Some ‘reserved’ item IDs
15Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Digital Object Model
• Compound objects, aggregate items per object• Some ‘reserved’ item IDs• Essentially an XML container
16Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Digital Object Model<foxml:digitalObject PID="demo:31" VERSION="1.1" 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#ownerId" VALUE="fedoraAdmin"/> <foxml:property NAME="info:fedora/fedora-system:def/model#createdDate" VALUE="2008-07-02T05:09:42.015Z"/> <foxml:property NAME="info:fedora/fedora-system:def/view#lastModifiedDate" VALUE="2008-07-02T05:09:42.015Z"/> </foxml:objectProperties> <foxml:datastream CONTROL_GROUP="X" ID="DC" STATE="A" VERSIONABLE="true"> <foxml:datastreamVersion CREATED="2008-07-02T05:09:43.328Z" FORMAT_URI="http://www.openarchives.org/OAI/2.0/oai_dc/" ID="DC1.0" LABEL="Dublin Core Record for this object" MIMETYPE="text/xml"> <foxml:xmlContent> <oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"> <dc:title>Apache Batik 1.5 Demo Directory</dc:title> <dc:creator>Chris Wilper</dc:creator> <dc:creator>The Apache Group</dc:creator> <dc:subject>svg</dc:subject><dc:publisher>The Apache Group</dc:publisher> <dc:format>image/svg+xml</dc:format> <dc:identifier>demo:31</dc:identifier> <dc:relation>http://xml.apache.org/batik/</dc:relation> <dc:rights>The Apache License</dc:rights> </oai_dc:dc> </foxml:xmlContent> </foxml:datastreamVersion> </foxml:datastream> <foxml:datastream CONTROL_GROUP="E" ID="DS1" STATE="A" VERSIONABLE="true"> <foxml:datastreamVersion CREATED="2008-07-02T05:09:43.328Z" ID="DS1.0" LABEL="Local copy of batikBatik.svg" MIMETYPE="image/svg+xml"> <foxml:contentLocation REF="http://www.fedora-commons.org/demo/misc/batikBatik.svg" TYPE="URL"/> </foxml:datastreamVersion> </foxml:datastream>
An Example
17Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Content Model Architecture
“an integrated structure for persisting and delivering the essential characteristics of digital objects in Fedora”
Modelling behaviours and structure of objects.
Complicated, fairly new, not widely implemented yet, in flux.
…can also be safely ignored when starting out.(which we did not realise)
18Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Fedora at TU Delft Library
• Used to create a repository Infrastructure
19Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Fedora at TU Delft Library
• Used to create a Repository Infrastructure• Multiple projects:
• Institutional Repository (academic output)• Special Collections (Tresor, bouwkunde dias)• Expert Search (finding People)• 3TU Datacentrum
20Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Implementation
• Front-end is Django application
21Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Implementation
• Front-end is Django application• We use the REST API for communication
22Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Implementation
• Front-end is Django application• We use the REST API for communication• Middleware as Python code providing a web API
23Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Implementation
• Front-end is Django application• We use the REST API for communication• Middleware as Python code providing a web API• MOAI flexible OAI-PMH service
24Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Implementation
• Front-end is Django application• We use the REST API for communication• Middleware as Python code providing a web API• MOAI flexible OAI-PMH service• Indexing via SOLR subsequently linked to DISCOVER
25Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
26Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Conversion of existing repository
• Legacy Stellent CMS stored in Oracle• Circa 12000 items• Mostly PDF plus metadata• Conversion scripts in Python• Bulk ingest
27Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Community Participation
• NL Fedora Usergroup• Contact with key Fedora participants at conferences• Presentations and workshop• Developer days planned• Possible collaboration on development• Sponsorship of open-source components
28Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Plans
• Convert existing repository with existing functionality• Incrementally build in new features on ongoing basis• Extend APIs and services• Linked Data repository• More innovative repository applications
29Overview of Fedora-Commons Repository
Challenge the future
DelftUniversity ofTechnology
Questions?
http://www.fedora-commons.org/