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:minutes20120110

This is an old revision of the document!


VuFind Developers Call Minutes: January 10, 2012

Attending:

Agenda

1. New/Updated JIRA Tickets

  • VUFIND-279 - The addition of a user phone number field to the database was proposed here.
  • VUFIND-421 / VUFIND-441 - Some updated files have been attached to these tickets, which deal with hierarchical navigation of VuFind records.
  • VUFIND-427 - Upgrade tools for the 1.3 release are complete, so this ticket has been closed.
  • VUFIND-480 - Demian has submitted patches proposing schema additions for Solr dynamic fields; he will commit these in time for the 1.3 release.
  • VUFIND-485 - This minor Unicorn driver improvement has been committed.
  • VUFIND-486 - This minor Voyager driver bug fix (involving character encoding in the volume field) has been committed.
  • VUFIND-487 - This tool exports MARC records from the VuFind index. Demian will try to find time to polish it and add it to the trunk eventually.
  • VUFIND-488 - The Summon API has a new parameter for dealing with user language preferences; this ticket is a reminder to implement support in VuFind.
  • VUFIND-489 - Certain characters in the marc_error field of the Solr index would occasionally cause RSS fields to fail to generate; this ticket includes a patch to fix the problem (which has been committed to the trunk).
  • VUFIND-490 - If a user created a list without naming it, it was always called “My Favorites” regardless of language setting; this ticket proposes a fix, which has been committed to the trunk.
  • VUFIND-491 - The marc.properties file does not include a “first” specifier to limit the number of editions values sent to the Solr index. Since the Solr schema's edition field is not multi-valued, this can cause fatal errors. A similar issue exists for the author-related fields. Since the MARC fields involved are never supposed to be multi-valued, this shouldn't be a problem in theory… but bad MARC records exist in reality. Do we want to make VuFind more fault-tolerant, or do we want to retain the current configuration to help users identify potential problem records?
  • VUFIND-492 - It appears that VuFind's .DEB package does not work under Debian (it was developed/tested under Ubuntu).
  • VUFIND-493 - This ticket proposes some XSLT code for breaking up comma-separated values in XML fields.
  • VUFIND-494 - The “hide_holdings” setting in config.ini now applies to search results as well as record views; this ticket includes a patch (which has been committed to the trunk). Note that this also improves the behavior when holdings information is unavailable – search results will now hide the “Location:” and “Call Number:” fields rather than leaving them blank/Unknown.

2. VuFind 2.0 Update

We will probably have to raise the base requirement to PHP 5.3 in order to take advantage of late static bindings; this requirement will also probably exist if we decide to upgrade to the soon-to-be-released Zend Framework 2.0.

Demian has once again refactored the search code in an effort to make the organization more logical. To test the latest arrangement, he has begun implementing non-standard search modules (Authority, Reserves, WorldCat). So far the new system works well – it is much easier to implement a whole new search interface than it used to be. However, more work needs to be done to make the record views that correspond with these searches a little more straightforward and less redundant.

The MyResearch area is also coming along nicely, with most of the list-related functionality now complete (apart from the need to add some fields to the database to allow sorting across multiple record sources).

More unit tests have been built, and code coverage should be improving; however, there are currently problems on the continuous integration server that are preventing PHPUnit from generating coverage reports correctly; Demian is investigating.

3. Hierarchical / Archival Data in VuFind

4. New Mobile Theme

5. Other Topics?

Next Call

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

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