NSDL Documentation Wiki

Announcement: The operation of NSDL has been transferred to ISKME's OER Commons (effective December, 2014) - Read the news release.

This documentation describes the policies, procedures, and services that existed while NSDL was operated by UCAR.

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



What's Happening

See it in Action

Latest Releases

SMS v1.2.9

Development Team

  • Tamara Sumner, Executive Director and Associate Professor
    • DLS, Institute of Cognitive Science - University of Colorado at Boulder
  • John Weatherley, NSDL Technical Lead
    • DLS and NSDL at UCAR
  • Sharon Clark, Web Developer
    • DLS and NSDL at UCAR
  • Lynne Davis, HCI Engineer and Instructional Designer
    • DLS at UCAR

Get Involved

  • For suggestions, questions, and more information, please send your inquiry to NSDL via the contact form


  • Overview - Overview of the SMS technology including how to harvest the benchmarks using the Open Archives Initiative Protocol for Metadata Harvesting.
  • Javascript API - The JavaScript API lets developers insert interactive Strand Maps into Web pages and place custom content into the maps.
  • CSIP REST API - The Concept Space Interchange Protocol (CSIP) REpresentational State Transfer (REST) API lets developers search and navigate objects and visualizations in the the Strand Map information space. Developers can access objects in the concept map space in number of formats including XML, OWLLite, SVG, PDF, PNG, TIFF, and JPEG.
  • Resource Alignment - How to align resources to benchmarks so they will be discoverable from the Science Literacy Maps.
  • Technical Training - All available technical training documentation including an FAQ.



  • Javascript enabled browser


  • Requirements are dependent on intent. Since the API is called from a central location on NSDL servers, it is possible to make a functional interface with a server to host the webpage, HTML, JavaScript, and CSS. More complex functionality may require a server-side web technologies and/or a database. For more information see theSMS JavaScript API implementation instructionsand theexample code.

Additional Information