This roadmap outlines future development of Exhibit 3.0 to spark community discussion about where the platform should go and point developers to tasks that need your help.
Exhibit 3.0 Scripted Mode
- Enhance documentation of the current API for writing new views and facets as more examples are authored for Exhibit 3.0 and patterns emerge.
- Add a progress bar to appear while Exhibits are rendering to provide a visual indicator to users (also applicable to Staged mode).
- Reach parity between features available in Exhibit 2 and Exhibit 3.0. See https://github.com/zepheira/exhibit3/wiki/Previous-Release-Comparison.
- Move all SIMILE projects over to a SIMILE GitHub repository.
Exhibit 3.0 Staged Mode
- Explore capacity: How many Exhibits can a Backstage instance support?
Add bookmark UI feature for Staged.
Explore caching to help reduce processing latency:
- With the limited number of ~100K item datasets we used, we observed a rule of thumb of approx 1.5G of RAM per dataset when using the in-memory database. At the current time, we don't have any capacity information for the on-disk database.
Reset Backstage session when exhibit HTML is edited after session is initialized.
Exportability of subsets of staged Exhibits
Testing of better or alternate means of associating the exported HTML+RDFa data with an exhibit should be evaluated and reevaluated over time as search engines adopt new conventions.
- Consider pre-generating and then caching without expiration the first page response, which can take several minutes currently while waiting for data to completely load.
- Caching query responses in general may speed up responsiveness.
- Provide a service that details which output formats are available in an installation.
- Add more output format options.
- Document for developers how to write more output formats.
Make Backstage stateless.
Add pagination for Exhibit 3.0 Staged mode.
Reach parity between features available in Exhibit 3.0 Scripted and Staged modes. See https://github.com/zepheira/backstage/wiki/Staged-Compared-to-Scripted.
- Lightly document where to find extension points in the code. Because input is a one-time operation, providing an input API seems less important.