On Wed, Oct 1, 2008 at 10:06 AM, Kathy Rippel <[EMAIL PROTECTED]> wrote:
> I agree, Marie. The list should have terms that librarians will recognize, > not programmers. The underlying structure can still use the programming > terms. > > Kathy > > > At 03:41 PM 9/30/2008, Nicole Engard wrote: > > As far as I know there isn't a list. It's sort of hit or miss. I usually > find out just testing different fields. I'm CCing the Koha List in case > they have any ideas. > > > --- > > Nicole C. Engard > Open Source Evangelist, LibLime > (888) Koha ILS (564-2457) ext. 714 > [EMAIL PROTECTED] > AIM/Y!/Skype: nengard > > http://liblime.com > http://blogs.liblime.com/open-sesame/ > > > On Tue, Sep 30, 2008 at 4:20 PM, Marie Wardall <[EMAIL PROTECTED] > > wrote: > Hi Nicole- > I'm looking at our test data for our school district and am trying to get a > handle on creating some custom reports because some of the reports in the > Wizard just don't pull enough or the right data. > > When I go into the custom report area I'm getting confused as to what a;; > of the things mean in Step 3 where you select columns for display. Is there > someplace that describes each of these so that I can make a good choice? > > Any help you could give me would be appreciated. > > Thanks, > > > Marie J. Wardall > Library Media Specialist > Mountain Bay Elementary School > 8602 Schofield Ave. > Weston, WI 54476 > [EMAIL PROTECTED] > Phone: 715-355-0302 ext. 5824 > > Change Today, Change Tomorrow, Keep Changing > > > _______________________________________________ > Koha mailing list > [EMAIL PROTECTED] > http://lists.katipo.co.nz/mailman/listinfo/koha > > > Kathy Rippel > > _______________________________________________ > Koha mailing list > [EMAIL PROTECTED] > http://lists.katipo.co.nz/mailman/listinfo/koha > > As far as I know, this is due to the columns.def file not being up to date with the Koha database. A while back, we discussed using MySQL's COMMENT option to put descriptive information in the table schema. We have a couple of options: * Update columns.def so that it has all of the columns referenced by the guided reports tool. * Using a db update, add comments to all of those columns. These can be gotten by SHOW FULL COLUMNS FROM <table>. This has the advantage of being more "proper", but is yet another displayed string in the database that would have to be translated... somehow. My vote is for columns.def, since it's under the template tree and therefore easily internationalized. Thoughts? -- Jesse Weaver Software Developer, LibLime
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
