From b1c7afdd4bbadc6087c95d1d02a620c0727f6a0e Mon Sep 17 00:00:00 2001 From: Lebbeous Fogle-Weekley Date: Mon, 17 Dec 2012 14:54:01 -0500 Subject: [PATCH] Tech spec updates Signed-off-by: Lebbeous Fogle-Weekley --- docs/TechRef/Circ/custom-best-hold-selection.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/TechRef/Circ/custom-best-hold-selection.txt b/docs/TechRef/Circ/custom-best-hold-selection.txt index ecac5accff..21e110e44a 100644 --- a/docs/TechRef/Circ/custom-best-hold-selection.txt +++ b/docs/TechRef/Circ/custom-best-hold-selection.txt @@ -48,9 +48,9 @@ Proposal To that end, we propose a new table to define field importance, and a new org- unit setting to replace "FIFO Holds" and select the appropriate definition for the capturing location. The UI for creating or editing hold order definitions -should consist of a drag-and-drop list for ordering the options, a text entry -for naming the definition, and a save button that will trigger inspection of -the ordinal position of the options within the list. +should consist of a list for ordering the options, controlled by up-and-down +buttons both clickable and accessible by keyboard. There will also be a field +for naming the definition and a save button. This org-unit setting will be retrieved at capture time, instead of the FIFO setting, and inspected by open-ils.storage.action.hold_request.nearest_hold. @@ -131,7 +131,7 @@ INSERT INTO config.best_hold_order ( name, hprox, pprox, aprox, priority, cut, depth, rtime, htime ) VALUES ( - 'Traditional with Holds-always-go-home', + 'Traditional with Holds-always-go-to-home-patrons', 1, 2, 3, 4, 5, 6, 7, 8 ); @@ -155,7 +155,7 @@ INSERT INTO config.best_hold_order ( name, hprox, priority, cut, rtime, depth, pprox, aprox, htime ) VALUES ( - 'FIFO with Holds-always-go-home', + 'FIFO with Holds-always-go-to-home-patrons', 1, 2, 3, 4, 5, 6, 7, 8 ); @@ -238,7 +238,7 @@ editing of existing ones, given sufficient user permission. The name field (metadata) will be editable with a free-form text widget, and the remaining (data) fields will be represented by objects that the user -manipulates via drag-and-drop to indicate order. +manipulates via clickable buttons (also keyboard accessible) to indicate order. //// vim: ft=asciidoc -- 2.11.0