You are here: Home » About » Software » Repository

Repository

The repository is responsible for storing content in Connexions. It currently houses content from countries around the globe, containing educational material for all ages.

Retrieval and display

Each version of a content object has a URI of the form http://cnx.rice.edu/content/<id>/<version>/ where <id> is the unique id of the form m##### for modules and col##### for collections, and <version> is the version identifier. For example http://cnx.rice.edu/content/m11617/1.2/ identifies version 1.2 of the module m11617. The most recent version of an object is available through a URI of the form http://cnx.rice.edu/content/<id>/latest/.

Note: Retrieving a collection URI sets a browser cookie for that course. From that moment on (until the cookie expires, is removed, or is replaced), the user (or rather, the user's browser) is in the "context" of that course. In the context of a course, any module included by that course will be displayed with the appropriate customizations such as display options, annotations, and links. The actual module in the repository is not altered, and is accessed via the same URI. It is only the presence of the course cookie that causes the module appearance to be changed.

Search

The repository provides a full text search function for finding content. The search can be narrowed to show only module, collection, or author results, and can be narrowed by subject. There is also a browse feature that searches metadata (ID, title, author, keywords, and so on) for results. For more help on finding content, see our Finding Content page.

Version control

The repository stores the complete history of all published content so that users can access any version, previous or current. Some important features of Connexions repository versioning are:

  • the entire content object (including metadata and any associated files or data) is versioned
  • each version of a content item is always accessible both internally as a first class object, and externally via a URL
  • the version history of an object (who published each version and the "change log") is always accessible
  • there is a special method for retrieving the latest version of an object in case a users wishes to obtain the most recent version, regardless of its version number.