Presented by
Gary Marchionini
University of Maryland
march@oriole.umd.edu
Theses and Dissertations Other Projects Processes/Approaches Theories/Models \ / \ / \ / FRAMEWORK
Theories
Aspects of DLs
Evaluation Process
Sense-Making
Work Practice
Lifecycle
--> Content
--> Using
--> System
--> Management
Who/how creates/ed
Who/how selects/ed
Who/how organizes/ed
(For these, context is related to goals and policies)
Why
How understandable
Coverage -- completeness, depth
Bib/fulltext/multimedia -- representations
Metadata, catalog, finding aids
Taylors dimensions: accuracy, currency, validity
Search -- Value-added Retrieving Share Find Communicate Discover Copy Browse Republish Extract Create Store Display Sort Organize
Functionality -- System-dependent Interface Openness Speed Durability Reliability Where can be accessed from Robustness Maintenance User-orientedness Staff level, skills, number Algorithms Capacity Uncertainty handling Security Scalability Expense Extensibility (Performance)
Reference
Training
Translate
Publish
Copy
Summarize
Deliver
Financial Management
IPR Management
Help
Bibliographies
Filter
SDI
Indexing
Cataloging
Perserving
Achiving
Annotations
Who, where
Job profiles
Location
Organization:
Work habits Cohorts Institutions Goals Cultures <---------------- Funders | Size Centralized/Decentralized | Norms Memory | Profitability | Collaboration: | Coordination Interaction | Communication Competition Proximity | Critical mass Conflict | Conflict resolution Relationships | Users: | Empowered | Goals Needs | Motivation Stakeholders ------------- Roles/relationships --> Benefactors Memory
Control
Open/closde
Accountability
Responsiveness
Flexibility
Cost
Staff needed
Dynamics
Changeability
Overhead
Policies: Access, Charging
Planning
Risk Management
Options
Resources
Style (e.g., hierarchical)
Structure
Centralized/decentralized
Status
Pay
Authority
Compare, improve systems, design process
Promote use, acceptance
Understand impact
Understand viability
---cost effectiveness
---DLs
Satisfy management (accountability)
Carry out: IR, HCI, Hypertext, design, DB, MM ... research
Check goals, usability
Verify, validate design/requirements
Evaluate if service, use, etc. (or, indicators/metrics for service and use, etc.) are met/supported
Performance Purpose specific --Learning Knowledge/technology transfer Adoption Adaption --------- Viability Rewards and punishments Participation Profits/benefits --------- Goal migration | Series of failures accumulating Change in practice | Meta issue: levels Matrix (from purpose, goals, objectives) Or tree? Correlations?
Acceptance of DL by organization with respect to goals
Acceptance by users with respect to goals
Effectiveness of system with respect to tasks
Ability of users to understand system during use (fn: knowledge, ...)
Traffic
No. of users (people, institutions)
No. of searches, links
Time on task, errors
Substitution effects (e.g., for paper)
Complementary effects
Repeated use
Satisfaction
Amount of help needed, training needed
Unintended uses/serendipity
Time sinks (where time gets used, wasted)
Time
Instruments to help
Tutorials on ...
(The above three items are needed for various approaches)
Sustainability
Predict/test
---For various time spans
---On users, organizations
TIME: 20-50 yrs. | (very long) | | 10-20 yrs. | (long term) | | 5-10 yrs. | (med. term) | | 3-5 yrs. | (short term) | | year | | semester | | session/day | | ----------------------------------------------> STAKEHOLDER: Indiv. -> Small group -> Large group -> Society (e.g., student -> class -> school -> field -> world)
Last Updated: Feb. 11, 1997