About Features Downloads Getting Started Documentation Events Support GitHub

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

VuFind Documentation

Site Tools

You are here: start » developers_call » minutes20150303
Trace:
Warning: This page has not been updated in over over a year and may be outdated or deprecated.
developers_call:minutes20150303

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:minutes20150303 [2015/03/02 17:50] – [1. Development Updates] demiankatzdevelopers_call:minutes20150303 [2015/03/06 14:28] (current) – [Next Call] demiankatz
Line 1: Line 1:
 ====== VuFind Developers Call Minutes: March 3, 2015 ====== ====== VuFind Developers Call Minutes: March 3, 2015 ======
  
-Attending: +Attending: Markus Beh, Filipe Bento, Chris Hallberg, Demian Katz, Tod Olson
  
 ===== Agenda ===== ===== Agenda =====
Line 13: Line 13:
   * [[https://vufind.org/jira/browse/VUFIND-1092|VUFIND-1092]] - This ticket reported a problem in the VuDL module's test suite which was causing Jenkins builds to fail; the issue has been corrected.   * [[https://vufind.org/jira/browse/VUFIND-1092|VUFIND-1092]] - This ticket reported a problem in the VuDL module's test suite which was causing Jenkins builds to fail; the issue has been corrected.
   * [[https://vufind.org/jira/browse/VUFIND-1093|VUFIND-1093]] - This ticket points out that validateCredentials(), which seems like a read-only operation, actually causes a database update; it might be best to change this behavior to avoid future confusion, but doing so will require some significant code changes.   * [[https://vufind.org/jira/browse/VUFIND-1093|VUFIND-1093]] - This ticket points out that validateCredentials(), which seems like a read-only operation, actually causes a database update; it might be best to change this behavior to avoid future confusion, but doing so will require some significant code changes.
 +  * [[https://vufind.org/jira/browse/VUFIND-1094|VUFIND-1094]] - This ticket points out the need for pagination in some of the ILS account related features; when hundreds of results come back (for checked out items, for example) PHP can run into memory limits.
  
 === Pull Requests === === Pull Requests ===
Line 35: Line 36:
  
 === Call Number Normalization === === Call Number Normalization ===
 +
 +Tod has continued work on SolrMarc and Marc4J related to his call number improvements. There will soon be a new Marc4J release, which will be pushed into SolrMarc and will then be followed by a SolrMarc release with Tod's new functions.
 +
 +Demian has opened a pull request ([[https://github.com/vufind-org/vufind/pull/305|#305]]) that significantly simplifies/improves the callnumber-related fields in the Solr schema (as well as their use).
 +
 +Demian will be able to finish his part of the work once SolrMarc is fully updated.
  
 === Code Generators === === Code Generators ===
 +
 +Demian has begun refactoring route generation (see PR [[https://github.com/vufind-org/vufind/pull/307|#307]]) in preparation for building related code generation tools; however, this work is not yet complete.
  
 === Solr Upgrade? === === Solr Upgrade? ===
 +
 +Demian has opened pull request [[https://github.com/vufind-org/vufind/pull/306|#306]] for upgrading to the latest Solr so that we can begin experimenting. There are still SolrMarc compatibility issues that need to be resolved. Also, Solr is moving toward a different model for handling multiple cores; rather than using solr.xml to define them, it auto-detects them based on directory structure. This works against VuFind's style of defining many cores but leaving most of them commented out until needed. Perhaps the overhead is insignificant, but this might be something we need to think about in future. The current 4.x line continues to respect the old solr.xml format, but that will go away in Solr 5.
  
 === 2.4 Release Goals === === 2.4 Release Goals ===
  
 +Demian has begun work on collecting translations for the 2.4 release, so he won't merge any new features to master that add language strings until after the release.
 +
 +After talking to Karen Coombs about her work, it was decided to hold off on merging that until after 2.4, to ensure that all of the related OCLC services are out of beta and have stable APIs before releasing code.
 +
 +That leaves the SolrMarc upgrade and call number issues as the major hold-ups before releasing.
 +
 +We discussed whether to change the default theme from blueprint to bootstrap3 or bootprint3. No objections to changing, but no decision on which theme to use as new default -- Demian will poll the mailing lists.
 +
 +No release date set yet -- March 23 might be a candidate, but we need to wait and see if SolrMarc/Marc4J releases move quickly enough.
 ==== 3. Other Topics? ==== ==== 3. Other Topics? ====
  
 +Tod asked if we could make edition multi-valued in the schema; Demian will investigate whether that can cause any problems.
 ===== Next Call ===== ===== Next Call =====
  
-The next call will be Tuesday, March 17, 2015 at 10am Eastern Standard Time (15:00 GMT).+The next call will be Tuesday, March 17, 2015 at 10am Eastern Daylight Time (14:00 GMT).
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
developers_call/minutes20150303.1425318626.txt.gz · Last modified: 2015/03/02 17:50 by demiankatz