Differences

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

--- developers_call:minutes20120821 [2012/08/21 14:04] – demiankatz
+++ developers_call:minutes20120821 [2015/12/21 17:23] (current) – [3. VuFind Developers Summit 2012] demiankatz
@@ Line 1: / Line 1: @@
 ====== VuFind Developers Call Minutes: August 21, 2012 ======
-Attending: Filipe Bento, Oliver Goldschmidt, Demian Katz, David Maus, Tod Olson, Sean Purcell, June Rayner, Al Rykhus
+Attending: Filipe Bento, Oliver Goldschmidt, Demian Katz, David Maus, Benjamin Mosior, Tod Olson, Sean Purcell, June Rayner, Al Rykhus
 ===== Agenda =====
@@ Line 20: / Line 20: @@
   * [[http://vufind.org/jira/browse/VUFIND-634|VUFIND-634]] - This ticket was opened to document a problem in Zend Framework 2, but it was fixed faster than expected; ticket closed, please ignore.
   * [[http://vufind.org/jira/browse/VUFIND-635|VUFIND-635]] - This ticket includes a patch to add [[http://www.clickatell.com/|Clickatell]] SMS support to VuFind.
-  * [[http://vufind.org/jira/browse/VUFIND-636|VUFIND-636]] - This new ticket differentiates the EBSCO Discovery Service (EDS) API from the EBSCO Integration Toolkit (EIT) API (covered by [[http://vufind.org/jira/browse/VUFIND-423|VUFIND-423]]).  It mentions the fact that EBSCO has released some code for incorporating EDS into VuFind.
+  * [[http://vufind.org/jira/browse/VUFIND-636|VUFIND-636]] - This new ticket differentiates the EBSCO Discovery Service (EDS) API from the EBSCO Integration Toolkit (EIT) API (covered by [[http://vufind.org/jira/browse/VUFIND-423|VUFIND-423]]).  It mentions the fact that EBSCO has released some code for incorporating EDS into VuFind.  Tod mentioned his willingness to discuss license terms with EBSCO if their existing code is not already licensed in a way that allows inclusion in the trunk.
 ==== 2. VuFind 2.0 Update ====
@@ Line 40: / Line 40: @@
 ==== 3. VuFind Developers Summit 2012 ====
-A preliminary schedule is being drafted and should be posted soon on the [[..:VuFind Summit 2012]] wiki page.  Presentation slots are filling up, so please submit your presentations soon.  Also on the wiki page are a couple of new areas for user input:
+A preliminary schedule is being drafted and should be posted soon on the [[community:conferences:summit_2012|VuFind Summit 2012]] wiki page.  Presentation slots are filling up, so please submit your presentations soon.  Also on the wiki page are a couple of new areas for user input:
 .) There is a "lightning round" signup section for people interested in giving 5-minute presentations about specific features/enhancements of VuFind.
@@ Line 48: / Line 48: @@
 ==== 4. Open Data / Shared Central Index ====
-Filipe has added an entry for [[..:open_data_sources#springeropen_oai_-_pubmed_format|SpringerOpen]].
+Filipe has added an entry for [[indexing:open_data_sources#springeropen_oai_-_pubmed_format|SpringerOpen]].  He next plans to investigate settings for importing from InTech Open, an eBook provider.
 ==== 5. Other Topics? ====
+Al brought up the subject of LibX causing COinS to display awkwardly.  Demian has adjusted the trunk to give COinS spans a display:none property -- this should prevent them from appearing when LibX is installed without breaking Zotero, etc.  It's an easy fix to apply to an existing install (just add a couple lines to CSS) if necessary.
+Filipe has been brainstorming a "remember me" solution for VuFind's login system.  He would like to find a way to uniquely identify a remote machine without using cookies for cross-browser memory.  However, this would seem to require generation of a key on the client, which would require extra components (i.e. a Java element) and could still be spoofed.  It would also be very dangerous in combination with public terminals.  There was also discussion of multi-level authentication (i.e. remember the user for "safe" actions but require reauthentication for "dangerous" actions... with configuration for defining what is safe and what is dangerous).
+Demian's recommendation: implement with cookies for now (the most common practice in this area) but make the long-term authentication mechanism configurable so the cookie check can be replaced with something else if we devise a more clever mechanism for identifying users.
+Everyone agrees that this system should be optional -- not everyone will want it, and in some cases it will cause problems (i.e. in combination with single sign-on).
+David pointed out the [[http://en.wikipedia.org/wiki/Cross-Site_Request_Forgery|Cross-Site Request Forgery]] as something that should be watched for.
 ===== Next Call =====
@@ Line 56: / Line 66: @@
 The next call will be Tuesday, September 4, 2012 at 10am Eastern Daylight Time (14:00 GMT).
 ---- struct data ----
+properties.Page Owner :
 ----