Differences

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

--- developers_call:minutes20171205 [2017/12/05 13:45] – [2. Development Planning] demiankatz
+++ developers_call:minutes20171205 [2017/12/05 14:20] (current) – [Next Call] demiankatz
@@ Line 1: / Line 1: @@
 ====== VuFind Developers Call Minutes: December 5, 2017 ======
-Attending:
+Attending: Matthias Edel, Demian Katz, Ere Maijala, Tod Olson
 ===== Agenda =====
@@ Line 27: / Line 27: @@
 Another topic for further consideration: the ZF convention is now to use fully-qualified class names as service names, with aliases set up where appropriate. VuFind has historically used short names for most services. This is now awkward in cases where VuFind mixes overrides to ZF services with its own services, as the mix of short and long names looks odd. Should we standardize on the ZF approach, or is that too verbose? (Note that we can merge #1067 before we decide on this issue -- it can always be addressed as a future enhancement).
+Ere voted in support of switching to fully-qualified class names.
 == Solr 7 ==
-Demian began experimenting with Solr 7. Due to a change from XML to JSON as default response format, SolrMarc is having trouble indexing to Solr 7, so fixing that is the first priority (Bob is working on it). Additionally, there are some deprecations that will have to be addressed in the schema. Finally, we might want to begin looking at the v2 API, though the legacy API still seems to be fully supported for the moment.
+Demian began experimenting with Solr 7. Due to a change from XML to JSON as default response format, SolrMarc is having trouble indexing to Solr 7, so fixing that is the first priority (Bob has committed a fix and will mint a new release soon). Additionally, there are some deprecations that will have to be addressed in the schema. Finally, we might want to begin looking at the v2 API, though the legacy API still seems to be fully supported for the moment.
 == What next? ==
@@ Line 37: / Line 39: @@
 === Image Metadata API ===
+No news.
 === Front End Updates ===
+No news.
 === Browse Handler Optimizations ===
+Tod has been working on setting up a test for this. Tod is encountering some volatility in class interfaces, etc., within the Solr code, which adds some extra challenges. No working tests yet, but progress is being made.
+Also some discussion of whether Marc4j supports JSON encodings of MARC.
 ==== 3. Institutional Home ====
+No news.
 ==== 4. Other Topics? ====
+Ere is looking at facet performance optimization -- not loading collapsed facet data to improve retrieval times.
 ===== Next Call =====
-The next call will be Tuesday, December 19, 2017 at 9am Eastern Standard Time (14:00 GMT).
+:!: Due to low participation and activity during the holiday season, we decided to skip the December 19, 2017 and January 2, 2018 calls.
+The next call will be Tuesday, January 16, 2018 at 9am Eastern Standard Time (14:00 GMT).
 ---- struct data ----
+properties.Page Owner :
 ----