UserPreferences

ScholarsBox/AppendixDocFipse2004


I'm in the process of revising this Appendix, making /NotesAndComments.

Appendix A: Functional and Technical Overview of the Scholar’s Box

There is much recent interest nationally in building new connections—organizationally and technically—between the domains of digital libraries and educational technologies. At present, a substantial gulf exists between these domains, to the detriment of libraries and museums on the one hand, and teachers and learners on the other. This gulf reflects specific technical barriers. Digital library and museum collections are inaccessible to the authoring tools and learning management systems being used to develop online educational services and course materials; they exist within different standards regimes and are managed and delivered with incompatible protocols. In addition, there are important cultural and organizational issues at work as curatorial professionals in libraries and museums, educational technologists, and teachers and administrators define and adjust to new roles and responsibilities. This appendix provides a short functional introduction to the Scholar’s Box tool, reviews interoperability issues, describes its abstraction framework, and provides a brief architectural overview.

The Scholar’s Box project seeks to translate teachers’ current practice into the digital realm so that teachers can work with the wealth of digital cultural objects available from museums and libraries. We seek not only to do this for individual teachers but for groups of teachers and/or content and collection experts working together to create supplementary curriculum resources. The Interactive University Project is building the “Scholar’s Box” tool that enables faculty, students, and the public to create, manipulate, annotate, and share personal collections of digital cultural objects gathered from multiple digital repositories. We are building both a Scholar’s Box tool as well as an abstraction framework that defines functionality and APIs for other possible implementations.

http://img19.photobucket.com/albums/v58/rdhyee/Fipse_Image1.jpg

DIAGRAM 1: Screenshot of the Scholar’s Box prototype. The Box is in the background, with larger views of each resource to illustrate the variety of collections and objects accessible through the Scholar’s Box. Teachers and students can search for or browse digital objects to gather into a Digital Box to build a personal collection for use in teaching, research, and building curriculum resources. Prototypes of the Scholar’s Box tool have already been implemented as both web-based and desktop-based software. We are first focusing on allowing users to search for and gather images from multiple repositories, to sequence and annotate the images, and then to generate a variety of products from these images (e.g., HTML albums, METS documents, SCORM-encoded learning objects). Work has also begun on the abstraction framework for the Scholar's Box that is essential to implementing the Scholar's Box easily on multiple platforms. Prototypes are being generalized to handle media other than images.

Interoperability: Building Connections between Technology Worlds

The Scholar’s Box software helps to address important interoperability issues at the intersection of four information technology domains: digital libraries and repositories; educational technologies and learning management systems; web syndication and portal technologies; and desktop applications and structured content authoring tools.

Enhancing interoperability among digital libraries, software applications, and data formats of content has been a time-honored strategy for increasing the utility of digital collections. A central issue in building the Scholar’s Box tool has been the initial data formats for digital content that the Scholar’s Box supports. There are many data formats that would be useful for the digital cultural community. One factor in our selection has been ease of development; another is greatest leverage in the educational community. Because we would like to enhance the exchange of materials among four communities—the digital library world, the educational technology world, the world of cutting-edge content syndicators on the web today, and the world of web content authoring tools—we are writing software adaptors for the following three formats, all of which are XML formats for structured data METS (for digital libraries and repositories) [3]; SCORM, IMS-Content Packaging (IMS-CP), and IMS-Metadata (IMS-MD) (for educational technologies and learning management systems); RSS (for web syndication and portal technologies) [4, 7]. In addition to technical interoperability, the Scholar’s Box project will help to address issues of “cultural interoperability.” Through its strong school-college partnership, the project will build new understandings and relationships among faculty, curatorial professionals, educational technologists, and K-12 teachers, librarians and district leaders.

The Abstraction Framework and Architectural Overview of the Scholar’s Box

The Scholar's Box abstraction framework allows the separation of logic and intelligence common to all implementations from implementation-specific details. This document will guide the implementation of the Scholar’s Box tool in other environments, enhancing its adoption and adaptability across institutional and technical contexts. In its most general formulation, the Scholar's Box allows users to (1) gather digital objects (of varying formats) and organize them into collections, and (2) transform them into other digital objects (through services). The Scholar's Box does not, of course, magically handle every format and implement every service. Rather, it can be systematically extended (programmed) to handle a new format or service. This framework is geared to enable practical interoperability in a sea of data heterogeneity as seen from the end-user of cultural digital objects.

Specifically, the Scholar's Box allows for the aggregation of complex (multipart) and simple objects; disaggregation of collections and complex objects into constituent pieces (because people often want pieces); reassembly of parts from multiple source objects into new objects; the association of metadata with digital objects; the interconversion of digital object types and their metadata; and the implementation of crosswalks among metadata systems. The disaggregation and reformation must take place while preserving key aspects of the original context of the materials. Although the Scholar's Box can conceivably be programmed to handle arbitrary transformation of digital objects, it is not meant to replace specialized authoring or viewing tools but work with them to leverage their functionality.

http://img19.photobucket.com/albums/v58/rdhyee/Fipse_Image2.jpg

DIAGRAM 2: The simplified example above shows a collection of digital cultural objects from multiple sources in the Scholar’s Box with a drop down list of possible services that users might apply to materials in the box.

We seek an architecture that is flexible, extensible, and portable to support the functionality of the Scholar’s Box. Diagram 3 presents a schematic view of this architecture. Content flows into the Scholar’s Box from two types of sources: digital libraries and archives (6 on the diagram) and content from individuals or teams of scholars (7 on diagram). We distinguish between these two categories because the architectures required to support them are different. Digital libraries and archives typically are backed by full databases holding materials with their associated metadata, accessible through persistent handles. Materials produced by individual faculty and departments may need various forms of structuring to be made accessible.

End-users will have access to the Scholar’s Box through the traditional browser interface (HTML or DHTML) (1 on diagram 3). However, the Scholar’s Box will also be designed to interface with computer agents. Programs (desktop and web applications) that use an XML-RPC [5]/SOAP [6] interface will be able to communicate with the Scholar’s Box (2 on diagram 3). Output and input will be carried in XML packets.

A key element of the design of the Scholar’s Box is to determine the type of content that will flow in and out of the Scholar’s Box: what type of scholarly materials (inputs) have to be handled and what do users want to be able to produce (products) from the input materials (3 and 4 on diagram). Internally, the Scholar’s Box is an XML data store, with an extensible workflow system that enables input materials (which themselves may not be XML) to be transformed into desired products (5 on diagram). Such workflow is instantiated as an extensible set of tools that act on the data. Although the detailed design of the Scholar’s Box remains in process, there are good models from which to learn. In particular, Groove [1] and Jabber [2] illustrate how XML can be successfully integrated, routed, and manipulated at various places in a technology architecture. We believe the movement and manipulation of XML based content packets will be a critical issue for the development of the Scholar’s Box tool.

http://iu.berkeley.edu/rdhyee/Filer/filetree/2003/architecturediagram_2003_10_14.jpg

DIAGRAM 3

References

  1. Groove. http://www.groove.net/

  2. Jabber. http://www.jabber.org/

  3. Metadata Encoding and Transmission Standard (METS). http://www.loc.gov/standards/mets/

  4. RSS 1.0: The New Syndication Format. http://www.webreference.com/perl/tutorial/rss1/

  5. XML-RPC Home Page. http://www.xml-rpc.com/

  6. Box, D., Ehnebuske, D., Kakivaya, G., Layman, A., Mendelsohn, N., Nielsen, H.F., Thatte, S. and Winer, D. Simple Object Access Protocol (SOAP) 1.1: W3C Note 08 May 2000. http://www.w3.org/TR/SOAP/

  7. Winer, D. RSS 0.92, 2000. http://backend.userland.com/rss092