SCORM-NSDL Workshop Persistence and Reuse

- 2 - Persistence and Reuse The Problem Educational materials are expensive to create. Over the past 25 years, the NSF and others have funded numerous projects that have developed excellent educational materials that have been used once or twice and then abandoned. What can be done?

- 3 - Reuse and Persistence Reuse Developer (commercial or not-for-profit) creates materials and wishes that they will be used by in many contexts. Persistence Teacher uses the same materials repeatedly (perhaps in one class per year) and wants to be confident that the materials will continue to perform as expected.

year Persistence What can a publisher or individual developer do to minimize the risk of technical obsolescence over 10 years? Choice of file formats? Identification and packaging? Labeling (metadata)? Internal checks and validation tests? What about dynamic content? Regular migration to new versions of software?

- 5 - NSDL Repository: Discussion Items Federation(s) Should we support selected federations (e.g., SCORM)? Object model Should we support selected packaging standards (e.g., METS, IMS, MPEG-21)? Should we support a persistent identifier system other than URLs and OAI identifiers (e.g., Handle, DOI)? Persistence How can our technical decisions enhance persistence and reuse?

- 6 -