1 / 14

Feeding Sakai The relationship between Sakai and repositories

Feeding Sakai The relationship between Sakai and repositories. Chris Awre Jerry Persons. Sakai and repositories. Sakai long-term future Introduction to Sakai presentation, Sakai Conference, 30th May. Repositories are here now!.

drake
Download Presentation

Feeding Sakai The relationship between Sakai and repositories

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Feeding SakaiThe relationship betweenSakai and repositories Chris Awre Jerry Persons

  2. Sakai and repositories • Sakai long-term future • Introduction to Sakai • presentation, Sakai • Conference, 30th May Repositories are here now!

  3. Enabling key university business processes in an online environment Recognition of multiple roles Identity management Adopting service-oriented approach Portal as key presentation point Supporting university use of information technology The Digital University

  4. ‘Repositories’ of digital content Theses Images Datasets Exam papers Video Archives E-prints Learning materials Sound E-books

  5. Portal Staff and student views Personalisation or ‘Groupisation’ Sakai E-Learning E-Research Web applications Desktop applications Presentation/application paths

  6. Interface layer Hull Fedora instance From CNI presentation, Spring 2005 A Technology analysis of repositories and services -- a Mellon project at Johns Hopkins University

  7. Level of interaction Lightweight or complex approach Positioning of content Where does the content need to be? Positioning of functionality Where is the functionality being delivered? Security Who can access what? Interface layer factors

  8. Influenced by the level of interaction required or enabled User as author, reader or manager Lightweight good for readers, e.g., search Complex good for authors, e.g., deposit Mixed approach good for managers Is interaction uni- or bi-directional? Lightweight or complex interface

  9. Does content need to move through the interface layer? Where can metadata act as an intermediary? Use of identifiers as minimal link Moving content raises versioning & DRM issues But can also open up possibilities Positioning content

  10. The functionality/content boundary In the presentation/application layer e.g., Discovery-2-Delivery In the repositories layer e.g., Content lifecycle In between Third-party intermediary shared infrastructure Positioning functionality

  11. Levels of access

  12. Interface layer Different levels of interface layer will be required

  13. Chris Awre c.awre@hull.ac.uk Thank you

  14. Who uses a repository with Sakai? What is the current relationship/link? Who uses repositories for other purposes? Does anything prevent it being used with Sakai? How do you access content from within Sakai? Questions

More Related