Skip to content
Mark A. Matienzo edited this page Aug 3, 2017 · 40 revisions

Blacklight Committers meeting Nov 3 2011

Please add/refine/elaborate as you see fit. It would be AWESOME if we could actually code some of this stuff while we’re there. (heads down folks: → folks who will actually make it happen, perhaps pair programming on a second day)

Who is interested in staying another day to actually work on some of these things? Put your names on the "heads down folks" lines for the topics below.

People:

  • Chris Beer, WGBH. arriving Wednesday noon, Leaving Friday late.

  • Jessie Keck, Stanford. Arriving Sunday evening, Leaving Thursday 4pm.

  • Sean Hannan, Johns Hopkins. Arriving ∞, Leaving ∞. I live here.

  • Rick Johnson, Notre Dame. Arriving Monday morning, leaving Fri 11/4 6:00am

  • Molly Pickral, University of Virginia. Thursday only.

  • Bob Haschart, University of Virginia. Thursday only.

  • Joe Gilbert, University of Virginia. Thursday only.

  • Xiaoming Wang, University of Virginia. Thursday only.

  • Julie Meloni, University of Virginia. Monday at DLF, Thursday for Blacklight (will be a bit late).

  • Erik Hatcher, Lucid Imagination. Thursday for sure. Possibly Wednesday also.

  • Christopher Ball, meta Heuristica. Thursday only.

  • Chris Awre, University of Hull. Thursday only, but also around for DLF beforehand

  • Naomi Dushay, Stanford. Thursday only (leaving 4pm)

  • Tom Cramer, Stanford. Thursday only (leaving 4pm)

  • Matt Zumwalt, MediaShelf. Thursday only

Developer Topics

Discussion Topics

  • Documentation & getting organized about it (Hudson & test suite as well)

    • heads down folks: ndushay

  • profile blacklight & optimization (jkeck) / probably will lead into a discussion of rails3 slowdowns

    • heads down folks: jkeck

  • Version releases, scheduling, and impact on wider usage (e.g., Hydra)

Development planning

Can we get cleaner search urls?
Is there a cleaner way to express a selected facet than f[format_facet][]=Book ?
  • heads down folks:

Would be great to have usage data for searches, etc.

Maybe something basic like http://digital.library.unt.edu/ark:/67531/metadc5668/stats/ ?
  • heads down folks: cbeer

    • Folders vs Bookmarks

What's the difference? What should the UX be? Can the codebase be unified?
  • Bug fix/refactor: The "search context" stuff, and how buggy and complicated it is (a top priority for jrochkind)

Refactoring this feature (so it doesn't rely on session context?):
Showing item 2 of 9,874 from your search.
<< Previous      Next >>

Heads-down work on bugs and features

This work is mostly complete in https://github.com/projectblacklight/blacklight-jetty/tree/solr-3.4 but could use a review before being pushed to master
  • heads down folks: cbeer, ndushay, …​

    • Blacklight config refactor

This work is tracked in https://github.com/projectblacklight/blacklight/tree/feature-config-refactor

cbeer would like to get more eyes on the code, trying it out, before it is merged into master
  • SASS/Asset Pipeline work

James at Columbia has been working on converting our existing CSS to work (exclusively) with the Rails 3.1 Asset Pipeline. Beyond an upgrade guide, the work is ready to be merged into master.
Add the opensearch style autocomplete to the input field on the search form.

jkeck wants to knock this one out at the meeting and has volunteered to organize this discussion
  • heads down folks: jkeck

    • Bug fix: exporting entire Folder, not just current page (CODEBASE-300)

Possibly related to the Folder vs Bookmarks discussion
What standards are we using? Can we pull in Hydra's validation tests?
Do right-to-left scripts display properly in search results and detailed record pages?
Are CJK being indexed appropriately out of the box? See http://groups.google.com/group/blacklight-development/msg/fe82c695492e654c
  • heads down folks: ndushay

UI/UX planning, design, and implementation

  • Different views/skinning/CSS/local customizations

    • heads down folks: Joe G (interested in theming architecture)

  • "more like this" (CODEBASE-39)

It would probably be useful to have a "more like this" feature in blacklight, once a document is selected.

Existing plugin at  http://github.com/cbeer/blacklight_mlt
  • heads down folks:

    • Range searching in core?

    • Branding Blacklight as a more general purpose solr interface.

New features/extensions planning and development

  • Book Cover fetching (CODEBASE-11)

    • heads down folks: jkeck

  • some kind of browse/headings search or browse search substitute (jrochkind has ideas for various approaches, a top priority for JHU. UW’s work in progress is one model)

  • call number virtual shelf browse. Not quite the same thing as headings browse above. desired by JHU & UVa.

  • Exhibits in Blacklight

Rick J: Notre Dame has done some work w/ in this space for Hydra.  They have called this functionality Atrium.  Rick would like to make this work w/ Blacklight alone and will try to attend the meetings to discuss how this Blacklight can be improved to facilitate this kind of extension.

Other

First, extending Blacklight to provide domain specific services. Out of box, Blacklight is rudimentary. Work is often necessary to make it applicable in particular domains, e.g. as a library management system and RoR alternative to systems such as Koha and Evergreen. The extension could be subject based too, e.g. music, JISC subject portals especially these entail specific use case/integration.  Second, enhancing the usability/usefulness of Blacklight for users and developers alike, e.g. making it even easier for developer to adopt the product, providing abstract layers for AJAX UI library, modernising the UI with HTML5 and meta-markups. Training and tutorial will help too.
Clone this wiki locally