Workshop presented by Mark Diggory.
Check out his powerpoint at Manakin workshop
Manakin : publishing framework called cocoon, which separates layers of process of producing the presenting of a page. content generation, transformation phases, serialization takes SACS events and serializes them to an xml stream. Could also be text or html, even binary content
Goal: a more modular, extendable, tiered interface using css
Putting more metadata in the item page to support semantic web scanning
CSS & html layouts. manakin has great set of defaults. can do branding at community and collection and item levels. However right now it is done on the server by the developer.
Visualization of metadata : Texas A&M geologic atlas of the united states. They put google maps on dspace, also google timeline. google maps produces kml file that is embedded in the repository’s view.
Customizable advanced search interface
dome@MIT : image manakin repository
Tiers
- style : create simple themes, xhtml and css
- theme : ccreate complex themes. xsl xhtml css
- aspect : add new features, cocoon and java
Documentation
- dspace manual
- theme writing tutorial
- dspace wiki
- mailing lists
Apache cocoon
- web dev framework
- sax based xml
- pipeline based architecture
Modular components
- generators
- transformers
- serializers
Pipeline model
sitemap defines how page is “transformed”, tags are added and removed and added in serialized fashion
3 components
- aspects
- themes
- DRI schema
Aspects have a process of transformation also, following a sitemap. Phased content generation through aspects phases chained into a dri document and passed to style application that assigns themes.
dri schema : digital repository interface schema
- gives you abstract representation of a repository page
- metadata elements
- references to METS
- DIM, DC, QDC, extendable to others
- structural elements
- TEI light
dri is about representing the logical content of page, what objects are referenced (collections, items),
<document>
structural elements based on TEI in <options>
structural elements based on tei in <body> artifact metadata (METS)
web-oriented metadata in <meta> : title, language, style sheets, etc.
</doc…>
aspects implement sets of related features.
- applied to all pages
- interact w repository
- aspect chain
- input dri – aspect process adds more content in stages
- output dri
core aspects:
- artifact browser
- eperson
- submission
- administrative
possibilities:
- shopping cart
- specialized searching
- customized workflow
all aspects are self contained
- java source code
- javascript flow script
- xml configuration
themes stylize content
- xsl, css, images, static resources
- Mark thinks it can be packaged in jars
content generation style application
artifact browswer –> eperson –> submission–> html rendering
theme components
- sitemap
- heart of theme
- config file
- referencees components
xsl
converts dri to html
theme components
takes dri document, applies sitemap that applies xsl and i18n, produces an xhtml doc to which css is applied
xsl is pattern matching : you match a pattern and instruct what html code to use. e.g. span class vs. <b>
you can import xsl stylesheets. dri to xhtml involves a library of xsl stylesheets.
xsl library feeds a single xsl template which is called by sitemap to manage transformation from dri to xhtml document.
a library can include
- package instructions
- structural.xsl
- metadata xsls:
- MODS-Handler.xsl
- QDC-Handler.xsl
- General-Handler.xsl
metadata handlers
4 display types, different versions for DIM, METS, and QDC
- summarylist
- summaryview
- detailed list
- detailed view
common modifications
- headerfooter
- item icon
- item logos
header & footer
some of the themes may not be portable because of the developer’s metadata conventions.
localhost:8080/xmlui
localhost:8080/xmlui/?XML
localhost:8080/xmlui/DRI
dspace-test.mit.edu
mit has a download this item as a package utility dev’d through open courseware program.
configure tomcat to always look at webapps
dspace jspui has a bunch of help pages. manakin does not have help pages.
may have to copy static html and creating links from manakin
where to put in htmls? could put them next to static content folders, such as images or lib. may be theme-specific, too.
you can use aspect level to get system to look at specific place for changed i18n translations, e.g. where you are changing text for different collections with unique submission workflows.
localhost:8080/metadata/handle/xxxx/mets.xml
What is a theme : going from dri to html is theme
What is an aspect : going from dri to dri is aspect
What is dri : dri is an xml document format
