I'd agree with Thomas that the hard coded IDs for legacy stat cats would
have no real meaning in our system either. I have to review the other
fields, but they might be interesting enough to interest our report
writers to have them included on our system.
We aren't using it in our DB, though apparently we have the fm_IDL
entries. Oops.
So as far as it being a good example, yes, I think that it's cool to
see/learn from them. But installing by default, maybe not all of it?
-- Ben
On 09/13/2012 10:09 AM, Thomas Berezansky wrote:
I am going to vote against including them by default, and vote for
commenting out their IDL views by default instead.
Having looked through some of the contents of that file it is making
assumptions I don't like. Grabbing asset stat cats based on them being
in specific IDs, for example, that may have no meaning on non-PINES
systems.
Basically, I think they make useful examples, but I don't think they
should be installed by default.
Thomas Berezansky
Merrimack Valley Library Consortium
Quoting Galen Charlton <[email protected]>:
Hi,
On Thu, Sep 13, 2012 at 9:55 AM, Dan Scott <[email protected]> wrote:
On the other hand - if there are lots of sites are currently using the
reporter extensions, then let's just add them to the stock database
creation scripts and be done with it.
I know we're using them, for example. Show of hands?
I'm for just installing them by default.
Regards,
Galen
--
Galen Charlton
Director of Implementation
Equinox Software, Inc. / The Open Source Experts
email: [email protected]
direct: +1 770-709-5581
cell: +1 404-984-4366
skype: gmcharlt
web: http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org &
http://evergreen-ils.org
--
Benjamin Shum
Open Source Software Coordinator
Bibliomation, Inc.
32 Crest Road
Middlebury, CT 06762
203-577-4070, ext. 113
