About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
developers_call:minutes20120221

This is an old revision of the document!


VuFind Developers Call Minutes: February 21, 2012

Attending:

Agenda

1. New/Updated JIRA Tickets

2. VuFind 1.3 Release

The 1.3 release went out on time; no major bugs reported yet.

3. VuFind 2.0 Update

Demian has completed basic single-record export support. This is now done more generically than before – all the behavior (HTTP headers and optional redirect-to-service) is handled via export.ini and generic record driver templates, which should make adding new export options simpler. It will still be necessary to add bulk export support (none of the bulk logic is in 2.0 yet), but this should be simpler and less redundant than before due to the new configuration-driven model.

VuFind 2.0's install process is now in place. The old platform-specific tools are gone in the interest of making installation more universal. A command-line PHP tool auto-configures the Apache configuration to help get web access in place. A web-based “install wizard” then takes over, creating the database, auto-configuring some items and providing tips on solving common problems. Currently the installer is English-only; there is a lot of complex language that made translation difficult. If we need installation in multiple languages, perhaps we should approach this in the same way that we did help screens.

Demian has begun implementing “local override directory” functionality – it is possible to create a directory that contains configuration, language and library files that override the VuFind core. You can have multiple override directories that are set to work with different Apache aliases in order to have different configurations of VuFind served from a single copy of the software. There are some limitations: themes can't fit into this model because of the way their resources (images, CSS, etc.) are served; some Zend components (controllers, models) don't easily lend themselves to this because they allow only single source directories, not search paths. Do we hack Zend core to allow overriding, avoid these mechanisms where possible or live without override capabilities for these things? Perhaps safest to defer on major decisions until Zend Framework 2 is available.

The [Extra_Configs] section of config.ini has been eliminated as it is no longer appropriate given the local override directory mechanism. It has been replaced by a [Parent_Config] section which allows you to specify a path to a “parent configuration” from which your current configuration inherits. This allows you to chain together multiple configurations if you need to – you could create a central shared configuration and then just override a handful of settings in each local directory. Another setting within the [Parent_Config] section allows you to specify which sections need to be completely overridden and which need to be merged with the parents. Obviously, all of this is optional and most people won't need to use it – but it's available if it's needed.

The translation routine has been updated to support two new features:

  • Tokens within strings, to allow sentences to be properly formatted in multiple languages (i.e. “showing results start - end of total”).
  • Default values may be provided to use if no translation is found; this will allow better namespacing of the language files (i.e. facet_format_Book with default value of Book).

There is still a large amount of work necessary to actually reformat the existing translation strings to take advantage of these features.

Chris and Demian took a look at the latest ZF2 beta release; it will definitely be a lot more than just a drop-in upgrade to switch from ZF1 to ZF2 – further investigation is deferred until more documentation is available.

Demian has begun work on porting the cart and bulk action logic to VF2; everything is being rewritten to allow mixed record sources (i.e. not just Solr, but also Summon, WorldCat, etc.). As part of this work, the logic for loading multiple records from multiple sources has been rewritten for greater efficiency (when possible, we load all records from each source as a batch instead of loading things one record at a time).

4. New Mobile Theme

No news.

5. VuFind Developers Summit 2012

The next in-person VuFind meeting at Villanova will be October 15-16, 2012. If you are interested in attending, please fill out this survey.

6. Other Topics?

Next Call

The next call will be Tuesday, February 21, 2012 at 11am Eastern Standard Time (GMT - 5:00).

developers_call/minutes20120221.1329333516.txt.gz · Last modified: 2014/06/13 13:13 (external edit)