+TEAM METHODS
+============
+
+Since the team object is supposed to be opaque to widgets, all access
+is via the following API methods rather than direct access to
+properties.
+
+String team.name()
+Bool team.submitted()
+Num team.perpage()
+Num team.totalRecordCount()
+Num team.currentPage();
+String team.currentRecordId() -- simple accessor functions that
+ provide the ability to read properties of the team.
+
+Array team.filters() -- another accessor function, providing access to
+ the array of prevailing filters (which narrow the search
+ results by means of Pazpar2 filters and limits). This is
+ really too complicated an object for the widgets to be given
+ access to, but it's convenient to do it this way. See the
+ "Navi" widget, which is the only place it's used.
+
+Hash team.config() -- access to the team's configuration
+ settings. There is almost certainly no reason to use this: the
+ settings that haven't been overridden are accessible via
+ this.config.
+
+Void team.set_sortOrder(string)
+Void team.set_perpage(number) -- "setter" functions for the team's
+ sortOrder and perpage functions. Unlikely to be needed outside
+ of the "Sort" and "Perpage" widgets.
+
+Queue team.queue(eventName)
+ Returns the queue associated with the named event: this can be
+ used to subscribe to the event (or more rarely to publish it).
+
+Bool team.targetFiltered(targetId)
+