3 Make a demo widget that displays an image, like the "From the
4 Digital Archive" panel of our Toronto Digital Library demo.
6 Make a widget demo that displays the top-hit full record
7 rather than a list of summary records. This can be used to
8 pull in Wikipedia text to make the bulk of a topic page.
10 Make an Amazon cover-art widget.
12 Do target selection by UDB rather than ZURL. Needs SP changes.
14 We will want a facets-only widget, e.g. to list top authors
16 Visualisation widgets e.g. pie-chart of authors, bar-graph of
17 records Generate embedded SVG? Does that even work?
19 Make am MKWS/Fresco demo by embedding widgets in our Koha
20 installation. Get Wolfram to do this, and find out which parts
21 of the process are cumbersome for him.
23 Write about interesting new widgets on the Index Data blog.
26 * Mainly a marketing thing on mkws.indexdata.com
27 * May also have a role in widget creation in MKAdmin
30 * Separate objects for each widget
31 * Translucent configuration
32 * Decouple using publish/subscribe
33 * Managed widgets held in the Torus
34 * 3rd party widget platforms
36 Write integration guides for various third-party CMSs.
38 In the widget builder, we want to expose capability
39 information (from ZeeRex or a Torus record) in a
40 human-consumable form: "this target can sort by recency", that
43 Auto-widgets should be able to include limits (as a full set
44 of MK2-like widgets does in order to implement facets).
46 Auto-widgets should be able to include filters (as a full set
47 of MK2-like widgets does in order to implement the Target
48 facet). This can be used to implement target categories as
49 well as the current cruder target-selection-by-ID facility.
51 In the widget builder, we should be able to filter the targets
52 available to the widget on the basis of what requirements the
53 widget has, e.g. ability to sort by recency. The capability
54 facet in MKAdmin may suffice for this.
56 Check library selection by hostname works for MKWS.
58 The widget-builder widget (WBW) should have a Save button that
59 is customised by a callback, so that the widget in question
60 can (for example) be copied into the clipboard, pasted into a
61 nominated div, saved to a database or whatever.
63 Allow debug() to be customised by setting a callback function
64 that is passed the string rather than just giving it to
67 Create a logging widget which displays the output of debug().
69 Add library selection by secret key as an alternative to
70 selection by user/pw. This is appropriate for
71 security-conscious customers to embed in their own CORS-aware
72 Apache2 configuration.