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.
77 Superuser field should not be mandatory.
79 In end-user record, username and password should not be
80 mandatory any more. (Perhaps it should be mandatory to have at
81 least one of u/p, IP range, hostname, etc.)
83 Add an "Act As" link on the Edit Library page.
85 When making a new user-access record, default the displayName
86 to that of the ibrary that owns it.
88 Add a capability facet to MKAdmin. The right way to do this is
89 to refactor the current hardwiry facet code to be more
90 data-driven, then add a configuration element to include
91 capabilities as a facet.
93 Make MKAdmin able to filter target list on whether we have
94 access: that is, to targets that either are open-access or we
95 have credentials or an IP proxy for.
97 Provide "select all targets" to they can be added.
99 Add batch edit on all targets found by the current search.
101 We want a way to let customers change the Index Data branding
102 of the MKX front page, as well as the logo at top left of the
103 MasterKey UI itself. Along with that, we could let them change
106 Indent second and subsequent lines of long facet names
108 Keep selected facets when narrowing by search, etc. NOT URGENT
110 Lose the search function and the A-Z list from the Categories
111 and User Access tabs.
113 Lose ALL the left panel options for the categories tab.
115 In the library list, rename "Act as this user" to "Act as".
117 We need only one add-new-field name/value pair at the bottom
118 of the screen, not three.
123 Lose Target Origin and Type columns from target list.
125 Lose the A-Z list from all tabs.
127 Remove "changed in last NUMBER days" from search form
129 In the target list, get rid of "Show record", make the target
130 title a link to the edit page, and discard the edit column
133 Lose the Create Target facility (from left panel and bottom
136 Remove the the Edit facility and the New button from the
137 categories tab. Keep the category_id column, for some
138 reason. (Although I bet if I removed it neither Seb nor D
141 Make the User Access tab display the single end-user record
142 for editing immediately. Remove everything that doesn't need
145 D will get back to me with a detailed specification of which
146 reports to include in the Reports tab.
148 In the edit page, lose all the top icons.
150 D will give me a list of target fields to retain in the
151 MKAdmin-- edit page. It may be just target name, categories
154 Remove all help from MKAdmin until Seb sends help texts that
157 BIG CHANGE: lose the edit-form distinction between inherited
158 and local values. Have a single column of editable values and
159 override only those that are actually changed.
164 Get Charles to remove the testing proxy-IPs from open-access
167 We need additional image-URL fields in our records -- in the
168 connector framework, in the Torus record's capabilities and
169 elsewhere. Figure out what's needed, and who needs to do it.
171 Fix the Torus's timed refresh to run on its own in the
172 background, rather than waiting until the next time a request
173 is made after the refresh-time has expired.
175 Can the IRSpy toroid be made to return a meaningful capability
178 Metasearch all targets and see what happens. Figure out why it