
8a705c16595ca9150195d00abacade91.ppt
- Количество слайдов: 15
“Abstract” repository services? James Dalziel Adjunct Professor and Director Macquarie E-learning Centre of Excellence (MELCOE) james@melcoe. mq. edu. au www. melcoe. mq. edu. au
The Problem • We have many different types of repositories – Learning Object Repositories – Digital Libraries – “Embedded” repositories (LD, assessment, etc) – File systems (eg, your computer!) – Corporate Content Management Systems (CMS) – Grid datasets and…. – Delivery systems (VLE, LAMS, Grid computing)
The Problem • We have different types of repository functions – Metadata management (entry, schemas, QA, etc) – File management (“black box” vs “internal” view) – Access management (AAA, identity, trust, federate) – Workflow (distributed tasks, approvals, etc) – Secondary usage metadata (human, machine) – Digital rights expression, automated licensing, copyright management, DRM, etc – Classification, taxonomies, vocabularies
The Problem • Different types of repository functions (cont) – Search services and search results presentation – “Delivery” issues (portals, file presentation formats, rendering of content using structural metadata) – Shared workspaces – Repository data manipulation & state (eg, grid) – Version control, Preservation/archiving – Identifiers and resolution – Auditing of changes/usage …. and the list goes on!
The heart of a repository? • A repository is just a “dump” • May use a relational database, XML database, file system, etc • Various technical differences (speed, efficiency) but does it matter conceptually? – If no, what does matter? • Services over the repository – But not how services are implemented (Java, . NET)
Before we describe services… • First, we need to answer some core challenges about the use of repositories (cost/benefit) – What does “publish” mean? – What is the difference between institutional vs personal repositories (ephemeral vs long lasting? ) – When is it worth the trouble of ……? • Second, we need to abstract the required functions across different repository types
Before we describe services… Common services vs Repository services
“Others” National Library NZ - Archive - E-Learn - E-Gov, etc © J. Dalziel 1/7/03 CLIENT (BROWSER) (ANON) Personalised Portal DATA STRUCTURES COMMON SERVICES APPS PORTLET SERVICES Personalised Portal DB (ANON) Access Management Library Catalogue Various examples: LMS/ CRM/ Archives Other Business Apps Federated Search Integrated Library Management System Etc Repository Etc Authentication Authorisation Identity Messaging DRM Security Digital Preservation Service Description (WSDL) MD Schema Package & Transfer Service Discovery (UDDI) Run-time & Tracking Integration Workflow Etc Identity -Objects, People, Organisations, Process Authorisation Etc Policy
“Abstract” repository services NB: Very preliminary thoughts! • (1) Abstract creation & workflow – Abstract metadata management • Schemas, classification, application profiles, etc – Abstract file management • Version control, identifiers, structural metadata, etc – Abstract workflow • MD creation, file submission, approval, updating, QA
“Abstract” repository services • (2) Abstract search (expose vs embed? ) – Abstract query • Common query language? – Abstract gather • Within institution and cross-institution (federation) – Abstract expose • Registries of repositories and use policies – Automation of policy (MAMS & ISO 2146) • NB: Lots of existing library work (but my weak area…help!)
“Abstract” repository services • (3) Abstract delivery – Abstract MD results delivery • Alternative rendering of output? – Abstract file delivery • Structural metadata, rendering of alternate outputs? – Abstract audit/tracking of access • But NOT educational service delivery/educational tracking (learner records) – Content package vs LAMS run-time instantiation? – Library equivalent: Book vs VHS?
© J. Dalziel 27/10/03 REPOSITORY SERVICES PORTLET SERVICES Portal Federated Search Abstract Creation & Workflow Abstract Search etc Abstract Delivery COMMON SERVICES “The dump” Authentication Authorisation Identity Messaging DRM Security Digital Preservation Service Description (WSDL) Service Discovery (UDDI) Integration Workflow Etc
8a705c16595ca9150195d00abacade91.ppt