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

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:minutes20160202 [2016/02/01 17:37] – [2. Development Planning] demiankatzdevelopers_call:minutes20160202 [2016/02/02 14:31] (current) – [3. Other Topics?] demiankatz
Line 1: Line 1:
 ====== VuFind Developers Call Minutes: February 2, 2016 ====== ====== VuFind Developers Call Minutes: February 2, 2016 ======
  
-Attending: +Attending: Chris Hallberg, Demian Katz, Claas Kazzer, André Lahmann, Jochen Lienhard, Ere Maijala, Brad Patton
  
 ===== Agenda ===== ===== Agenda =====
Line 9: Line 9:
 === JIRA Tickets === === JIRA Tickets ===
  
-  * [[https://vufind.org/jira/browse/VUFIND-1143|VUFIND-1143]] - +No developments since last time.
  
 === Pull Requests === === Pull Requests ===
Line 24: Line 24:
   * [[https://github.com/vufind-org/vufind/pull/576|#576]] - in progress - Refactoring of VuFind's search persistence functionality (memory of most recent sort/limit/view/etc. settings); see below.   * [[https://github.com/vufind-org/vufind/pull/576|#576]] - in progress - Refactoring of VuFind's search persistence functionality (memory of most recent sort/limit/view/etc. settings); see below.
   * [[https://github.com/vufind-org/vufind/pull/578|#578]] - merged - Improved RSS/OpenSearch standards compliance.   * [[https://github.com/vufind-org/vufind/pull/578|#578]] - merged - Improved RSS/OpenSearch standards compliance.
-  * [[https://github.com/vufind-org/vufind/pull/579|#579]] - merged - Translation improvements.+  * [[https://github.com/vufind-org/vufind/pull/579|#579]], [[https://github.com/vufind-org/vufind/pull/583|#583]] - merged - Translation improvements.
   * [[https://github.com/vufind-org/vufind/pull/580|#580]] - merged - Fixed escaping of translation keys in generated Javascript.   * [[https://github.com/vufind-org/vufind/pull/580|#580]] - merged - Fixed escaping of translation keys in generated Javascript.
 +  * [[https://github.com/vufind-org/vufind/pull/581|#581]] - merged - Fixes to deduplication listener.
 +  * [[https://github.com/vufind-org/vufind/pull/582|#582]] - in progress - Upgrade to bootstrap slider control; will be reviewed soon.
  
 ==== 2. Development Planning ==== ==== 2. Development Planning ====
Line 31: Line 33:
 === Improved Author Indexing === === Improved Author Indexing ===
  
-More translations have been merged to the branch, and Demian has merged the necessary code changes into SolrMarc master and inquired about the next release.+More translations have been merged to the branch, and Demian has merged the necessary code changes into SolrMarc master and inquired about the next release. This seems likely to be merged to master quite soon (barring a delay in the SolrMarc release process). 
 + 
 +Ere requested a comprehensive summary of changes so that indexing tools can be properly updated; Demian will adjust the schema change log soon (if it is not already up to date).
  
 === Delimited Facets === === Delimited Facets ===
Line 39: Line 43:
 === Solr Upgrade === === Solr Upgrade ===
  
-Demian has updated PR [[https://github.com/vufind-org/vufind/pull/435|#435]] to Solr 5.4.1, which solves the MoreLikeThis problem found in 5.4.0. The branch is once again functional. We still need to investigate outstanding potential performance issues and decide how to address docValues, if at all.+Demian has updated PR [[https://github.com/vufind-org/vufind/pull/435|#435]] to Solr 5.4.1, which solves the MoreLikeThis problem found in 5.4.0. The branch is once again functional. We still need to investigate outstanding potential performance issues and decide how to address docValues. Recent mailing list discussion (including a thread started today by Günter Hiplerwho was unable to attend today's call) suggests that this remains a significant problem.
  
 === Javascript Reorganization === === Javascript Reorganization ===
 +
 +Work is ongoing on improved (simplified) lightbox functionality in [[https://github.com/vufind-org/vufind/pull/402|pull request #402]]. Demian has been doing some work on automated testing of simulated ILS functionality to help exercise relevant code paths.
 +
 +Chris is also working on eliminating the "two search boxes for responsiveness" approach in order to have just one functioning search box.
 +
 +Coming soon: a style guide for code/front end of VuFind (also from Chris).
  
 === Cover Issues === === Cover Issues ===
 +
 +No news.
  
 === API === === API ===
 +
 +Günter reports that his API project with Markus Maechler is slightly delayed, but he will share more information as it becomes available.
 +
 +Ere's search API implementation goes live tomorrow. He will think about generalizing this further in the near future (and open a PR for discussion).
  
 === Modularization === === Modularization ===
 +
 +Günter suggested reviewing [[https://mwop.net/blog/2016-01-28-expressive-stable.html|this blog post on Expressive]] and the [[http://framework.zend.com/blog/|Zend Framework blog]] in general for progress on ZF3 which may impact future VuFind development. We should all take a closer look at this and discuss it in more detail on the next call.
 +
 +Ere requested a summary of ZF3's current state; Demian mentioned the importance of [[http://www.php-fig.org/psr/psr-7/|PSR-7]] but needs to do more research himself to have a full understanding of the situation -- more next time.
  
 === Improved Use of Permissions === === Improved Use of Permissions ===
  
 Demian has begun working on this. One challenge: how should we handle displaying links to permission-driven functionality when users are not logged in? For example, if only some users are allowed to store favorites, should we, or should we not, display a favorites link to a non-logged-in user? We should determine a pattern/convention for this situation that we can apply across the board, should we decide to make some of these features permission-driven. Demian has begun working on this. One challenge: how should we handle displaying links to permission-driven functionality when users are not logged in? For example, if only some users are allowed to store favorites, should we, or should we not, display a favorites link to a non-logged-in user? We should determine a pattern/convention for this situation that we can apply across the board, should we decide to make some of these features permission-driven.
 +
 +Suggestion: use flash messages to display "please log in to see advanced features."
 +
 +Ere's comment: "try not to promise too much before the user logs in." Hard to come up with wording.
 +
 +Demian's thought: we may need some configuration mechanism for associating permissions with behaviors (i.e. show link, hide link, show flash message, etc.). More thought/discussion needed.
  
 === Session Performance Improvement === === Session Performance Improvement ===
Line 58: Line 84:
 ==== 3. Other Topics? ==== ==== 3. Other Topics? ====
  
 +Ere asked what the next VuFind version number will be. Demian is set on 3.0 at this point (mainly for improved semantic versioning compliance -- the main number will increment more quickly from now on, even though the pace of development probably won't accelerate dramatically to match).
 ===== Next Call ===== ===== Next Call =====
  
 The next call will be Tuesday, February 16, 2016 at 9am Eastern Standard Time (14:00 GMT). The next call will be Tuesday, February 16, 2016 at 9am Eastern Standard Time (14:00 GMT).
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
developers_call/minutes20160202.1454348268.txt.gz · Last modified: 2016/02/01 17:37 by demiankatz