NSDL & Access Management

NSDL & Access Management David Millman Columbia University Jan ‘02

NSDL Project • National SMETE Digital Library (Science, Mathematics, Engineering & Technology Education) (Now “STEM”) • NSF funding ca 90 projects, approx $24 million/year • 3 “tracks” • Collections (~65) • Services (~20) • Core Integration (3) • Operational library by Fall 2002

NSDL Vision Five-year planning target: 1,000,000 users 10,000,000 digital objects (items) 10,000 to 100,000 collections

Active Passive NSDL Core Integration • 1. Engaging community • Community involvement in policy-level guidance & planning (including business models, IP, etc.) • Educational networking/outreach, evaluation... • 2. Providing & supporting technology • An evolving architecture with open interfaces & implementations for an interoperability spectrum • Tightly coupled federation (rich standards) • Looser coupling, with mediation services, e.g. • Harvested aggregations (minimal standards) • Implementation tools, consultation, & support

NSDL Core Integration (cont.) • 3. Operating core services • Registries, repositories, & usage statistics • Collection registry & (raw) metadata repository • Normalized metadata repository (per community standard) • Advanced information retrieval system • Portals (primary, specialized & customizable) • Prototype system to manage intellectual property rights • User database • Authentication mechanisms • A SourceForge-based NSDL Communications Portal • Collaborative software development • List servers, with archiving...

CI Players • Columbia • Cornell • University Corporation for Atmospheric Research (UCAR) • UCSD • UCSB • Carleton College • U Mass • Montana State

Roles of the CI Players • Columbia: Addressing access-rights mgmt & other aspects of a business model for NSDL. • Cornell: Operating core NSDL components for metadata harvesting, based on the Open Archives Initiative (OAI); a normalized metadata registry; the primary portal; special portals; & a portal-tailoring capability. • UCAR: Central office, project mgmt, evaluation strategy; w/ Carleton & Montana St: Data in the classroom;w/ UCSB & UCSD: Tools/methodologies that exploit the “Data Grid,” georeferencing, & other advanced DL techniques;w/ U Mass: Advanced information retrieval (IR).

Intellectual Property Flow • New knowledge is created by IP flow and interconnection • Within and between institutions • Between individuals • Openness and multiple flows create complexity • Heterogeneous environment • Teaching and Research • Commercial development • Creator’s intent • Use determines access • Who you are • What are you looking at • Why you are looking

Input from Authors/Users • What are the necessary/desirable components of a digital rights management system for authors/users? • What type of information and tracking should a system provide? • How should a digital rights management system provide protections/credit for authors as well as accommodate users’ needs for broad access and fair use?

Communities & Restrictions subscribing institution NSDL/CI specify membership in communities Dir specify terms of access U U U U collection U U U U U U U U U U U U U

Attributes . . . Access Restriction Examples Open Research and professional use Personal teaching only Personal teaching and library/course pack distribution Personal educational use only (e.g., an individual student) User Community Examples Everyone All engineering professors Every NSDL user California undergraduates All graduate students Memphis City School District All high school students U.S. State Department All K-8 students Rand Corporation Content and Metadata Match access restrictions with user communities

CI Components U U U NSDL/CI collection U U U U U U U U U U metadata repository (catalog) U portal U U collection central search service U U U U U U U U U U U U U collection profile server U portal U U U U U U rights broker U U U U U U U

CI Access Mgmt • Profile Server • anonymous directory • customized services • authentication on behalf of portal • Rights Broker • attribute hierarchy matching • authentication on behalf of portal • trusted intermediary for collections

Institutional AuthN/Z Assertion NSDL/CI collection profile server collection 3, 4 AuthN rights broker Dir 2 portal 1 collection 5 U U U U U U U U U U U U U

Collection Validates via CI NSDL/CI collection profile server collection AuthN rights broker Dir 6, 7 portal collection 5 U U U 8 U U U U U U U U U U

CI Medium Range Plan AuthN U NSDL/CI U Directory collection U U U portal U U U U U U U U profile server collection AuthN U U Directory access mgmt library U U U rights broker U U U portal U U collection U U U AuthN U U Directory U U portal U U U U U U U U U

CI Short Range Plan NSDL/CI U U collection proxy U U U U portal U U U U U profile server collection AuthN U proxy U Directory access mgmt library U U U rights broker U U U portal U U proxy collection U U U portal

decentralized authentication home institution authenticates attributes specified by central authority common trust model for attribute release anonymous & pseudonymous services portals can specify attributes collections specify attrib requirements Functional Requirements

CI Admin Role • NSDL Central Office • establish policies and standards • community building • Interoperability trust policies • Develop models with publishers • Articulate desired services

end

NSDL & Access Management