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

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
developers_call:minutes20151110 [2015/11/09 14:02] – [1. Development Updates] demiankatzdevelopers_call:minutes20151110 [2015/12/21 17:18] (current) – ↷ Links adapted because of a move operation demiankatz
Line 1: Line 1:
 ====== VuFind Developers Call Minutes: November 10, 2015 ====== ====== VuFind Developers Call Minutes: November 10, 2015 ======
  
-Attending: +Attending: Guenter Hipler, Demian Katz, Claas Kazzer, André Lahmann, Jochen Lienhard, Ere Maijala, Brad Patton
  
 ===== Agenda ===== ===== Agenda =====
Line 25: Line 25:
   * [[https://github.com/vufind-org/vufind/pull/502|#502]], [[https://github.com/vufind-org/vufind/pull/503|#503]] - merged - small fixes/improvements to AJAX tab loading.   * [[https://github.com/vufind-org/vufind/pull/502|#502]], [[https://github.com/vufind-org/vufind/pull/503|#503]] - merged - small fixes/improvements to AJAX tab loading.
   * [[https://github.com/vufind-org/vufind/pull/504|#504]] - merged - Translation fix.   * [[https://github.com/vufind-org/vufind/pull/504|#504]] - merged - Translation fix.
 +  * [[https://github.com/vufind-org/vufind/pull/505|#505]] - merged - Template typo fix.
 +  * [[https://github.com/vufind-org/vufind/pull/506|#506]] - merged - Adds comment to httpd-vufind.conf regarding configuration of Shibboleth with Apache 2.4 (previous comment was 2.2-specific).
  
 ==== 2. Development Planning ==== ==== 2. Development Planning ====
  
 === Improved Author Indexing === === Improved Author Indexing ===
 +
 +André and Demian have been working on getting the indexing and display of author relators right; a solution has nearly been reached. Some progress has also been made on indexing corporate authors separately from non-corporate authors to reduce the amount of MARC-specific logic coded into VuFind's PHP.
  
 === Solr Upgrade === === Solr Upgrade ===
 +
 +Demian has been doing some research into docValues. See comments on [[https://vufind.org/jira/browse/VUFIND-1100|VUFIND-1100]] for more details. He will continue experimenting in the near future.
 +
 +Ere mentioned that National Library of Finland is using docvalues on dynamic fields currently without obvious performance problems. However, they are experiencing some problems on their development instance which they hope will be resolved by the release of Solr 5.4. Demian suggested that it may be wise to wait on merging Solr 5 to master until 5.4 is released so that we can confirm that it helps with performance.
  
 === Javascript Reorganization === === Javascript Reorganization ===
  
 +More tests have been written, and the test suite has been adjusted to allow both Selenium and Zombie.js drivers to be used (for either convenient headless testing, or for the ability to watch the tests executing in a real browser). Unfortunately, there are still some challenges getting the tests to pass consistently -- nothing wrong with VuFind itself but rather with the inherent challenges of web testing. Chris and Demian continue to work on this.
 ==== 3. VuFind 3 Roadmapping ==== ==== 3. VuFind 3 Roadmapping ====
  
-These items were noted down at the VuFind Summit; we should determine which should move to the ongoing development discussionwhich should become JIRA tickets, who should work on what, etc.+Two main topics from Guenter: 
 + 
 +1.) Refactor application to be more component-based. 
 + 
 +2.) Try to build API for some functionality. 
 + 
 +These goals should be approached incrementally. First step: spend two or three months gathering information, getting an idea of what might be possible. 
 + 
 +One example: factoring out covers to a separate module. (Challenge: refactoring while still potentially allowing hooks to other VuFind components like the theme system for retrieving images or the search system for retrieving image-specific metadata). 
 + 
 +Another possibility: creating a stand-alone ILS driver module (potentially with its own DAIA/PAIA API). 
 + 
 +For next yearMarkus (Guenter's colleague) will be making steps in the direction of an API.
  
-Refactoring of Modules +Guenter has built a search API prototype using APIgility. Ere is also working on an API prototype (see [[https://github.com/NatLibFi/NDL-VuFind2/pull/240|here]] -- but note that this is in early stages; handle with care).
-  * Separate modules for search backends? +
-  * How much is too much? +
-  * ILS drivers to a module with DAIA/PAIA interface+
  
-API +Demian favored initially searching for "low hanging fruit" to factor out in simple ways (just reusable code, not ZF2 modules). This should make the core smaller make the more complex problems easier to analyze.
-  * Where? How? +
-  * Simple extension of existing RSS feed? What else? +
-  * Consider on a per-module basis for organization +
-  * Needs to be extendable+
  
-Permissions +André pointed out that components may help spread out maintenance responsibility for the project (i.e. different people could focus on maintaining different components).
-  * Move forward with Demian's email proposal+
  
-Language Namespacing +We also briefly discussed the other items from the [[community:conferences:summit_2015#roadmapping_notes|VuFind Summit roadmapping session]].
-  * Tokenize more, chunk less +
-  * API strings are a problem (EDS) +
-  * Move towards [[http://translatewiki.net|Translate Wiki]]+
  
-Minimum system requirements +Demian will try to find time to move forward on the permissions discussed in an email earlier in the year.
-  * Solr 5? +
-  * PHP 5.5? +
-  * Compare to requirements of Zend Framework 3+
  
-Should we continue to bundle the vendor directory? +We still need volunteers to work on some of the language file improvements.
-  * Leaning towards no +
-  * Install package would be fine +
-  * Git hooks+
  
-More asynchronous loading of inline elements +Demian has made progress on de-bundling the vendor directory (see [[https://github.com/vufind-org/vufind/pull/501|PR #501]]). This can probably be merged soon; Guenter will review.
-  * Holdings Tab +
-  * More Like This+
  
-Investigate new Solr spelling options+Ere is working on asynchronous loading of the holding tab.
  
-Support Solr date range fields (Solr 5)+New Solr spelling options are on André's to-do list (and he will communicate with the swissbib team about their work in similar directions).
  
-Revisit binary availability status in ILS interface.+Demian will investigate Solr date range fields.
  
-Cover generator options +André mentioned that his discussions with Oliver about overcoming limitations of displaying ILS data in VuFind may help inspire improvements to the currently limited and possibly overcomplicated interface for dealing with availability status.
-  * Cache proxied urls +
-  * Pattern-based image retrieval from local file system+
  
-Better documentation about command line tools, LESS, etc.+Demian will investigate the cover generator feature requests discussed at the Summit.
  
 +Demian will work on documenting command line tools.
 ==== 4. Next Call Date/Platform ==== ==== 4. Next Call Date/Platform ====
  
-There has been some renewed discussion about the call platform; there may be a need to find a more Linux-friendly call mechanism without the 10-person limitation of Google Hangouts.+There has been some renewed discussion about the call platform; there may be a need to find a more Linux-friendly call mechanism without the 10-person limitation of Google Hangouts. We attempted a demo of [[https://jitsi.org/|Jitsi]] but were not successful; at this point, it seems like WebEx will continue to work as our primary call mechanism, since all participants were able to call in successfully. However, Jitsi is worth watching as a potential open source alternative, and we may have better results if we can set up a private instance rather than attempting to use the public demo.
  
 Due to the Thanksgiving holiday, November 24 is not going to be a good date for a call. Instead, we will wait for December 8. Due to the Thanksgiving holiday, November 24 is not going to be a good date for a call. Instead, we will wait for December 8.
Line 91: Line 92:
 ==== 5. Other Topics? ==== ==== 5. Other Topics? ====
  
 +None this time.
 ===== Next Call ===== ===== Next Call =====
  
-The next call will be Tuesday, December 8, 2015 at 10am Eastern Standard Time (15:00 GMT).+The next call will be Tuesday, December 8, 2015 at 9am Eastern Standard Time (14:00 GMT).
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
developers_call/minutes20151110.1447077775.txt.gz · Last modified: 2015/11/09 14:02 by demiankatz