Re: [OPEN-ILS-GENERAL] Planned Parts Development

2013-01-29 Thread Mike Rylander
Tim, That looks like a good set of enhancements. Just one comment and one question: * I suspect that the DISK 15.1 anomaly is caused by an extra space between DISK and 15.1, which gets it an extra pile of zeroes. * Do you plan to leave the existing sort label infrastructure there, and use

Re: [OPEN-ILS-GENERAL] Planned Parts Development

2013-01-29 Thread Tim Spindler
Mike, The coding table design decisions will ultimately be up to Dan Pearl (our in house developer) but I was thinking the label_sortkey would not be eliminated since that would be a default sort. I personally was envisioning that an extra table column would be needed for sort order whereby

Re: [OPEN-ILS-GENERAL] Planned Parts Development

2013-01-29 Thread Hardy, Elaine
29, 2013 11:38 AM To: Evergreen Discussion Group; open-ils-...@list.georgialibraries.org Subject: [OPEN-ILS-GENERAL] Planned Parts Development We are looking for comment on the proposed development. Attached is the specification. -- Tim Spindler Manager

[OPEN-ILS-GENERAL] Planned Parts Development

2013-01-29 Thread sarahc
Elaine asks: Have you considering, rather than Pt 2 merging labels changing it to making managing parts permissions at the consortium level rather than the local level? That would solve the duplicate label issue and move the management further up the hierarchical structure. This would

Re: [OPEN-ILS-GENERAL] Planned Parts Development

2013-01-29 Thread Hardy, Elaine
Subject: [OPEN-ILS-GENERAL] Planned Parts Development Elaine asks: Have you considering, rather than Pt 2 merging labels changing it to making managing parts permissions at the consortium level rather than the local level? That would solve the duplicate label issue and move the management