Differences

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

--- developers_call:minutes20150331 [2015/03/26 14:16] – [1. Development Updates] demiankatz
+++ developers_call:minutes20150331 [2015/04/08 18:48] (current) – demiankatz
@@ Line 1: / Line 1: @@
 ====== VuFind Developers Call Minutes: March 31, 2015 ======
-Attending:
+Attending: Chris Hallberg, Filipe Bento, Jochen Lienhard, Chris Delis, Tod Olson
 ===== Agenda =====
@@ Line 12: / Line 12: @@
   * [[https://vufind.org/jira/browse/VUFIND-1099|VUFIND-1099]] - This ticket proposes a better workflow for the new items module (which currently requires a user to fill out a form before seeing any results); due to the potential complexity of the new items form, this may require significant work, but for the moment, we should at least collect ideas on this ticket.
   * [[https://vufind.org/jira/browse/VUFIND-1100|VUFIND-1100]] - This ticket points out a new data storage mechanism (docValues) in Solr which we may be able to utilize for improved performance; please comment on this ticket if you have opinions on how best to do this.
+  * [[https://vufind.org/jira/browse/VUFIND-1101|VUFIND-1101]] - This ticket proposes a CLI tool to force a Solr commit; one has been added (util/commit.php).
 === Pull Requests ===
@@ Line 26: / Line 27: @@
   * [[https://github.com/vufind-org/vufind/pull/329|#329]] - merged - Improved the way the Database authentication module creates users, to reduce redundant logic and centralize user creation in the table object; note that the implementation committed to master is somewhat different from the one originally proposed in this PR.
   * [[https://github.com/vufind-org/vufind/pull/330|#330]] - closed - This PR proposes a CLI tool to manage language file synchronization; due to redundancy/overlap with existing tools, it has been closed without action; however, we expect a new PR that's more fully integrated and less redundant to appear soon.
+  * [[https://github.com/vufind-org/vufind/pull/331|#331]] - in progress - This PR adds some rel="nofollow" attributes to links in the bootstrap3 theme to improve search engine crawling behavior. We'll merge it soon, but feedback would be appreciated.
+  * [[https://github.com/vufind-org/vufind/pull/332|#332]] - in progress - This proposes some improvements to the Spanish translation; Spanish speakers are encouraged to review/comment.
+  * [[https://github.com/vufind-org/vufind/pull/333|#333]] - merged - A fix to the way VuFind deals with colons when preprocessing user search queries; colons inside double quotes are now ignored, since stripping them out can cause phrase searches initiated by alphabrowse to fail unexpectedly.
+  * [[https://github.com/vufind-org/vufind/pull/334|#334]] - merged - bug fix to VoyagerRestful ILS driver storage retrieval request functionality.
+  * [[https://github.com/vufind-org/vufind/pull/335|#335]] - in progress - a new configuration for the Voyager ILS driver to help improve status displays.
 === 2.4 Release ===
@@ Line 34: / Line 40: @@
 === Call Number Normalization ===
+No news.
 === Solr Upgrade? ===
+There hasn't been any further discussion on the solrmarc-tech list since the last call.
 === Improved Tag Interface ===
@@ Line 43: / Line 53: @@
 === Labeling of "My" vs. "Your" ===
-Pull request [[https://github.com/vufind-org/vufind/pull/227|#227]] (designed to normalize some inconsistent language in the UI) has been floating around for quite a while but no action has been taken; we should come to a consensus and do something about it.
+Pull request [[https://github.com/vufind-org/vufind/pull/227|#227]] (designed to normalize some inconsistent language in the UI) has been floating around for quite a while but no action has been taken; we should come to a consensus and do something about it. No decisions this week.
+=== VuFind Solutions GitHub ===
+We have several new features lined up that we often debate whether or not they should be part of master or not (e.g. the offcanvas menus, [[https://github.com/vufind-org/vufind/pull/214|#214]]). We often include as many useful features as we can and control it with configs but there's another way... A separate respository/website/use the issues page for useful tweaks that don't belong in master.
+Overall positive support for this idea, seems like a logical idea to provide extended functionality, but concerns for extended work to maintain the branches to keep them up to date. Will send an email out to the tech group outlining the idea for more general feedback and will bring up in the call in two weeks.
 ==== 3. Other Topics? ====
+None this week.
 ===== Next Call =====
@@ Line 50: / Line 68: @@
 The next call will be Tuesday, April 14, 2015 at 10am Eastern Daylight Time (14:00 GMT).
 ---- struct data ----
+properties.Page Owner :
 ----