Skip to content

Roadmap

Michael Cummings edited this page Aug 5, 2016 · 5 revisions

Current Release (m40_001) August, 2016

This release focuses on upgrading the Ubuntu server from Ubuntu 12 to 14.4 and upgrading Oracle to Release 1.8, both of which are necessary. The procedure has been completed on three developer servers and the Ubuntu 14.4 test server.

Remaining work entails

  • test whether we should use SQL-Lite or Postgres for the default database
  • update our semi-automated deployment script (fabric),
  • establish a new Ubuntu 14.4 production server,
  • deploy the system from a development server to the new test server,
  • deploy the system from a development server to the new production server, and
  • redirect traffic to the new production server.

This work should be complete by mid-August.

Near Term (m41_001) mid-August, 2016 - December 2016

We have tentatively assigned a few issues to milestone m41_001.

Those issues describe work that would need to be done to accommodate the changes to the way Gelman periodicals are cataloged as proposed by the Continuing Resources group. The coding changes would be relatively complicated. These issues should be given priority.

The majority of other pending issues are enhancement ideas, represented by the tag 'consider' and would fall under longer term work.

Longer Term

The consortium libraries plan to migrate from Voyager and Summon to Alma and Primo, with an implementation target of Summer, 2018. The most active implementation period will be November/December 2017 through August, 2018.

Primo

  • We will be able to have a bento search interact with the Primo search API and return results scoped to articles vs items in the library catalog, just as we do now with Summon.
  • Based on information provided at the ExLibris Users group meeting, it appears that the Primo discovery catalog will be much better, and more customizable than Summon. Primo will manage functions currently handled by the MyAccount and CLS fuctions through WRLC. A likely scenario is that there would be little advantage to link users from Primo to a custom catalog view like launchpad.