Warning: This page has not been updated in over over a year and may be outdated or deprecated.
developers_call:minutes20140916
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
developers_call:minutes20140916 [2014/09/16 13:38] – [VuFind Developers Call Minutes: September 16, 2014] demiankatz | developers_call:minutes20140916 [2014/09/16 14:55] – [4. Other Topics?] demiankatz | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== VuFind Developers Call Minutes: September 16, 2014 ====== | ====== VuFind Developers Call Minutes: September 16, 2014 ====== | ||
- | Attending: Filipe Bento, Demian Katz | + | Attending: Filipe Bento, Judy Brink-Drescher, |
===== Agenda ===== | ===== Agenda ===== | ||
Line 25: | Line 25: | ||
==== 2. Development Planning ==== | ==== 2. Development Planning ==== | ||
+ | |||
+ | === Consortialize === | ||
+ | |||
+ | Chris D. mentioned that progress is being made on this [[https:// | ||
=== Call Number Normalization === | === Call Number Normalization === | ||
Tod has sent an email proposing a change to LC call number sort key generation to solrmarc-tech and is awaiting feedback. | Tod has sent an email proposing a change to LC call number sort key generation to solrmarc-tech and is awaiting feedback. | ||
+ | |||
+ | Tod's goals: | ||
+ | |||
+ | - Create classes for all call number manipulation logic (for easier code reuse and to reduce redundant work) | ||
+ | - More robust support for "not exactly LC" data (e.g. local custom variations of call number standards, or call numbers conforming to different standards, which some institutions stick in the same field as LC) -- we should be more tolerant of unexpected data. Current code drops things it doesn' | ||
+ | |||
+ | Tod discussed the algorithm behind his [[https:// | ||
+ | |||
+ | Demian suggested that Tod should talk to Luke O' | ||
+ | |||
+ | Demian also mentioned his recent work improving Dewey sort key generation. | ||
+ | |||
+ | There was some discussion of the solrmarc project, SVN merging, and other external challenges to getting all of this fully incorporated into VuFind. | ||
+ | |||
+ | Anna is working on some call number related improvements to the UI -- link call numbers to call number browse, have "no results" | ||
=== Should we eliminate AbstractPluginFactory implementations? | === Should we eliminate AbstractPluginFactory implementations? | ||
Line 35: | Line 54: | ||
Note one significant exception to the rule: right now, most Search\Options, | Note one significant exception to the rule: right now, most Search\Options, | ||
+ | |||
+ | There was no objection to the basic idea, so Demian will put together a pull request for review and submit it to vufind-tech before merging it to master. | ||
=== Should we split out stand-alone libraries? === | === Should we split out stand-alone libraries? === | ||
Demian is thinking about whether it makes sense to move portions of VuFind to their own GitHub projects for ease of reuse. Right now, he is considering splitting out the \VuFind\Code\ISBN class to its own \VuFindCode\ISBN project as a trial. This would then be loaded into the vendor directory with Composer in the main VuFind project instead of being part of the core VuFind module. The project could be given its own continuous integration page. Since this particular class is fairly stable, this is unlikely to add a major development burden. Moving some of the more volatile pieces (like the VuFindSearch module) might add greater complexity to project management, but is still worth considering. | Demian is thinking about whether it makes sense to move portions of VuFind to their own GitHub projects for ease of reuse. Right now, he is considering splitting out the \VuFind\Code\ISBN class to its own \VuFindCode\ISBN project as a trial. This would then be loaded into the vendor directory with Composer in the main VuFind project instead of being part of the core VuFind module. The project could be given its own continuous integration page. Since this particular class is fairly stable, this is unlikely to add a major development burden. Moving some of the more volatile pieces (like the VuFindSearch module) might add greater complexity to project management, but is still worth considering. | ||
+ | |||
+ | If Demian finds time, he will try to set up a VuFindCode project and see how difficult the process is. Once that is done, he will share it with vufind-tech and the determination can be made whether or not it's worth pulling it in as a vendor dependency or maintaining the current code as-is. | ||
==== 3. 2014 VuFind Summit ==== | ==== 3. 2014 VuFind Summit ==== | ||
Some cosmetic fixes still need to be made to adjust some outdated text, but the [[http:// | Some cosmetic fixes still need to be made to adjust some outdated text, but the [[http:// | ||
+ | |||
+ | If you propose a talk and have the proposal accepted, you can get in free -- no need to register. Submit proposals to Demian. | ||
==== 4. Other Topics? ==== | ==== 4. Other Topics? ==== | ||
+ | No other topics this week. | ||
===== Next Call ===== | ===== Next Call ===== | ||
developers_call/minutes20140916.txt · Last modified: 2016/04/07 15:14 by milenakrakowiy