NSDL & Access Management David Millman Columbia University Jan ‘02

Millman—1/2—2 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

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

Millman—1/2—4 NSDL Core Integration 1. Engaging community –Community involvement in policy-level guidance & planning (including business models, IP, etc.) –Educational networking/outreach, evaluation 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 Active Passive

Millman—1/2—5 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...

Millman—1/2—6 CI Players Columbia Cornell University Corporation for Atmospheric Research (UCAR) –UCSD –UCSB –Carleton College –U Mass –Montana State

Millman—1/2—7 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).

Millman—1/2—8 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

Millman—1/2—9 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?

Millman—1/2—10 Communities & Restrictions collection subscribing institution U U U U U U U U U U U U U U U U U NSDL/CI Dir specify membership in communities specify terms of access

Millman—1/2—11 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 EveryoneAll engineering professors Every NSDL userCalifornia undergraduates All graduate studentsMemphis 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

Millman—1/2—12 CI Components collection U U U U U U U U U U U U U U U U NSDL/CI U U U U U U U U U U U U U U U U U U U U U U U U U U U collection metadata repository (catalog) central search service profile server rights broker portal

Millman—1/2—13 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

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

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

Millman—1/2—16 CI Medium Range Plan collection U U U U U U U U U U U U U NSDL/CI collection profile server rights broker portal AuthN Directory U U U U U U U U U U U U U AuthN Directory U U U U U U U U U U U U U AuthN Directory access mgmt library portal

Millman—1/2—17 CI Short Range Plan collection U U U U U U U U U U U NSDL/CI collection profile server rights broker portal U U U U U U U U U U U U U AuthN Directory access mgmt library portal proxy

Millman—1/2—18 Functional Requirements 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

Millman—1/2—19 CI Admin Role NSDL Central Office –establish policies and standards –community building Interoperability trust policies Develop models with publishers Articulate desired services

Millman—1/2—20 end