22
DLF Services Framework Overview Geneva Henry Rice University/DLF Distinguished Fellow, 2006 19 April 2007
DLF Services Framework Overview
Geneva HenryRice University/DLF Distinguished Fellow, 2006
19 April 2007
19 April 2007 DigCCurr 20072
AgendaSummary of MotivationBusiness vs. Systems LogicDefinitions, Approaches and VocabularyExamplesDetermining ServicesDevelopment Phases and ProcessSFG Members
19 April 2007 DigCCurr 20073
19 April 2007 DigCCurr 20074
Services FrameworkOverview
Need to clearly understand the business(es) of research libraries as we move aggressively in new directions and what processes and functions are needed to serve that mission
We are not designing and implementing a system; we are articulating a services perspective
The systems we run must meet service needs. Libraries should not be held hostage by vendors with nonflexible solutions
19 April 2007 DigCCurr 20075
Strategize
Plan
Build
Business Objective
Business Requirement
Business Process
Business Function
Application
Product
Product Line
Human Interface
Machine Interface
DataData
Entities
Component
Process Driven Services
19 April 2007 DigCCurr 20076
Adopting Existing Models
Initially looked at adopting an existing framework model
Close cooperation with UK e-framework initiatives
Most frameworks focus on systems; we need to look at library business processes as well
Business Process Models considered (e.g. OMG BPM)
19 April 2007 DigCCurr 20077
Towards a Service Oriented Architecure (SOA)
Think legos
Not too small, not too big
19 April 2007 DigCCurr 20078
SFG’s Definition of a Services Framework
A service framework is a set of reference models, along with a set of concepts and vocabulary for expressing and relating them. The service framework – i.e., vocabulary and reference models – covers the range of entities relevant to the articulation of library business goals at varying levels of granularity, as well as the services that support these goals.
19 April 2007 DigCCurr 20079
Approach
Decision to focus on the business logic first, then look for service genres that emerge (automatable, reusable)
Working group focused on defining an approach that could be further developed and implemented
19 April 2007 DigCCurr 200710
So Why Should a Digital Curator Care?
Managing digital knowledge assets = providing the services needed to meet both librarian and consumer needs
Systems need to adapt to rapidly changing needs, constantly providing improved capabilities
Improved efficiency for librariansImproved services for users
19 April 2007 DigCCurr 200711
Key Business Logic Vocabulary Terms
Business Requirement: identifiable segment of an organization’s overall mission. Example: Electronic Resource Management (ERM)
Business Process: a grouping of activities required to fulfill a business requirement. Example: Business/License Negotiation
Business Function: identifiable activities that fulfill a business process. Example: Log Licensing Information
19 April 2007 DigCCurr 200712
Critical Elements of an IROpen Archival Information System Functional
Model
Ingest
DataManagement Access
Dissemination
Storage
Common Services
Administration
Prod
ucer
Management
Con
sum
er
CatalogueMetadata
Archival IP
SIP D
iss emi na t io n
I PCatalogueMetadata
AIP
AdditionalMetadata
Queries
ResultsSets
Orders
From www.sstd.rl.ac.uk/ccsdsp2/isoas/bnsc97/oais1/O
AIS1.PPT
Long-TermPreservation
PreservationPlanning
ReceiveSubmission
QualityAssurance
ExtractMetadata
GenerateAIP
CoordinateUpdates
DataManagementIngest AdministrationArchival
Store Access
Example from OAIS Reference Model, part of Collection
Management
ProvideData
DisasterRecovery
ErrorChecking
ReplaceMedia
ManageStorage
Hierarchy
ReceiveData
AdministerDatabase
ReceiveDatabaseUpdates
GenerateReport
PerformQueries
Packaging,MigrationPlanning
DevelopPreservation
Strategy
MonitorTechnology
MonitorDesignatedCommunity
DeliverResponse
GenerateDIP
CoordinateAccess
Activities
CustomerService
ActivateRequests
AuditSubmission
EstablishStandards,
Policies
PhysicalAccessControl
ArchivalInformation
Update
ManageSystemConfig.
NegotiateSubmissionAgreement
Business Requirement
Business Process
Business Function
19 April 2007 DigCCurr 200714
19 April 2007 DigCCurr 200715
19 April 2007 DigCCurr 200716
19 April 2007 DigCCurr 200717
Electronic Resource
Management
Administration
Notify library personnel of
product
Receive/collect usage data
Activate product
Receive activation information
Supply authentication info (IP, etc.) to
provider
Ensure complete admin info about
product
Order/register/formally sign license
Example from ERMI Model, part of
Collection Management
Business Requirement
Business Process
Business Function
Technicalevaluation
Notify constituentsof product
consideration
� Determine scope of trial
Evaluate trial feedback
Log decision to proceed or
not
Business/Licensenegotiation
Log licensing information
Negotiate license terms
Initiate licensing process
Plan technical implementation
Determine technical feasibility
Consider business
issues: price, interface, archiving,
reliability, etc.
Product review
Notification of impending expiration
New Productconsideration
and trial
Product Implementation
and Maintenance
Renew subscription
Cancel subscription
Determine perpetual
access rights
Update holding status
� Initiate product trial
Make product accessible to
users
Notification of new e-product
Available e-product
19 April 2007 DigCCurr 200719
Systems LogicIdentifying business functions that repeatedly occur across business areas provides a strong indicator of a good services genre candidate
These can be further examined for deriving service genres that are reused
Approach from a systems perspective is service oriented -- logical components that perform a set of operations consistently, lending themselves to reuse across multiple applications
With this it is possible to design for open systems of reusable components that can be mixed and matched to achieve the necessary business logic
19 April 2007 DigCCurr 200720
Development PhasesPhase 1, 2006
Definition of services framework and approachProcess and templates for developing business functions
Phase 2, 2006 - 2007Detailing of library/digital library workflows and their business requirementsProvide Service Usage Models (SUMs) of library activitiesBegin identifying candidate service genres
• Activities that can be discretely automated• Coordinated with JISC/DEST e-Framework
Phase 3, 2007 - 2008Prototype Service Oriented Architecture (SOA) components for identified servicesBegin flexible systems development for production use
19 April 2007 DigCCurr 200721
Working Group MembersLorcan Dempsey, OCLC (chair)Brian Lavoie, OCLCMacKenzie Smith, MITDale Flecker, HarvardKrisellen Maloney, Georgetown UniversityAndy Powell, Eduserv
Peter Brantley, CDLGeneva Henry, DLF Dist. FellowDavid Seaman, DLFJim Michalko, RLGSayeed Chaudry, JHUDan Rehak, Univ. of Memphis
